What Not to Say — And What to Say Instead
Every server has said something that landed the wrong way. Sometimes it's a phrase that felt natural in the moment but left the guest uncomfortable, pressured, or simply put off.
This repository identifies the language patterns that damage the guest experience, explains why they fail, and provides better alternatives for each situation.
Use this guide in staff training, pre-shift briefings, and performance coaching. The goal is not to restrict your team's personality — it is to sharpen their awareness of how words land from the guest's perspective.
How to Use This Guide
Phrases are grouped by the type of harm they cause. Each section includes the problematic phrase, an explanation of why it fails, and one or more alternatives that achieve the same goal without the damage.
Category 1: Pressure Phrases
Language That Makes Guests Feel Coerced
These phrases create discomfort by implying the guest is making a wrong or inadequate choice. Even when said with good intentions, they put the guest on the defensive.
1.1 Spending Pressure
Never say:
✗ "Do you want to spend more?"
✗ "It's only a few dollars more."
✗ "It's not that much extra."
✗ "That's very affordable."
✗ "For the price difference, it's really worth it."
✗ "You might as well upgrade — the difference is minimal."
✗ "Most people go for the premium option when they see the price gap."
✗ "It's a small price to pay for something much better."
✗ "You won't even notice the difference on the bill."
Why it fails: Referencing money directly puts the guest in an awkward position. It implies they may be making a decision based on cost — which many guests find embarrassing — or it pressures them to spend more than they intended. It also signals that the server is focused on the bill rather than the experience.
Say instead:
✓ "The [upgraded option] has a richer flavour — many guests find it worth it."
✓ "The difference with the premium version is [specific quality] — would you like to try it?"
✓ "Both are excellent — it really depends on whether you'd like something a little richer."
✓ "I'm happy to tell you more about either option if it helps you decide."
1.2 Obligation Language
Never say:
✗ "You should upgrade."
✗ "You need to order..."
✗ "You have to try the..."
✗ "I'm telling you, you must get the..."
✗ "Trust me, you need this."
✗ "Everyone orders that — you should too."
✗ "You really ought to add..."
✗ "I would strongly recommend you get..."
Why it fails: Guests do not take instructions from servers. Obligation language removes the guest's sense of agency and replaces a recommendation with a directive. It also puts the server in an inappropriate position of authority over the guest's personal choices.
Say instead:
✓ "If you enjoy [flavour profile], that would be a lovely addition."
✓ "Many guests who order that also enjoy..."
✓ "It's worth knowing that [dish] pairs really well with..."
✓ "I'd be happy to suggest a pairing if you'd like one."
1.3 Urgency and Scarcity Manipulation
Never say:
✗ "You need to decide now — it sells out fast."
✗ "We only have two left, so I'd order it quickly."
✗ "Everyone's ordering it tonight — I can't promise it'll be available later."
✗ "It's going fast."
✗ "Last chance to get it tonight."
✗ "I wouldn't wait too long if you want that."
Why it fails: Manufactured urgency is a manipulation tactic. Guests who feel rushed make uncomfortable decisions and often feel buyer's remorse. If a dish is genuinely limited, it can be mentioned once, factually, without pressure.
Say instead:
✓ "Just so you know, the [dish] is available in limited quantities tonight."
✓ "That's a popular choice — I can check availability if you're interested."
✓ "The [dish] is seasonal, so it's worth trying while it's on the menu."
Category 2: Shaming Phrases
Language That Makes Guests Feel Embarrassed or Judged
These phrases are often said without any intention to shame, but they carry an implied criticism of the guest's order, appetite, or choice.
2.1 Portion Shaming
Never say:
✗ "Are you sure that's enough food?"
✗ "You won't be full with just that."
✗ "That's a small portion — most people add something."
✗ "That doesn't come with a lot."
✗ "That's quite a light meal."
✗ "Are you sure one course is enough?"
✗ "Most people don't just get the one course."
✗ "That's really more of a side dish than a main."
✗ "A lot of guests find they're still hungry after that one."
✗ "It won't take long to eat that."
✗ "You might find that a bit small."
✗ "That's not very filling on its own."
Why it fails: Comments about portion size touch directly on appetite, body image, and personal budget — all sensitive areas. A guest who is watching what they eat, managing dietary needs, or simply not very hungry will feel judged and uncomfortable. This is particularly damaging in international contexts where eating habits vary enormously across cultures.
Say instead:
✓ Say nothing, and let the guest order what they want without comment.
✓ "Of course — and if you'd like anything else later, I'm happy to bring it."
✓ "We also have some lighter sides if you'd like something alongside."
✓ "Shall I leave the menu in case you'd like anything to follow?"
2.2 Choice Shaming
Never say:
✗ "That's an interesting choice."
✗ "Most people don't order that."
✗ "That's not our most popular dish."
✗ "Are you sure about that one?"
✗ "Not many people go for that."
✗ "That's a brave choice."
✗ "I wouldn't normally recommend that one."
✗ "It's an acquired taste."
✗ "You might not enjoy it if you haven't had it before."
✗ "That's quite unusual."
✗ "Just checking — you know what's in that?"
Why it fails: The guest has made a decision. Questioning it implies their taste or judgment is wrong. Even phrases meant as helpful warnings — like "it's quite unusual" — can come across as condescending. If there is a genuine allergy or preference concern, there is a right way to address it.
Say instead:
✓ "Wonderful choice — that's a really [specific quality] dish."
✓ "Great — is there anything about the dish you'd like to know before I put it in?"
✓ If genuinely concerned about preference: "Just so you know, that dish has quite an intense [flavour/heat level] — I want to make sure it's what you're looking for."
2.3 Regret Language
Never say:
✗ "You'll regret it if you don't try the..."
✗ "You'll wish you'd ordered the..."
✗ "Most people who don't get it end up wishing they had."
✗ "Don't say I didn't warn you."
✗ "You're going to be jealous when you see theirs."
✗ "I always feel sorry for people who miss out on that."
✗ "That's a decision you might second-guess later."
Why it fails: Predicting that a guest will feel regret is manipulative. It creates anxiety around what should be a pleasurable experience and implies the server knows the guest's preferences better than they do. It also creates an uncomfortable dynamic if the guest does later feel they made the wrong choice.
Say instead:
✓ "If you'd like a recommendation, I'm happy to give one."
✓ "Both are excellent — it depends on what you're in the mood for."
✓ "That's a great choice — and the [other dish] will definitely be here next time."
Category 3: Dismissive Phrases
Language That Makes Guests Feel Ignored or Unimportant
These phrases signal — often unintentionally — that the server is not fully present, not listening, or does not value the guest's custom.
3.1 Rushing the Guest
Never say:
✗ "Are you ready to order yet?"
✗ "Do you know what you want?"
✗ "Have you decided?"
✗ "We're quite busy tonight, so..."
✗ "I'll need to take your order soon."
✗ "The kitchen closes in [X] minutes."
✗ "Whenever you're ready — we are quite full tonight."
✗ "I'll come back,k but I do need your order in the next few minutes."
✗ "Can I just grab your order quickly?"
Why it fails: Guests can feel a busy restaurant without being told about it. Highlighting operational pressure transfers stress from the kitchen to the table and removes the sense of relaxed hospitality. Guests who feel rushed order less, enjoy less, and tip less.
Say instead:
✓ "Take all the time you need — I'll check back when you're ready."
✓ "No rush at all — I'll be nearby whenever you're set."
✓ "If you have any questions about the menu while you're deciding, I'm happy to help."
3.2 Dismissing Dietary Needs or Preferences
Never say:
✗ "It only has a tiny bit of [allergen] — you probably won't notice."
✗ "Most people with that intolerance are fine with it."
✗ "It's just a flavour, it's not really an ingredient."
✗ "We can't really change that dish."
✗ "That's just how it comes."
✗ "It would be really difficult to make it without that."
✗ "The chef doesn't like to change his recipes."
✗ "You could just pick it out."
✗ "I don't think there's much [allergen] in it."
✗ "Are you actually intolerant or just avoiding it?"
✗ "Is it a real allergy or more of a preference?"
Why it fails: Dietary needs — whether medical, religious, ethical, or personal — are never up for debate. Minimising an allergy is dangerous. Questioning the legitimacy of a preference is condescending. Either response erodes trust immediately and can expose the restaurant to serious liability.
Say instead:
✓ "Let me check with the kitchen exactly what's in that for you."
✓ "We take dietary requirements very seriously — I'll make sure the kitchen is fully briefed."
✓ "We have several dishes that work well for that — would you like me to point them out?"
✓ "I'll let the chef know, and we'll do everything we can to accommodate you."
3.3 Forgetting or Inattention
Never say:
✗ "Sorry, what did you order again?"
✗ "Which one was yours?"
✗ "Who had the fish?"
✗ "Was it you that wanted the..."
✗ "I'll have to check what you ordered."
✗ "Sorry — remind me what you asked for?"
Why it fails: Guests notice when they are forgotten. While these situations happen in busy service, announcing inattention out loud amplifies the problem. It signals to the guest that they were not worth remembering.
Say instead:
✓ Check the docket or notes before approaching the table wherever possible.
✓ If needed, quietly ask a colleague rather than the guest.
✓ If unavoidable: "I want to make sure I have this right — just confirming, was this the [dish]?"
Category 4: Unprofessional Phrases
Language That Undermines Credibility or Trust
These phrases reduce the guest's confidence in the server's knowledge, the restaurant's quality, or the professionalism of the team.
4.1 Undermining Menu Items
Never say:
✗ "That one's not really my favourite, to be honest."
✗ "I personally don't like that one."
✗ "That's not as good as it used to be."
✗ "The chef's changed the recipe, and it's not the same."
✗ "That's more of a filler dish."
✗ "Between us, the [other dish] is much better."
✗ "I wouldn't really order that myself."
✗ "It's fine — it's just not what we're known for."
✗ "That dish gets a lot of complaints."
✗ "People either love it or hate it."
Why it fails: Guests trust servers to guide them through the menu. Negative commentary about a dish — even casually — destroys confidence in the entire menu and in the server's ability to guide. If a guest asks for an honest opinion, there are ways to redirect without undermining.
Say instead:
✓ "Both are excellent in different ways — it depends what you're in the mood for."
✓ "If you enjoy [flavour], the [other dish] might suit you slightly better."
✓ "That's a very popular choice — and our [recommended dish] is also worth considering."
✓ If pressed for a personal opinion: "They're both dishes I'd happily recommend — the [dish] is particularly well-made at the moment."
4.2 Apologetic or Uncertain Language About the Menu
Never say:
✗ "I'm not sure if that's any good."
✗ "I haven't tried that one."
✗ "I don't really know much about that dish."
✗ "I think it's probably okay."
✗ "I'm not sure what's in it exactly."
✗ "It should be fine."
✗ "I think the kitchen can do that, but I'm not sure."
✗ "I'm pretty new, so I'm still learning the menu."
✗ "I don't know — I'll have to ask."
Why it fails: Uncertainty destroys confidence. Guests rely on servers to be the authority on the menu. While it is perfectly acceptable not to know everything, the way uncertainty is expressed matters enormously. Announcing inexperience or ignorance transfers the guest's trust problem from the server to the restaurant itself.
Say instead:
✓ "That's a great question — let me find out exactly for you."
✓ "I want to give you the right information — I'll check with the kitchen."
✓ "I'll confirm that for you right now so you can be sure."
✓ For new staff: Study the menu thoroughly before service. Ask the chef to brief you daily.
4.3 Overfamiliarity
Never say:
✗ "No worries!"
✗ "No problem!"
✗ "Sure thing!"
✗ "Yep!"
✗ "Yeah, totally."
✗ "Guys" (when addressing a mixed or formal group)
✗ "You guys ready?"
✗ "Awesome!" (repeatedly)
✗ "Cool, cool."
✗ "Literally, same." (in response to a food preference)
✗ "Oh my God, that's such a good choice!"
✗ "Babe", "Love", "Sweetheart", "Dear" (in most professional contexts)
Why it fails: Tone should always match the context of the restaurant and the guest. In fine dining, especially, casual language undermines the atmosphere entirely. Even in casual dining, overfamiliarity can feel presumptuous — particularly with international guests who may find such language unexpected or inappropriate.
Say instead:
✓ "Of course." / "Certainly." / "Absolutely."
✓ "My pleasure." / "Right away." / "I'll take care of that."
✓ "That's a wonderful choice." / "A great selection."
✓ Match the formality level to the restaurant type and the guest's own register.
Category 5: Complaint And Conflict Phrases
Language That Escalates Problems Instead of Resolving Them
When something goes wrong, the words a server uses in the first ten seconds determine whether a complaint becomes a recovery opportunity or a reputation risk.
5.1 Defensive Responses to Complaints
Never say:
✗ "That's not usually a problem."
✗ "No one else has complained about that."
✗ "That's how it's supposed to be."
✗ "The chef made it correctly."
✗ "That's just how we do it here."
✗ "I don't think that's right — let me check with the kitchen." (said in a disbelieving tone)
✗ "Are you sure it wasn't to your taste before you tried it?"
✗ "We've been doing it this way for years."
✗ "Other guests enjoy it like that."
✗ "It should be fine."
Why it fails: Defending the restaurant before acknowledging the guest's experience makes the guest feel unheard and adversarial. Even if the complaint is unfounded, leading with defence escalates the situation. The guest is not interested in being proven wrong — they are interested in having their experience improved.
Say instead:
✓ "I'm so sorry to hear that — let me sort that out for you right away."
✓ "Thank you for telling me. I'll bring that straight to the kitchen."
✓ "That's not the experience we want you to have — let me make it right."
✓ "I completely understand — I'll take care of this immediately."
5.2 Passing the Blame
Never say:
✗ "That's a kitchen issue — I just serve the food."
✗ "You'd have to speak to the manager about that."
✗ "That's not my section."
✗ "I only just started my shift."
✗ "The person before me must have taken that order."
✗ "The kitchen made it that way."
✗ "It's not really up to me."
✗ "That's a management decision."
Why it fails: The guest is not interested in the restaurant's internal structure. To them, every member of staff represents the restaurant as a whole. Deflecting responsibility makes the guest feel like a problem to be passed on rather than a person to be helped.
Say instead:
✓ "I'll personally make sure this is sorted for you."
✓ "Let me get the right person to help you immediately — I won't leave you waiting."
✓ "I'll take ownership of this right now."
5.3 Minimising the Complaint
Never say:
✗ "It's really not that bad."
✗ "I think it might just be the way the dish is."
✗ "Are you sure? It looked fine to me."
✗ "It's probably just the seasoning."
✗ "I wouldn't worry too much about it."
✗ "Some people find it quite nice, actually."
✗ "I didn't notice anything when I brought it over."
Why it fails: Minimising a complaint tells the guest their experience doesn't matter. Even if the issue is small, the guest's feelings about it are not. Dismissing the complaint doesn't make it go away — it makes the guest feel worse and far less likely to return.
Say instead:
✓ "I completely understand — thank you for letting me know."
✓ "Your experience matters to us — let me make this right."
✓ "I appreciate you telling me rather than just leaving me unhappy."
Category 6: End-Of-Meal Phrases To Avoid
Language That Leaves a Poor Final Impression
The final moments of a meal have a disproportionate effect on how the guest remembers the experience. These phrases undermine an otherwise excellent visit.
6.1 Bill and Payment Phrases
Never say:
✗ "Are you paying together or separately?" (said abruptly, without reading the table)
✗ "How are you paying?"
✗ "Cash or card?" (as the very first thing said)
✗ "The machine doesn't always work."
✗ "We have a minimum card spend."
✗ "We don't do split bills." (said with no alternative offered)
✗ "I'll just leave this here." (Bill dropped without a word)
Why it fails: The payment moment is one of the most transactionally obvious points of a meal — the restaurant's job is to make it feel as smooth and gracious as possible. Abrupt or clumsy payment handling leaves a sour final impression regardless of how good the food was.
Say instead:
✓ "Whenever you're ready, I'm happy to take care of the bill."
✓ "Shall I bring the bill, or would you like a few more minutes?"
✓ "We accept cards and cash — just let me know how you'd like to pay."
✓ "I can split that however you'd like — just let me know."
6.2 Closing Phrases That Feel Transactional
Never say:
✗ "Have a good one."
✗ "Cheers, bye."
✗ "See ya."
✗ "Thanks for coming." (said flatly, while already moving away)
✗ "Bye then."
✗ Nothing at all.
Why it fails: The farewell is the last impression a guest takes with them. A rushed or casual goodbye signals that now that they have paid, they are no longer important. In a competitive restaurant market, that feeling is what determines whether they return.
Say instead:
✓ "It was a real pleasure having you with us tonight."
✓ "I hope we see you again soon."
✓ "Thank you so much — enjoy the rest of your evening."
✓ "Please do come back — it was wonderful to have you."
✓ "Safe travels if you're heading out — it was great to meet you."
6.3 Pushing for Return Visits in a Clumsy Way
Never say:
✗ "Make sure you leave us a review."
✗ "We'd really appreciate it if you could review us online."
✗ "If you could give us five stars, that would be great."
✗ "Don't forget to follow us on Instagram."
✗ "We have a loyalty card if you want to sign up." (said at an inappropriate moment)
Why it fails: Asking for reviews at the table — especially with stars mentioned — feels transactional and can make guests uncomfortable. Social media solicitation at the end of a meal breaks the mood. These things can be offered gracefully, but only in the right way and at the right moment.
Say instead:
✓ Let the experience speak for itself — guests who have a great time leave reviews without being asked.
✓ If a card or flyer is appropriate: leave it quietly with the bill folder without comment.
✓ If a guest is visibly very happy: "We're so glad you enjoyed it — we'd love to see you again."
Category 7: Culturally Insensitive Phrases
Language That Alienates International Guests
For restaurants serving an international clientele, cultural awareness in language is essential. These are common blind spots.
7.1 Assumptions About Familiarity
Never say:
✗ "You've had this before, right?" (assuming knowledge of local cuisine)
✗ "Do you know how to use chopsticks?" (asking without being invited to)
✗ "It's quite spicy — can you handle spice?" (assuming based on appearance)
✗ "This might be a bit unusual for you."
✗ "It's quite exotic." (when speaking to guests from the cuisine's country of origin)
✗ "Do you eat [ingredient]?" (based on assumed ethnicity or religion)
✗ "Where are you from originally?" (asked out of personal curiosity during service)
✗ "Your English is very good." (as a compliment — it is often perceived as condescending)
Why it fails: These phrases make assumptions based on appearance, ethnicity, or perceived background. They reduce guests to stereotypes and can cause significant offence, particularly from guests who are well-travelled, multilingual, or from the very culture being referenced.
Say instead:
✓ "Have you dined with us before, or is this your first visit?"
✓ "Would you like me to explain any of the dishes or the way they're traditionally served?"
✓ "Some of our dishes are quite spicy — I'm happy to note the heat levels if that's helpful."
✓ "Do you have any dietary requirements I should be aware of?"
✓ Let guests lead — if they ask a cultural question, answer it warmly and without assumptions.
7.2 Exclusionary Language
Never say:
✗ "That's our most expensive wine." (volunteering price judgement)
✗ "That's quite a lot of food for one person."
✗ "The full tasting menu is very long — are you sure?"
✗ "That's a very adventurous order."
✗ "You don't look like you eat much." (said as a joke — never appropriate)
✗ "Is this a special occasion?" (asked presumptuously to guests who appear to be on a date)
Why it fails: These phrases make assumptions about the guest's capacity — financial, physical, or social. They create a sense of being evaluated rather than welcomed.
Say instead:
✓ "An excellent choice — can I tell you a little more about what to expect?"
✓ Say nothing beyond a warm acknowledgement of the order.
Universal Phrases To Retire Entirely
Regardless of restaurant type, price point, or cuisine, the following phrases should be removed from every team's vocabulary permanently.
✗ "Do you want to spend more?"
✗ "You should upgrade."
✗ "Are you sure that's enough food?"
✗ "Everyone buys this."
✗ "It's only a few dollars more."
✗ "You need to order..."
✗ "You won't be full with just that."
✗ "That's a small portion — most people add something."
✗ "Are you sure you don't want anything else?"
✗ "I really think you should try the..."
✗ "That doesn't come with a lot."
✗ "Most people don't just get the one course."
✗ "You'll regret it if you don't try the..."
✗ "It's just how the chef makes it."
✗ "I don't know — I'll have to ask someone."
✗ "That's not my table."
✗ "We're really busy tonight."
✗ "No worries." (in formal dining contexts)
✗ "Are you still working on that?" (food is not work)
✗ "Are you done with that?" (use "Shall I clear this for you?")
Manager Coaching Notes
Poor language habits rarely come from bad intentions. They come from:
Phrases learned from other servers and never questioned
Pressure to upsell without training in how to do it well
Nervousness that produces filler phrases and overfamiliarity
A lack of awareness about how words land from the guest's perspective
How to address this in your team:
Role-play is the single most effective tool. Pair staff and have one play an international guest with a specific scenario — a complaint, a dietary need, a hesitant order. Have the other respond, then debrief together. Hearing words out loud in context changes behaviour faster than any written guide.
Run a pre-shift phrase of the day — one phrase to avoid and its replacement. Keep it brief and practical.
Create a no-blame culture around language correction. If a manager hears a problematic phrase during service, address it privately and constructively afterwards — never in front of a guest or other staff.
Reward the right language. When a server handles a difficult moment with grace, name it in the team debrief. Language that is praised gets repeated.
Remember:
The most important thing a server can do is make the guest feel welcome, heard, and cared for. Every phrase in this guide that should be avoided fails that test. Every alternative offered passes it.