Businesses tend to evaluate answering services on the service. In practice the thing that determines whether the arrangement works is the script — the document telling operators what to say, what to ask, and what to do with the answers. A good team working from a vague script produces polite, useless messages. An ordinary team working from a precise one produces messages you can act on from a truck or between patients.
The script is yours to write, and it is worth an hour. Here is what goes in it.
Start with the greeting
Write the opening line exactly as you want it heard, word for word, rather than describing it. "Answer with our company name" produces five different greetings from five operators; a written line produces one.
Decide two things while you are at it. Should the operator identify themselves by name? Most businesses prefer yes, because a named person feels accountable. And should the greeting reveal that this is an answering service? Many businesses prefer that callers simply reach a helpful person; others in regulated fields prefer transparency. Either is defensible, but it should be a decision rather than an accident.
Write the questions that change the outcome
This is the heart of the script and the part most often left generic. A message saying a customer has a problem and would like a call back tells you nothing you can act on. The right questions are the ones whose answers change what you do next.
The test for including a question: if the answer would change whether you go out tonight, who you send, or what you take with you, it belongs in the script. If it would not, it is padding that lengthens the call.
For a trade business that usually means the nature of the fault, whether anything is actively causing damage, whether the property is occupied, and access. For a medical practice it means the caller's relationship to the patient, what has changed and when. For a law firm it means the matter type and whether a deadline is involved. Our posts on property management call scripts and restoration call intake work through two of those in detail.
Order matters
Put the urgency question early. If the third question establishes that this is an emergency, the operator has spent two questions on the wrong path and the caller has spent them getting more anxious. Ask what is happening before you ask for a spelling of a surname.
Define urgency in the caller's words, not yours
Every script needs a rule for which calls are urgent. The mistake is writing that rule in your professional vocabulary. An operator cannot apply a category the caller will never use.
Write the classification from what people actually say. Not "category one fault" but "the customer says they can smell burning" or "the caller says water is coming through the ceiling". Those are observable in the sentence a caller offers unprompted, which means an operator can act on them without interpreting anything.
Keep the tiers few. Two or three categories get applied consistently; six do not.
Say what operators may resolve themselves
A script that only permits message-taking guarantees message-taking. If operators may book appointments, quote your hours, confirm your service area, or explain your process, say so explicitly and give them the wording.
The highest-value addition here is a short list of the questions your customers ask constantly, with the answers you want given. A dozen approved answers turns the service from a message desk into something that actually helps the caller — and stops a call from becoming a callback.
Be equally explicit about the other side. Name what operators must never do: quote a figure, commit to a time you have not agreed, offer an opinion on a medical or legal matter. Clear limits make the permissions safe to grant.
Write the escalation path, including the failure case
Who is contacted, in what order, and how long the operator waits before moving on. Most scripts stop after the first name. The one that matters is the second and third, because the arrangement is judged on the night the first contact does not pick up.
State what happens if nobody answers at all — a repeat cycle, a supervisor, a partner firm, or a defined message to the caller. Silence is not an acceptable outcome for an urgent call, and if you do not choose an answer the operator will have to.
Specify delivery
Who receives which messages, by which channel, and when. Routine messages batched to email in the morning; urgent ones by text or a call through, immediately. Name a second recipient for when the first is unavailable, and name at least one channel that does not depend on your office network.
Five things that make a script fail
- 1Writing it in internal jargon. If a phrase would not survive being read aloud to a stranger, it does not belong in a script.
- 2Too many questions. Every question added is time an anxious caller spends answering rather than being helped.
- 3No failure path. Everything after the first unanswered contact is improvisation.
- 4Never updating it. Rosters change and people leave; a script naming someone who left last year works perfectly until it does not.
- 5Copying the old provider's script wholesale when you switch. If it was wrong, you have faithfully reproduced the problem.
Test it out loud
Before you sign anything, read the script aloud as though you were the operator, with a colleague playing an upset customer. Awkward phrasing, missing branches, and questions in the wrong order all surface within a few minutes and are invisible on paper.
Then place a real test call once it is live, describe a situation that should escalate, and follow it all the way to the phone that was supposed to ring. The gap between what the script says and what happens is only visible if you walk the whole route.
Answering365 builds the script with each client rather than handing over a template. To work through yours, call 888-588-9800 or get in touch — and see live answering for how the calls are handled once it is written.
