Plumber Call Intake Script: Six Details to Capture Before Dispatch

A plumbing inquiry needs enough detail for the next person to act without making the caller repeat everything. Start with the service request, then capture contact and location information, urgency and a preferred time. Do not turn the first conversation into a diagnosis or a promise of arrival.

floGPT’s inspected home-services template contains six intake fields: name, phone, service type, urgency, address and preferred window. The first five are required in that template; the preferred window is optional. Here is a practical way to use that structure for a plumbing business.

Open with the caller’s request

An illustrative opening is: “Thanks for calling. What plumbing work do you need help with?” Let the caller describe the situation before asking for contact details. “Kitchen sink draining slowly” is more useful to a dispatcher than a generic label such as “repair.”

Record what the caller reports. Avoid converting a description into a technical diagnosis that no technician has verified. If the caller mentions a situation covered by your business’s escalation policy, follow that policy and involve a person.

Capture the six details in a natural order

• Service type: “Which fixture or part of the property is affected?”
• Name: “Who should our team ask for?”
• Phone: “What number should the team use to reach you?”
• Address: “What is the service address, including the unit?”
• Urgency: “When do you need help, and what is happening now?”
• Preferred window: “Is there a time that would work for a callback or visit?”

The order can change with the conversation. If the caller has already supplied a detail, confirm it where appropriate rather than asking the same question again. The template marks name and phone to skip when already known; useful intake still requires checking that the information belongs to this request.

Read the address back

A transposed house number or missing apartment can make an otherwise complete note unusable. The inspected template specifically calls for address confirmation. A concise read-back might be: “I have 42 Example Street, unit B. Is that the service location?” This is a fictional address used only to illustrate the script.

Ask about missing access details when they affect the handoff, but avoid gathering unrelated information. A phone assistant does not need a caller’s entire account history to describe a new leaking-tap inquiry.

Separate preference from a confirmed appointment

“I would prefer tomorrow morning” is an availability request. It becomes a confirmed appointment only through the business’s actual scheduling process. Until then, say: “I’ll include tomorrow morning as your preferred window for the team to review.”

The same distinction applies to price. Capture a quote request without inventing a firm charge or suggesting a technician has accepted the job. The source template explicitly avoids firm pricing promises.

Finish with a dispatch-ready summary

An illustrative handoff is: “New plumbing inquiry; kitchen sink draining slowly; service address confirmed; callback number recorded; caller requests tomorrow morning; visit and price not confirmed.” The actual record would hold the supplied name, number and address in the business system.

Review several simulated calls before enabling the flow. Check missing addresses, repeated callers, urgent language and requests outside the service area. floGPT’s home-services overview describes the phone, chat and team-handoff use case. Create a business account to configure an intake flow around your own dispatch rules.

Original paper-art illustration; not a photograph, site plan or product screenshot.