Inbound Call Center Scripts: A Copy-Paste Library for Agents, Receptionists and AI

Most script libraries give you forty one-liners and stop. That helps a new agent on day one, but it does not tell you which lines callers respond to, what to avoid when someone is angry, or how to hand the same knowledge to an AI receptionist that answers the phone at 11 pm.

This page is a working library. Every script sits in its own block, with square brackets for the parts you fill in and grey notes for what the agent does. Under each one is a short note on why it works. Copy them, change the wording to sound like your business, and test them on real calls. If you are writing calls you place rather than receive, use our outbound call script templates instead.

Note: Recording notices and identity checks are shown as examples, not legal advice. The wording you must use depends on your country, industry and data protection rules. Confirm it with someone qualified before you go live.

What Makes an Inbound Call Script Actually Good?

Inbound callers already want something. Your script's job is to find out what, prove you are the right place, and get it done with as few steps as possible. Five rules separate scripts that work from scripts that sound like scripts:

• Write for the ear. Short sentences, one question at a time, no words you would not say out loud.
• Give the outcome, not just the words. "Confirm date, time and service before you book" is more useful to an agent than a paragraph of dialogue.
• Script exactly only what must be exact. Recording notices, identity checks, prices and regulated wording. Leave the rest flexible.
• Always say what happens next, and when. "You will get a text with the details in the next few minutes" ends more calls cleanly than "Is there anything else?"
• Never leave silence unexplained. If the agent is typing or checking, they say so.

Call Center Greeting Scripts

1. Standard business-hours greeting

Why it works: the caller hears they reached the right place in the first two seconds, gets a real name to use, and is asked one open question. Keep it under ten seconds. "Good morning and thank you for choosing [Business], your trusted partner in…" delays the reason for the call and adds handle time to every call.

2. Greeting for a returning caller (when your system shows who is calling)

Why it works: it confirms identity before using the record, then offers the most likely reason so the caller can just say yes. Always leave "or something else" in; guessing wrong without it feels like being ignored.

3. After-hours greeting

Why it works: it confirms the caller reached the right business, gives the hours once, and tells them exactly what to leave so the callback is useful. Promise a real time ("tomorrow morning"), not "as soon as possible".

4. Public holiday greeting

Why it works: it answers the two questions every holiday caller has, "when are you back?" and "is my booking still on?", before they ask. Record it once per holiday, or better, let the calendar switch it. In DialerBee, business-hours and holiday calendars are set per tenant and enforced by schedule gates, so the closed message plays without anyone remembering to switch it, and an SMS fallback template can go out so the caller knows they were heard (inbound contact center).

5. Arabic and English bilingual greeting

For businesses in the Gulf and the wider Arab world, the greeting should sound local, not translated. Here are two versions: a formal one in Modern Standard Arabic that works in any Arab country, and a warmer Gulf-friendly one. Each ends with a one-line English offer.

Why it works: the Arabic comes first because most callers will use it, and it is short enough that an English speaker waits only a few seconds. "حيّاكم الله" is the everyday Gulf welcome and "كيف أقدر أخدمكم؟" ("how can I serve you?") is what a good front desk in the region actually says. The English line tells English speakers they can switch without pressing anything. If your callers are evenly split, a language select step at the start of the call (a node in the IVR builder) sends each caller to an agent or voice pack in their language.

Customer Service Phone Scripts by Call Type

6. Identity verification

Why it works: it explains why before asking, uses two pieces of information, and has a polite, firm route when the check fails. Never read details out for the caller to confirm ("is your address 14 Palm Street?"); that hands the answer to anyone who asks. Never ask for a full card number or a password on a call.

7. Appointment booking

Why it works: two specific options get a decision faster than "when are you free?". The read-back catches mistakes while the caller is still on the line, and "you're booked" is only said after the system confirms it, so nobody is told a slot is theirs when it is not.

8. Rescheduling or cancelling

Why it works: "no problem at all" removes the guilt that makes people skip appointments instead of calling. Offering to move first keeps the booking; offering a new time after a cancellation saves a second call.

9. Order status

Why it works: telling the caller where to find the order number saves a minute of searching. The status comes with a date and the next step. Order status is also the most common call that never needs an agent: a self-service flow can look the order up in your own system (DialerBee's IVR builder has CRM lookup and an HTTP node for this) and only route the caller to a person if something is wrong.

10. Billing question

Why it works: it finds the exact charge before explaining anything, explains it in plain words, and asks the caller to agree. If it is your mistake, the script says so plainly and gives an amount, a method and a date. Never quote a price or refund amount you have not checked.

Complaint and De-escalation Scripts (and What Not to Say)

11. Handling a complaint

Why it works: the read-back proves the agent listened, which lowers the temperature faster than any apology. The apology is specific and the offer is concrete. When the agent cannot go further, they name who can and by when, rather than saying no.

12. When the caller is shouting

Why it works: it acknowledges the feeling, then moves the caller from venting to answering, which is a calmer state. The second line sets a limit once, calmly, with a way back. Agents should know they are allowed to use it.

What not to say, and what to say instead:

Hold, Transfer and Callback Scripts

13. Putting a caller on hold

Why it works: asking permission and giving a time turns a wait into an agreement. Coming back when the time runs out, with a choice, stops callers hanging up mid-hold and calling again angrier.

14. Transferring a call

Why it works: the caller knows why they are being moved and that they will not repeat themselves. The colleague gets name, verification status, problem and the outcome wanted in one breath. For when an AI voice agent passes a call to a person, see our human handoff playbook.

15. Callback offer when the queue is long

Why it works: a real position and a real wait let the caller decide, and "you won't lose your place" removes the fear that choosing a callback means starting over. A WhatsApp option moves simple questions out of the voice queue altogether. These are platform features, not just words: DialerBee queues can announce position and estimated wait, callers can request a callback and keep their place in the queue, and the IVR builder has a WhatsApp deflect step that sends the thread from inside the call flow.

Closing Script

16. Closing the call

Why it works: the summary is the most important line on the call. It catches misunderstandings while they are cheap to fix and tells the caller exactly what to expect, which is what stops repeat calls. "Anything else?" comes after the summary, not instead of it.

Which Script Elements Move Which KPIs?

Scripts are not just about tone. Each element has a measurable effect on the numbers your contact center already tracks. Here is where to look when you change one. For the formulas behind each metric, see call center KPIs and formulas.

Change one element at a time and compare two weeks before and after, on the same queue. Otherwise you will not know which change did the work.

AI Receptionist Script Examples: Turning Scripts into Instructions

An AI receptionist does not read a script line by line. It needs four things your scripts already contain, written in a different shape:

1. Knowledge: the facts it may answer from. Opening hours, services, prices, policies, parking, what to bring.
2. Rules: how it behaves. Tone, how long its replies are, what it must confirm before acting, what it must never say.
3. Actions: what it is allowed to do. Book, reschedule, cancel, send a confirmation.
4. Handoff triggers: when it stops and passes the caller to a person.

Here is a sample instruction block built from the scripts above, for a fictional salon. It is a template to adapt, not DialerBee's internal format.

Notice what changed. The greeting became a language rule. The booking script became four booking rules. The complaint script became a handoff trigger, because complaints and sensitive calls should go to a person by design, not after the AI has tried and failed. The "what not to say" table became the NEVER list. And every handoff trigger is decided before launch, not discovered on a live call.

Where these instructions go in DialerBee

DialerBee's AI receptionist is its AI voice agent, Layla, answering an inbound number routed to it from your DID inventory. You configure it yourself in Agent Studio, and each part of the instruction block has a home there:

• Role and tone map to the persona: name, voice, gender, tone and pace.
• Knowledge goes into the knowledge base: you upload your documents and the agent retrieves from them by semantic search. Change a document and you change what the agent knows.
• Prices come from your service catalogue. The agent speaks only prices that are in it.
• Booking actions run after a free-busy check on your Google Calendar or Microsoft 365 calendar, and an action has to return a confirming status before the agent says it is done. A confirmation can follow by SMS or WhatsApp.
• Conversation shape is set by a flow profile, and every reply passes guardrails before it is spoken.
• Handoff goes to a human agent in your own queues, on the same platform your staff already use.

Before going live, place a test call from Agent Studio and listen in the language and dialect your customers actually speak. Publish as a version, and if a change makes things worse, roll it back. Kill switches let you stop the agent at any time. The agent works in 11 languages, with Arabic handled as dialects including Gulf, Levantine and Egyptian. For the full setup, follow how to set up an AI receptionist, or see what it handles on the AI receptionist page.

Hear scripts like these on a call

These short recordings use DialerBee's AI voice agent. AI voice agent demo — simulated caller: the replies come from the production voice agent, the callers are synthetic and the businesses are fictional.

Transcripts are on the AI voice agent page. Listen for the booking read-back and the callback offer: they are scripts 7 and 15 above, in a different form.

Human Agents, AI or an IVR: Who Should Use Which Script?

Most teams end up with all three on one number: an IVR or AI receptionist for the routine calls, and staff in inbound queues for the rest, with supervisors able to listen, whisper to the agent or barge in when a call needs help.

How to Roll Out a New Script Library in Four Steps

1. Start from your top five call reasons. Pull them from last month's dispositions or call notes. Write those blocks first; they cover most of your volume.
2. Read every block out loud. If you run out of breath or stumble, shorten it.
3. Listen to ten recorded calls per block. Note where callers interrupt, repeat themselves or ask "sorry?". That is where the wording is wrong.
4. Change one thing, then measure. Use the KPI table above to pick the metric to watch.

Frequently Asked Questions

What is an inbound call center script?

It is the set of words and steps an agent uses when a customer calls in: the greeting, how to verify the caller, how to handle each common request, what to say on hold or transfer, and how to close. Good inbound scripts are short, written for the ear, and give the agent the outcome to reach rather than a speech to recite.

What is a good call center greeting script?

Thank the caller, name the business, give your first name, mention recording if it applies, and ask one open question. For example: "Thanks for calling Northside Dental, this is Sara. This call may be recorded. How can I help you today?" Keep it under ten seconds; long greetings delay the reason for the call.

What should a receptionist say when answering the phone?

The business name, their own name and an offer to help, in that order. If the line is busy, add a choice instead of an open hold: "Can you hold for one minute, or would you like me to call you back?" Then confirm the caller's name and number early, so a dropped call can be returned.

What should you never say to an angry customer?

Avoid "calm down", "that's our policy", "there's nothing I can do", "you should have", and "I understand" on its own. Each one argues with the caller or closes a door. Name the problem, say what you can do, and give a time for the next step.

Should call center agents follow scripts word for word?

Only for the parts that must be exact: recording notices, verification, legal or regulated wording, and prices. Everything else works better as a structure with sample lines, so agents sound like people and can adapt to the caller. Review recordings to see which lines callers actually respond to.

Can I use the same scripts for an AI receptionist?

Not word for word. A human script is dialogue; an AI receptionist needs the knowledge it may answer from, the rules it must follow, the actions it may take, and the moments it must hand the call to a person. Your scripts are the best raw material for writing those, as the sample instruction block on this page shows.

How do I greet callers in Arabic and English?

Lead with the language most of your callers speak, keep each version short, and tell callers how to switch. In the Gulf, a warm Arabic greeting such as "حيّاكم الله في" followed by the business name and a one-line English offer works well. An IVR language select step or an agent who answers in the caller's language avoids making people repeat themselves.

How long should an inbound call script be?

Each block should fit in one or two breaths: a greeting under ten seconds, a hold message under fifteen. The whole library can be long, because it covers many call types, but any single call should only use the few blocks it needs.

The Bottom Line

Good inbound scripts are short, specific and honest about what happens next. Use the blocks above for your agents, write the parts that must be exact word for word, and turn the rest into rules, knowledge and handoff triggers when you hand routine calls to an AI receptionist. If you want to hear your own scripts running on a call, with bookings in your calendar and handoffs to your team in the same system, book a demo and we will set up the number for you, or start a 14-day free trial with your own SIP trunk or PBX. The AI voice agent is billed at $0.60 per started connected minute on managed AI, added to the Professional or Enterprise plan; full details are on the pricing page.