Phone Scripts Your Staff Will Actually Use

Most restaurant phone training fails for the same reason: somebody writes a polished paragraph, tapes it next to the phone, and expects a nineteen-year-old host to deliver it while three parties are waiting to be seated. It does not survive first contact with a Friday rush.

What actually survives is short lines. Five to twelve words, said the same way every time, until they become muscle memory. This article gives you those lines for the six calls your restaurant gets over and over, plus the two habits that prevent most order errors. Steal them, edit them into your own voice, and print them on one page.

Why scripts feel fake — and how to fix that

The objection is fair. Nobody wants their restaurant to sound like a call center. But the goal of a script is not to make staff sound like robots; it is to remove the pauses where staff have to invent something under pressure. Those pauses are where callers get put on hold, where the upsell gets skipped, and where "medium" gets written down as "large."

Three rules keep a script human:

The greeting: three parts, four seconds

A good greeting does three jobs — confirms they dialed correctly, gives them a human, and sets the direction of the call.

"Thanks for calling Mario's, this is Dani — pickup or a question?"

That last half — offering two doors — is the part most restaurants skip, and it is worth more than the pleasantry. It sorts the call in one second instead of thirty. Callers who want to order say "pickup" and you go straight to the order. Callers with a question ask it immediately instead of easing into it.

If you take reservations too, make it "pickup, reservation, or a question?" Do not add a fourth option. Three is the ceiling for what someone processes on the phone.

The six calls you get every day

1. "How long is the wait?"

The instinct is to guess low so they still come. That instinct costs you the customer twice — once when they wait longer than promised, once when they tell someone.

"Right now about 25 minutes. Want me to take your name?"

Give a real number, then immediately offer the next step. A wait quote without an action attached is just bad news.

2. "Are you busy right now?" (the pickup timing call)

"We are — a pickup order is running about 30 minutes. Want to order now for 7:15?"

Turning a capacity problem into a scheduled order keeps the ticket and gives the kitchen a slot it controls.

3. The order itself

This is where money is made or lost, and where the two habits below matter most. The one line to standardize is the close, not the open:

"That's a large pepperoni and a Caesar, 20 minutes, under Marcus — anything to drink?"

Notice the drink question comes after the read-back, not during the order. Asking mid-order interrupts the caller and creates errors. Asking at the close feels like service.

4. "Do you have anything gluten free / vegan / nut free?"

"We do have options — let me be exact so I don't get it wrong. One second."

Say what is true and go check. Guessing on allergens is the one place where speed is worth nothing. Train staff that "let me be exact" is always an acceptable answer.

5. The catering or large-party call

These are your biggest tickets and they are the ones most likely to get handled badly, because they arrive mid-rush and nobody on the floor owns them.

"That's great — I want to get this right. Can I take your name and number and have Sam call you back within the hour?"

Then actually write it somewhere that gets seen. A callback promised and missed is worse than no callback.

6. "Are you open on Sunday?" / hours and directions

"Sunday we're open 11 to 9. Anything else I can grab for you?"

Short answer, then one open door. A surprising number of hours calls turn into orders when you leave the door open.

The two habits that prevent most errors

Everything above is polish. These two are the actual fixes.

The read-back. Repeat the complete order — items, sizes, modifiers, name, and time — before you hang up. Every time, including when you are certain. Most phone-order mistakes are not exotic; they are a size, a modifier, or a missing name, and every one of them dies at the read-back. It costs fifteen seconds and saves a remake plus an apology.

The name and number, first. Take the caller's name and phone number at the start of an order, not the end. Calls drop. Rushes interrupt. If the line goes dead after the order is placed and you have nothing written down, that ticket is gone. If you have a number, you call back and the customer is impressed instead of annoyed.

Make it stick in one week

That last exercise is where most operators find the real gap: the script is fine, but nobody can get to the phone during the rush. If that is what you hear, the fix is coverage, not wording — either someone owns the phone as a station, or something answers when nobody can. That second option is what Ring to Kitchen AI does: it picks up every call in English and Spanish, does the read-back, and sends the complete order to the kitchen. For a deeper look at what the direct channel is worth, see the margin math on phone orders versus delivery apps.

The takeaway

Good phone service is not charisma. It is six short lines, said the same way every time, plus a read-back nobody skips. Write them in your own voice, put them on one page, and coach one line a week.

Want help running your restaurant's numbers? Book a free 15-minute call and we will do the math with you — no pitch unless it makes sense.