Caller identity
Ask for this
Name, callback number, customer status, and who is on-site.
Why it matters: Dispatch cannot safely continue if the office cannot reach the right person.
Dispatch script guide
Answering service dispatch scripts and fields for home services.
A dispatch script is useful only when it tells agents what to ask, what to avoid, where to document the work, and when to escalate instead of guessing.
Required fields
The handoff is not complete until these fields are captured.
These fields make the difference between a basic answering service message and outsourced dispatch support that a dispatcher, office manager, or on-call owner can act on.
Service location
Ask for this
Address, unit, access notes, gate code policy, and service area.
Why it matters: A call is not dispatch-ready until the service location is clear.
Issue type
Ask for this
Trade, symptom, active failure, quote request, warranty concern, or routine update.
Why it matters: Issue type drives urgency, script language, booking path, and escalation owner.
Urgency signal
Ask for this
Active leak, no heat, no cooling, safety concern, commercial account, VIP, or angry customer.
Why it matters: Urgency determines whether the call waits, books, or wakes the on-call person.
Next-step authority
Ask for this
Can the agent book, prepare notes, transfer, page, or only create a callback task?
Why it matters: Authority boundaries stop agents from improvising pricing, warranty, or dispatch judgment.
System record
Ask for this
Where should the note, tag, callback, booking review, or escalation receipt live?
Why it matters: A separate message log creates rework; the operating record needs the context.
Script blocks
Sample language for the first dispatch lane.
These are not a replacement for client-approved scripts. They show the type of language that keeps agents inside the workflow boundary.
Opening
Thanks for calling. I can help collect the details and route this based on the approved after-hours process. What is the service address?
Urgency check
Is this causing active damage, a safety concern, no heat, no cooling, or another issue that cannot wait until the next business day?
Booking boundary
I can prepare the service request and route it according to the schedule rules. If pricing, warranty, or an exception comes up, I will send it to the approved owner.
Escalation handoff
I am escalating this now with the address, issue, urgency, callback number, and the details you shared so the on-call owner has the context.
QA review
Review the script against real calls before expanding authority.
- The note includes caller, callback, location, issue, urgency, next step, and system record.
- The agent did not quote, approve warranty work, promise arrival time, or resolve an exception outside the approved script.
- Emergency, angry-customer, VIP, commercial, or unclear calls escalated to the right owner.
- Routine calls entered the morning queue with enough context to continue without restarting the conversation.
FAQ
Dispatch script questions.
What fields should an answering service collect before dispatch?
At minimum, collect caller identity, callback number, service location, issue type, urgency, access notes, customer status, approved next step, and where the record was updated.
Can an outsourced dispatch team book jobs directly?
Yes, but only after the client defines booking authority, schedule rules, service zones, job types, blocked actions, and escalation triggers.
What should never be improvised in an after-hours script?
Pricing, warranty decisions, refunds, safety judgment, technician routing exceptions, legal language, and angry-customer recovery should route to the approved internal owner unless the client has provided exact approved language.