Start from a sample for your trade, then write it in your own words: the greeting, the questions asked on every call, answers to the questions callers ask most, what to say about price, what happens on an urgent call and how the call ends. The preview shows the whole script in order. Hear it read aloud, try it on a simulated call, then download it or copy it.
A call script is not a speech read word for word. It is the set of lines and decisions a receptionist falls back on: how the call opens, what it always asks, what it says to the questions that come up every week, what it says about price, and what happens when a call cannot wait. Written down, those lines are also the brief for whoever sets up your receptionist, person or software.
The builder keeps the parts in the order a caller hears them. Each part has guidance next to it, and several parts check your wording as you type, for example a price answer that names a number, a greeting that never says it is a virtual receptionist, or a question the simulation would answer some other way.
Callers hear the whole greeting before they can say anything, so keep it short: the business name, what the caller is talking to, and one question that hands them the turn, such as how can I help.
Say it is a virtual receptionist. Callers should not have to guess whether they reached a person, and a receptionist that says what it is sets up the rest of the call honestly.
If calls are recorded, say so at the start, before the caller shares anything. A Chleb receptionist keeps recordings and transcripts of calls, and section 934.03 of the Florida Statutes makes recording a call lawful when all parties to it have given prior consent. A short line such as this call may be recorded is common practice. Whether it gives enough notice for your business is a question for your attorney; this page is not legal advice.
Every question is time the caller spends on the phone, so ask only what the next step needs. A name and a callback number are always asked, because the receptionist cannot book or call anyone back without them. A service address matters for businesses that go to the customer; whether a caller is new or existing matters for practices and firms. The reason for the call, in the caller's words, is what your team reads first.
When the simulation on this page books, it offers open times from the sample calendar and reads the details back before booking. It is a habit worth asking for at setup, because it lets a caller fix a wrong digit or a misheard street before it reaches your schedule.
Pick the three to five questions your front desk answers every week, such as weekend work, insurance, parking, warranties or financing. Write each answer in one or two sentences and leave out anything that changes often, such as a sale price.
The builder takes the key words from each question so the simulation can recognize it when a caller asks, and it leaves out words your callers also use when they ask for a service, so a booking request is not answered with the parking policy. For each question it tells you whether the simulation gives your answer as written, or answers another way, for example a question about hours, which is answered from your hours.
The price answer is said on every price question, word for word, so it is the one line in the script that can cost you money. Never promise a price you cannot honor. A number, a range, or a word such as free or guaranteed becomes something every caller can hold you to, whatever the job turns out to be.
A safer answer explains how the price is set instead of naming a figure: a firm price after the visit, before any work starts, or a callback from the person who quotes. If you leave the answer blank, the simulation says the price is confirmed after the visit, without naming a number.
An urgent call needs two things from the script: who it goes to, and what the caller hears will happen next. Name the person in plain words, such as the on-call technician, and choose how they are reached: a live transfer, a text with the caller's details, or a message for a callback. Do not promise a response time the person on call cannot keep.
The closing line should end the call in a sentence. Thank the caller by the business name and stop.
Hear it reads the script aloud in the voice your browser provides, usually one built into your device, which is not the voice of the production receptionist. When the browser has only an online voice, the page says so next to the button, because the script text then goes to the browser maker to be read. Questions about the live receptionist: call (813) 694-8671 or book a demo.
Try it runs a simulated call that uses your greeting, your answers and your price answer word for word, with services, hours and a sample calendar from a fictional business in your trade. It follows your choice of who takes urgent calls and how they hear about them, and asks for the service address and whether the caller is new or existing only when those questions are on. The rest is in its own words: how it asks for details, what it tells an urgent caller and how it says goodbye. At setup, Chleb builds the call flow from your actual services and pricing and runs test calls before your number goes live, so bring the downloaded script to that conversation.
Your script is the brief. At setup, Chleb builds the call flow from your actual services and pricing and tests it with calls before your number goes live. If part of your script does not fit a workable flow, you hear that before you sign.
Yes. Saying it is a virtual receptionist in the first sentence means no caller has to wonder whether they reached a person. It takes a few words and sets up the rest of the call honestly.
No. Hear it uses the voice your browser provides, so it sounds like your phone or computer, not like the production receptionist. Questions about the live receptionist: call (813) 694-8671 or book a demo.
The receptionist answers in US English, so write the script in English.
Chleb does not receive it, and the page does not save it. The script stays in this browser tab until you download or copy it, and closing or leaving the page discards it. Two browser features are the exception. If your browser has no voice of its own on your device, reading aloud, in Hear it or for the replies in Try it, uses the browser maker's online voice, which receives the text it reads; next to Hear it, the page tells you when that is the case. The microphone in Try it uses your browser's speech recognition, which in some browsers, including Chrome, sends the audio to the browser maker.