10:40 p.m., fifth drink, hand already up
He's been at the bar since seven. Pleasant all night, tipped well on the first round, told the bartender about his daughter's wedding. Somewhere around nine-thirty the sentences started running together, and he's now signalling for another.
The bartender is twenty-six, four months in, and knows the answer. What she doesn't have is the sentence.
So she says: "I think maybe you've had enough for tonight."
And he says, entirely reasonably from where he's sitting, "I'm fine. I've had four drinks in three and a half hours. I'm not drunk."
Now they're having a debate about whether he's intoxicated, in front of eleven people at the bar, with a man who by definition cannot assess the thing they're debating. She's already lost, and the only routes out are backing down or escalating.
Three problems at once, and the usual tool is broken
Most difficult conversations have one hard feature. This one stacks three.
It's a legally required refusal. In most jurisdictions, continuing to serve a visibly intoxicated person carries liability for the server and the business, and in some places personal liability for the individual pouring. This isn't a customer service judgment call with a compliance overlay. It's an obligation with a hospitality problem attached.
The counterparty cannot process the reason. Everywhere else in this series, explaining well is the skill — name the problem, give the rationale, bring the person along. Impairment removes the ability to weigh a rationale, and reduced inhibition makes argument more likely rather than less. You cannot reason someone into accepting that they're too impaired to reason. The tool that works everywhere else is the one thing guaranteed to fail here.
And it's public. Other guests are watching, some of whom are drinking, all of whom are forming a view about how this bar treats people. A refusal handled as a humiliation is the version that gets filmed.
The move: take it off the person
The failure in the opening scene is a single word — you. "You've had enough" is a verdict about a person, and it's arguable. The workable version is about the server's own obligation, and it isn't.
"I'm not able to serve you another one tonight."
Not a judgment of his state. Not a negotiation. A statement about what the person behind the bar can do. He can dispute his own sobriety all night; he can't dispute what she's permitted to pour.
Around that one sentence, five supports:
Decide before you speak. The decision is made privately, ideally with a second person, before any approach. Staff who appear to be deciding in the moment invite a negotiation, and a refusal that looks reversible will be tested.
Never debate the evidence. No counting drinks, no "you're slurring," no citing behavior back at him. Every one of those is a claim he can contest, and contesting it in front of an audience is worse for everyone than the original refusal.
Substitute rather than terminate. "I'll get you a water and something to eat — kitchen's open for another twenty minutes." Keeping a guest in the room, seated and eating, is safer than clearing them onto the street, and it converts a refusal into a different kind of service.
Arrange the exit before it's needed. A ride, a phone call, a friend at the table. This is where duty of care actually lives, and it's the step most often skipped because the refusal itself absorbs all the attention.
Bring a second person early. Not as muscle — as presence. A colleague standing nearby before the conversation starts prevents more escalation than any intervention after it begins.
Tell the whole team. A refusal that holds at one station and not another isn't a refusal; it's an inconvenience, and he will simply order from the server at the far end. This is the most common practical failure and it's purely a communication problem.
Four ways it goes wrong
The debater argues the facts. Unwinnable by construction, and it puts the guest's dignity on the table in public.
The one-more-then-stopper serves a final drink to avoid the confrontation and refuses the next one. Every subsequent refusal is now negotiable, because the guest has learned that persistence produces a drink.
The solo hero handles it alone at a busy bar with no colleague nearby and no manager told.
The punisher delivers the refusal with a moral edge — you've clearly had plenty — which converts a legal obligation into a humiliation. This is the version that produces aggression, and it usually comes from a tired server at the end of a long shift.
Why current training doesn't get there
Certification teaches the law and the signs. Responsible-service programs cover liability, standard drinks, and the physical indicators of intoxication. That content is necessary and often mandatory. It ends precisely where the difficulty begins.
The signs are the easy part. Staff are generally good at identifying who shouldn't be served. What they lack is the sentence, delivered to a specific person, in front of a room.
Nobody practices it out loud. It's covered in a module, mentioned in onboarding, and then the first live refusal happens on a Friday at 10:40 p.m.
And peer role play produces a caricature. Asked to play an intoxicated guest, colleagues perform comedy drunkenness — exaggerated, slurring, obvious. Real impairment at the refusal threshold is usually subtle: coherent, articulate, mildly insistent, and entirely convinced of their own sobriety. Staff who rehearse against the caricature are prepared for the version that's easy to spot and unprepared for the one that argues well.
What intoxicated guest de-escalation training should rehearse
A simulation can hold the articulate, plausible, persistent register that peers can't — and run it enough times that the sentence is automatic rather than invented. Foretell AI provides the counterparty configuration, transcripts and rubric-based scoring; the service policy and the legal thresholds stay where they belong, with the operator.
Four to build:
- The affable persister, warm and friendly, who asks four times in four different ways and never raises his voice. The most common and the hardest to hold against.
- The aggressive turn, where refusal flips a pleasant guest into a hostile one within seconds.
- The advocate — a friend or spouse who intervenes: “come on, he’s fine, it’s one drink.” Splits the refusal across two people and is rarely rehearsed.
- The station-shopper, who accepts the refusal, waits, and orders from someone else. Tests whether the staff member communicated it to the team.
Design caution. This scenario touches alcohol-related harm and legal liability. Scenario content should reflect the operator's actual policy and jurisdiction rather than invented thresholds, the debrief matters more than the score, and the exercise rehearses the conversation only — it is not a substitute for any legally required certification.
Designing the module
Pass one — the sentence. A cooperative guest. Score whether the refusal was framed as the server's obligation rather than the guest's state, and whether any evidence was cited.
Pass two — the persister. Score whether the refusal held across repeated asks without the server re-explaining or softening into ambiguity.
Pass three — the advocate. Score whether the server held the line with a third party while keeping the original guest's dignity intact.
Rubric on observable behavior: Was the refusal phrased as capability rather than verdict? Was the guest's condition debated at any point? Was a substitution offered? Was transport addressed? Was a colleague involved before the conversation started? Was the team told?
The operator case
The liability is direct and insurable in ways other guest conversations aren't. Over-service claims attach to the business and sometimes to the individual. This is the one scenario in the hospitality set where a risk manager is as interested as an L&D director.
Certification proves knowledge, not behavior. Every operator can evidence that staff completed responsible-service training. Almost none can evidence that staff can actually deliver a refusal — which is the thing that matters if an incident is ever examined.
Consistency across the team is the practical failure point. Most over-service happens not because one person misjudged but because a refusal didn't travel across stations.
And it's a safety issue for staff. Refusals are among the highest-risk interactions front-line hospitality workers face. Preparation is a duty of care to the people delivering it, not only to the guest.
For hospitality programs, this is a valuable scenario because the correct approach contradicts the instinct the rest of the curriculum builds: here, explaining your reasoning makes it worse.
Frequently asked questions
How do you cut off a drunk customer? State it as your own obligation — "I'm not able to serve you another one tonight" — rather than as a judgment about them. Don't debate their condition, offer food and water, arrange transport, and make sure the rest of the team knows.
What do you say when a guest insists they're not drunk? Don't engage the claim. Their sobriety is arguable; what you're permitted to serve isn't. Repeat the same sentence without adding new reasons.
Should you explain why you're refusing service? A brief reference to your obligation, once. Extended explanation invites a debate you can't win with someone whose judgment is impaired, and it makes the refusal look negotiable.
Who else needs to know about a refusal? Everyone working the floor and the bar. A refusal that holds at one station and not another is simply a delay, and station-shopping is the most common way over-service actually happens.
The short version
The instinct is to explain. Explaining is the one thing that cannot work, because the person you're explaining to is impaired in exactly the faculty the explanation requires — and because the moment the conversation becomes a debate about his condition, it's happening in front of an audience and there's no graceful exit.
"I'm not able to serve you another one tonight." One sentence, about your obligation rather than his state, said the same way every time it's tested. It's short enough to memorize and hard enough that almost nobody delivers it well the first time.
Foretell AI lets operators build conversational simulations — including service refusal, over-service risk, and bar de-escalation scenarios like the one above — with configurable guest counterparties, transcripts, recordings, and rubric-based evaluation. If you're closing the gap between responsible-service certification and rehearsed refusal, we're happy to walk through how other operators have structured it.