Hospitality training for a café or restaurant team: role-play scripts and a two-week plan

This is the last part of our 7-part series Guest experience at a café or restaurant. Earlier: steps of service, the first 30 seconds, large parties, serving guests with disabilities, special requests and measuring guest experience.

You can teach someone to pull a shot in an afternoon. Teaching them what to say when a guest's drink is wrong, the line is out the door and the guest is already annoyed takes longer, because reading about it doesn't help much. People learn it by saying the words out loud, a few times, before they need them for real.

That's what role-play is for. Done badly, it's an awkward performance in front of the whole team. Done well, it's ten minutes, two people and one scene, repeated until the words come naturally. This post has the format, six scripts and a two-week plan.

First: training time is work time

Before you schedule anything, a rule on pay. Under the federal Fair Labor Standards Act regulations, training only falls outside paid working time when all four conditions in 29 CFR 785.27 are met: "Attendance at lectures, meetings, training programs and similar activities need not be counted as working time if the following four criteria are met: (a) Attendance is outside of the employee's regular working hours; (b) Attendance is in fact voluntary; (c) The course, lecture, or meeting is not directly related to the employee's job; and (d) The employee does not perform any productive work during such attendance."

Role-play about your own service fails at least the third condition: it's directly related to the job. And on "voluntary", 29 CFR 785.28 says: "Attendance is not voluntary, of course, if it is required by the employer."

So plan role-play inside paid shifts, such as the pre-shift huddle. Our post on the pre-shift huddle covers the same rule. State law can add to it; check your state's rules or ask an employment lawyer.

How to run a role-play people don't dread

• Two people, not an audience. One plays the guest, one plays themselves. A lead watches. Nobody else needs to.
• Ten minutes, one scene. Run it, give feedback, swap roles, run it again.
• The guest is realistic, not cruel. Play an annoyed guest, not a monster. The point is practice, not a test of nerves.
• Use your own words. The scripts below are starting points. Each person should find a version that sounds like them, within the standard.
• Feedback: one thing that worked, one thing to try. Then run it again with that one change.
• The lead goes first the first time. It shows the team that nobody is being judged.

Six scripts

Each scene has a setup, the guest's opening line, what a good answer covers, and a sample. Tie each one to your own written standard: steps of service for the order of things, our complaint steps for what each role can offer.

1. The wait that slipped

Setup: A party of two was quoted 15 minutes. It's been 25. Guest: "You said fifteen minutes. It's been almost half an hour." Good answer covers: an apology without excuses, the real reason, a new honest time, and what you can offer. Sample: "You're right, I'm sorry. The table we expected is still finishing dessert. I think it'll be about five more minutes. Can I bring you a drink while you wait?"

2. The wrong order

Setup: A guest returns a latte made with whole milk; they ordered oat. Guest: "This isn't what I ordered." Good answer covers: taking it back without arguing, remaking it first, and checking the rest of the order. Sample: "I'm sorry about that. I'll have a fresh oat latte made right now. Was everything else right?" (Then log the remake, as in our post on order accuracy.)

3. The allergy

Setup: A guest asks if the pesto has nuts. Guest: "Does the pesto have nuts? I'm allergic." Good answer covers: not guessing, checking the matrix, and starting the allergy procedure. Sample: "Let me check that for you, not guess. ... Yes, it's made with pine nuts. I can suggest the tomato sauce, which I've checked. I'll make sure the kitchen knows about your allergy." (Follow our allergy order procedure.)

4. The service dog

Setup: A guest comes in with a dog. It isn't obvious what the dog does. Guest: "Table for one, please." Good answer covers: a welcome, the two allowed questions only, and nothing more. Sample: "Welcome in! Is that a service animal required because of a disability? And what task is it trained to do? Thank you, follow me." (See our post on serving guests with disabilities.)

5. The regular

Setup: A regular comes in. The person at the register is new and doesn't know them. Guest: "Just the usual, please." Good answer covers: honesty, warmth and learning the name and order. Sample: "I'm new, I'm Jo! I don't know your usual yet. What can I get you?" (Then learn their name and order. Our post on remembering regulars covers guest notes.)

6. The guest at closing time

Setup: Five minutes to close. The espresso machine is being cleaned. A guest walks in. Guest: "Am I too late for a coffee?" Good answer covers: a clear answer, a real option, and the guest leaving with a good impression. Sample: "We've just cleaned the espresso machine, so I can't do a latte, I'm sorry. I can do a drip coffee or a bottled cold brew, though." (Decide what's still available at closing before this happens, and write it down.)

The two-week plan

Ten minutes in the pre-shift huddle, on paid time, plus a few minutes of practice during quiet moments. Week one introduces the scenes; week two repeats them under pressure and signs people off.

After week two, keep one scene a week in the huddle. Our post on measuring guest experience tells you which one: the scene closest to this week's top complaint or remake reason.

Signing people off

A sign-off means the lead saw the person handle the scene naturally, in their own words, without prompting. Record it the same way you record station training: our training sign-off sheet has room for "Hospitality scenes 1 to 6" as its own row. And when someone handles a real guest well, say so in front of the team. Our post on feedback on the floor covers praise and coaching in the moment.

Where Mays fits

• The scripts, on every phone: put the six scenes in a Knowledge Base article so people can read them before a shift. See Knowledge base basics.
• A quiz for day 9: in Learning, an admin builds a module from that article. Generate from docs drafts multiple-choice and true/false questions from it with AI, each with the quote it came from, for you to read and edit before publishing, and you set the passing score. See Creating learning modules.
• Assigned and taken on the phone: assign the module by location, role or person, and staff take it in the Mays app. See Assigning training and Taking quizzes on mobile.
• Pop quizzes while on shift: once a module is assigned, people on a published shift who haven't passed it can get one question a day as a push notification, inside hours an admin sets. See Snap quizzes.
• Sign-offs as tasks: give the lead a one-off task per person, "Sign off: hospitality scenes"; in the phone app you can set a Due Date. See One-off tasks.

Mays can't run the role-play for you. The scenes still need two people, ten minutes and a lead who goes first.

Your hospitality training checklist

• Role-play on paid time, inside the shift
• Two people, one scene, ten minutes, one change at a time
• Six scripts tied to your own standards, in your own words
• A two-week plan: introduce, repeat, sign off
• One scene a week after that, chosen from the scorecard
• Real moments praised in front of the team, coaching in private

Train the words before the moment

Put the scripts where the team can read them, quiz them on the phone, and sign people off when the words come naturally.

Start your free trial: 30 days, every module, no card needed. Or book a walkthrough and we'll set up your first hospitality module with you.