Separate intake from technical diagnosis
An answering representative needs enough information to route the call, not to diagnose the plumbing system. Capture the caller’s name, callback number, service address, concise description, and any access or tenant details the contractor requires.
Use the contractor’s approved wording for safety notices and never improvise technical instructions.
Define the service boundary
The script should identify the geographic service area, customer types served, hours, excluded work, and any information that must be collected before dispatch. This prevents avoidable pages to the on-call technician.
If pricing cannot be quoted from an approved schedule, say so and explain the next step rather than estimating.
Write observable urgency and dispatch rules
The contractor should define which caller-reported conditions trigger an immediate page and which can wait for normal scheduling. The representative applies those rules and records the caller’s words; the contractor remains responsible for the technical decision.
Document the contact order, retry timing, and fallback when the on-call technician cannot be reached.
Close the loop
Tell the caller whether the message is being dispatched, queued for scheduling, or sent for a callback. The message should contain the details the next person needs to act.
Review calls after severe weather and seasonal peaks. They reveal missing script branches and help distinguish overflow needs from permanent coverage gaps.
