A Phone Answering Script for a Trade Business

A phone answering script is a short, fixed set of questions asked in the same order on every call, before anyone tries to solve what the caller actually wants. The order does the work: ask what's wrong first, and a caller with a genuine emergency spends thirty seconds describing a job before anyone realizes it can't wait. Ask what kind of call this is first (emergency, urgent, routine, or an estimate) and everything after that sorts itself. The same four-question order works whether a person is reading it off a card or an AI receptionist is running it word for word, because it's question design, not conversation skill. What it can't do is replace judgment once a call is sorted. It only decides where the call goes next.

What is a phone answering script?

A fixed, short sequence of questions asked in the same order on every call, before anyone tries to solve what the caller actually wants. It exists to sort urgency first and content second, because a caller who has to explain the whole job before anyone decides how fast it needs handling has already lost the seconds an emergency doesn't have.

The typical script gets built the other way around: it opens with "How may I help you today?", and the question of how urgent the call is, when it gets asked at all, comes after the caller has explained the job. That ordering feels natural because it's how a normal conversation goes, but it puts the slowest question first for the one caller who can't afford it. A phone answering script inverts that on purpose. The sort comes before the story.

What order should the questions go in?

Emergency first, then urgent, then routine, then estimate, in that order, every time. A script that asks anything else first buries the one answer that decides how the rest of the call gets handled, and asking it last means asking it too late for the calls where it matters most.

Here's the sort written out as the artifact itself: the question, what the answer decides, and what happens next. Adapt the wording to your own business; keep the order fixed.

Four questions, four destinations. A script with more branches than this is usually solving a staffing problem by adding complexity to the one part of the call that has to work in under ten seconds.

How do you keep an emergency caller on the line while you sort the call?

Acknowledge before you ask anything else. One short sentence that says help is coming, then the sorting question, then the handoff. Think about what you'd do yourself with water coming through the ceiling: silence, or a slow, generic greeting before the first real question, sounds like nobody is taking this seriously, and the next number on the list starts looking better than waiting.

That first sentence isn't the sort. It's what buys the two or three seconds the sort takes. "I hear you, let's get this handled fast" costs nothing and commits to nothing, but it changes how those seconds feel to the caller. Skip it, and a script that's perfectly ordered on paper can still lose the caller who hangs up before question one finishes.

What changes for a specific trade?

One extra branch question after the general sort, never a different sort. Plumbing asks whether water is still running. HVAC asks whether anyone in the building is at risk from the heat or the cold. Electrical asks whether there's smoke or a burning smell. Nothing else about the script changes by trade.

That branch question exists because "emergency" means something different by trade, and the general sort above can't know that on its own. It still comes after the general sort, not instead of it: the four-question order stays fixed, and the trade-specific question is what an emergency answer triggers next, not a replacement for asking it. Beyond that one branch, a trade-specific script is the same script with a different trade's name on it, and that's exactly as far as this page goes: the branch is systems logic borrowed from what each trade's emergency call actually turns on, not a claim about running one.

Does the same script work for a human answering service and an AI receptionist?

Yes, because it's question design, not conversation skill. A person reading it off a card and a system running it verbatim both need the same fixed order and the same branch logic. What differs is how forgiving each one is of a caller who answers sideways, which is worth testing before you commit to either.

A human can hear "the basement's flooding" in response to almost any question and know to jump straight to the emergency branch. An AI receptionist can do the same thing, but only if it's built to recognize the emergency inside an answer that doesn't match the question asked, not just a caller who answers the questions in order. The general after-hours math is the decision about whether to pay for either one. This script is what either one should actually be running once you have.

Don't buy this if…

Skip formalizing this if you take every call yourself and already sort by instinct. A fixed order helps most when whoever's answering isn't the person who understands your business, and a script alone doesn't fix what happens after the sort: who's actually reachable once a real emergency is on the line.

A script that routes a burst-pipe call perfectly to an on-call rotation with nobody on it hasn't solved anything; it's just found the gap faster. Get the sort right, but don't mistake it for the harder problem it sits on top of.