Greetings & Scripts
What Is a Call Script?
A call script is the written flow a receptionist, answering service, or AI follows on every call. It covers the greeting, the questions to ask, how to tell a real lead from someone just browsing, and how to end the call with a booking or a message. It makes every call sound the same, no matter who picks up.
Key Takeaways
- Every script has four parts: greeting, intake, qualifying, and close.
- The close is where the money is. A script that ends with "someone will call you back" leaks jobs.
- Scripts should branch. An emergency call and a quote request should not follow the same path.
- An AI receptionist is set up from the same script a human would use, just written as questions and if-then rules.
How a Call Script Works
A call script is a map of the conversation. It tells whoever answers what to say first, what to find out, and how to end. Most scripts have four parts, in this order:
- Greeting. Name the business and who is speaking. "Thanks for calling Ridgeline Plumbing, this is Sam." Short and warm. This is where the caller decides they reached the right place.
- Intake. Collect the basics: name, callback number, address, and what the caller needs. This is customer intake, and the script lists the questions so none get skipped.
- Qualifying. One or two questions that sort the call. Are they in the service area? Is it an emergency or a quote? Is it a system you work on? This is lead qualification built into the flow.
- Close. End with an action. Book the appointment, transfer the urgent call, or take a message with a promised callback time. The close is the whole point of the call.
Good scripts branch. An emergency call skips the quote questions and follows the call escalation rules straight to the on-call tech. A quote request skips the emergency questions and goes to the calendar. The branches are usually written as simple if-then rules.
An AI receptionist runs on the same script. The greeting becomes its opening line. The intake and qualifying questions become the custom questions it asks on every call. The if-then rules tell it when to book, when to transfer to a forwarding contact, and when to switch to message taking.
Example of a Call Script
A two-truck plumbing company writes this script:
- Greeting: "Thanks for calling Ridgeline Plumbing. How can I help?"
- Intake: Name, phone, address, what is going on.
- Qualifying: "Is water leaking right now?" and "What city are you in?"
- Close: If leaking, transfer to the on-call tech. If not leaking and inside the service area, offer the next open slot on the calendar. If outside the area, say so kindly and end the call.
A homeowner calls at 2 pm about a slow bathroom drain. The script collects her name and address, confirms she is in the service area, confirms it is not an emergency, and books her for 9 am tomorrow. The call takes about two minutes. The job bills at $400. A second caller has a burst pipe. The script skips the calendar and sends the call straight to the tech. Same script, two paths, both callers handled.
What People Get Wrong About Call Scripts
Owners put all the care into the greeting and none into the close. They write three versions of "Thanks for calling," then end the script with "take a message and someone will call back." That close loses jobs. The caller hangs up with nothing, and the callback has to beat the next plumber she dials.
The greeting is the part the caller forgets. The close is the part they act on. A script that ends with a booked time, or a live transfer, or at least a specific callback window, turns the call into a job. A script that ends with a message turns it into a to-do.
The fix is to write the close first. Decide what a good outcome looks like for each type of call: booked, transferred, or a message with a time attached. Then work backward and write only the questions you need to reach that outcome. Most scripts get shorter when you do this, and the calls get better.
Call Script vs. Phone Greeting vs. Auto-Attendant Menu
- A call script is the full flow of a live conversation, from hello to the close.
- A phone greeting is just the first line. It is one part of the script, and it also stands alone as a recorded business hours message or voicemail greeting.
- An auto-attendant menu is a recording that asks callers to press a number. It routes calls, but it does not ask questions or qualify anyone. A script picks up where the menu leaves off.
Why It Matters
A call script is how a two-person shop sounds like a company with a front desk. Every caller gets the same questions, nobody forgets to ask for the address, and every call ends with an action instead of a promise. It also makes training fast. A new hire or an AI receptionist can follow the same page on day one, and the owner can read the call summaries to see if the script held. For wording you can copy, see professional phone greeting examples.
The Bottom Line
A call script is the written flow for every call: greeting, intake, qualifying, close. It keeps calls consistent no matter who answers, and it is the same document an AI receptionist is set up from. Write the close first, keep the questions to the ones you need, and make sure every path ends in a booking, a transfer, or a message with a time on it.
Frequently Asked Questions
- What should a call script include?
- Four things, in order. A greeting that names the business and whoever is answering. Intake questions that collect name, phone, address, and what the caller needs. One or two qualifying questions that tell you if this is a job you want, like the service area or the type of system. And a close that books the job, transfers the call, or takes a clear message with a callback time. Keep the whole thing short enough to fit on one page.
- How do you write a call script for an AI receptionist?
- The same way you would for a new hire, just more literal. Write the greeting word for word. List the intake questions in order. Write the rules in plain if-then form: if the caller is outside the service area, say this; if it is an emergency, transfer to this contact. Add the facts the AI needs, like hours, prices, and services. Cira is set up this way, and its onboarding team helps you build it at no extra cost.
- Should a call script sound scripted?
- No. The script is a checklist, not a speech. A good one tells the answerer what to find out and what to do next, and leaves the exact words flexible. Read a stiff script out loud and you can hear the problem. Callers with a flooded basement do not want a sales pitch. They want to know someone is coming. Write the script so that answer comes fast, then collect the details.
Never miss another call
Cira answers every call, books jobs, and texts you the details while you work.