What to Say: Scripts for the Five Hardest Front Desk Conversations

Why scripts — and why they don’t make you robotic

Objections to scripts usually come from imagining the bad kind: a page of canned lines read in a flat voice. That is not what works. What works is scripting the first two sentences of each hard conversation — the moment where an untrained response does the damage — and letting the human take it from there.

The first sentences matter disproportionately because they are spoken under pressure. A price question, a complaint, a demand for a same-day slot — each triggers a small panic in an untrained team member, and panicked answers hedge, over-apologize, or over-promise. A rehearsed opening removes the panic; everything after it can be natural.

1. The price shopper: "How much is…?"

The instinct is to dodge — "it depends, you’d have to come in" — because you are afraid the number ends the call. In practice the dodge ends more calls than the number does: a caller who cannot get a straight answer assumes the answer is bad, and dials the next place on their list.

"Great question — that service is [price], and it includes [the one or two things that make it worth it]. Were you thinking about booking this week? I can check what we have open."

• Give the number in the first sentence. Attach the value in the same breath, not as a defensive follow-up.
• If pricing genuinely varies, give the honest range and what moves it: "Most clients are between X and Y depending on [factor]."
• Pivot immediately to availability. Price shoppers are ready buyers doing their homework — the pivot converts homework into a booking.

If your team cannot state prices confidently, the problem is usually upstream of the script — packages that are too complicated to quote. That is a pricing-design problem, covered in service & pricing packages.

2. The squeeze-in: "Can you fit me in today?" (when you’re full)

The wrong answers are a flat "sorry, we’re fully booked" (a dead end) and a stressed "let me see what I can do" followed by double-booking your own team (a worse one). The right answer holds the line on the calendar while keeping the demand.

"Today is fully booked, but cancellations do happen — I can put you first on today’s waitlist and text you the moment something opens. And I have [specific day/time] open if you’d rather lock something in now."

• Always pair the waitlist offer with the next concrete opening. Some callers want certainty more than speed.
• Take the waitlist seriously as an operation, not a sticky note — capture the window they can make, their service, and the channel to reach them fast, and actually work the list when a slot opens.
• Never say just "no." A full calendar is a good problem; a caller turned away with nothing is how the good problem quietly becomes churn.

3. The repeat late-canceller

This conversation goes wrong in both directions: teams either avoid it forever (and eat the cost) or deliver it coldly (and lose a client who might have reformed). The script threads the needle by being warm about the person and firm about the pattern.

"We’d love to keep seeing you — and I have to be upfront: we’ve had a few last-minute cancellations on your account, and those slots are ones other clients asked for. Going forward we’ll need [a card on file / a deposit] to hold your bookings. Want me to set that up with your next appointment?"

• Name the pattern with numbers, not adjectives — "three of the last four" lands better than "you always."
• Attach the consequence to the booking mechanics, not to the person’s character.
• Have the policy decided before the call, so the front desk enforces rather than negotiates — aim it at the pattern, not the population, the same principle behind deposits in the no-show system.

4. The unhappy client

Complaint calls are won or lost in the first ten seconds, before any solution is on the table. The client is braced for defensiveness; the script’s job is to make the bracing unnecessary.

"I’m really glad you called us about this — tell me what happened." …then, after listening without interrupting: "That’s not the experience we want you to have. Here’s what I can do right now: [specific remedy]. Does that work for you?"

• Thank them for calling before anything else. A complaint delivered to you is a gift; the alternative is a complaint delivered to a review site.
• Let them finish. The first pause is not the end of their story.
• Offer a specific remedy, not an open question. "What can we do to make it right?" hands a stressed person homework; a concrete offer they can accept or adjust does not.
• Log it and follow up in a few days — the post-issue check-in is the highest-stakes message in your follow-up program.

5. The soft no: "I’ll think about it"

"I’ll think about it" is sometimes a real deliberation and sometimes a polite exit. The script’s job is not to overcome the objection — high-pressure closes are wrong for service businesses, where the relationship is the product. The job is to keep the door open concretely.

"Of course — it’s worth thinking over. Can I text you the details we talked about so you have them in one place? And if it helps, I can pencil you in for [day] — no charge to change or cancel it before [deadline]."

• The recap text converts a fading memory into a durable artifact — with your name, price, and booking link in it.
• The pencil-in with a free-change window converts "thinking" into a default yes. Unclaimed holds release automatically; nobody is trapped.
• Capture consent to follow up once. One considered follow-up in a few days is service; three is pressure.

Making scripts stick — for humans and AI

A script document nobody rehearses is shelf-ware. Three habits make these real:

1. Role-play each script once at hiring and once a quarter — sixty seconds per script, worst-case version of the caller.
2. Review one real hard call a week as a team: what was said, what the script says, no blame attached.
3. Rewrite any script your team keeps deviating from. Consistent deviation is field data, not disobedience.

And if an AI receptionist answers when your team cannot, it needs the same material: your prices, your policies, your escalation rules, and your tone. A system that can absorb them — and hold the same line on a 2 a.m. price question that your best staffer holds at 2 p.m. — is exactly what to test for in the buyer’s guide.