How to Write a Receptionist Call Script That Holds Up

Most call scripts fail the same way: they read fine on paper but fall apart the moment a real caller says something unexpected. A script that holds up isn't a monologue — it's a small set of rules for what to say, what to ask, and where to draw the line.

Start with a greeting that sets expectations

Your greeting should state your business name clearly and, if relevant, briefly signal what the caller should expect — that you'll take some details and follow up, for instance. Keep it short. A greeting that runs fifteen seconds before the caller can speak makes people hang up or start talking over it.

Qualifying questions that earn their place

Every question in your script should exist because someone on your team actually uses the answer. A common failure is copying a generic intake form that asks for information nobody reads. Instead, list the two or three facts your team needs to act on a call — urgency, location, what the caller needs — and build questions around exactly those.

1. What do you need help with today? — open-ended, let them describe it in their own words.
2. Where are you located, or what's the service address? — confirms you can even help.
3. How urgent is this? — a direct urgency question, not just inferred from tone.
4. What's the best number to reach you back at? — confirmed, not assumed from caller ID.

Set boundaries explicitly

Decide in advance what your script should never promise: a specific price before diagnosis, a same-day appointment, or a guarantee about outcomes. Write the boundary as a line the receptionist can say plainly — 'final pricing depends on what the technician finds' — rather than leaving it to be improvised differently on every call.

Escalation rules that don't rely on judgment calls

Write your emergency and escalation criteria as an explicit list rather than trusting each caller's tone to signal urgency: certain keywords, symptoms or situations that should always transfer or flag immediately. This matters most after hours, when no one is around to notice a call was more urgent than it sounded.

Close with a clear next step

End every call by telling the caller what happens next — 'someone from our team will call you back within the day' is better than a vague goodbye. A caller who knows what to expect is far less likely to call a competitor five minutes later out of uncertainty.

• Greeting: business name, brief expectation, get out of the way quickly.
• Qualifying questions: only what your team will actually use.
• Boundaries: written explicitly, not improvised per call.
• Escalation: a fixed list of triggers, not a judgment call.
• Closing: tell the caller exactly what happens next.

For more on where to draw the line on transfers, see call transfer rules for small business, and for the full setup process read how to set up an AI receptionist.