What makes suggestive selling different from being pushy?
Suggestive selling feels pushy when it is generic and repeated too often, and it feels like hospitality when it is specific, limited to a few natural moments, and offered by someone who genuinely believes in the item.
The line between the two is not about how many times a server speaks up. It is about what they say. "Would you like anything else?" is a closed question with an easy exit. It gets answered no most of the time because it asks for nothing and offers nothing. A specific recommendation, like naming a drink and explaining why it pairs with what the guest already ordered, gives the guest a reason to say yes instead of a reason to say no.
Restaurants that train this well limit suggestions to three moments per table. Beyond that, even specific suggestions start to feel like pressure. The limit is part of what keeps the approach from tipping into pushy territory.
When during the meal should a server actually suggest something?
There are three natural windows: the greeting, the entree order, and the point after entrees are cleared when dessert or another round can be offered.
The greeting happens within the first moments of a guest sitting down. This is the highest-converting moment because the guest has not committed to anything yet and is genuinely open to a suggestion for a drink or starter.
The order moment happens when the guest states their entree. This is where a specific modifier or upgrade gets offered, something like swapping a side for a higher-margin version at a stated price, tied to what the guest just chose.
The third moment, after entrees are cleared, is the one servers skip most often because they are busy and assume the table will say no. Offering a specific dessert or another round at this point captures revenue that most restaurants leave on the table simply because nobody asked.
- Greeting: a specific high-margin drink or appetizer, offered quickly, before the guest has decided anything
- Order: a specific modifier or upgrade tied directly to what the guest just ordered
- Dessert or second round: a specific item offered right after entrees are cleared, not a vague check-in
What should servers say instead of 'would you like anything else'?
They should name the exact item, describe it in one sentence, and connect it to what the guest has already ordered.
A script gives every server the same structure without forcing them to sound robotic. The wording can flex to match each server's style, but the shape stays the same: name the item, describe it briefly, and tie it to the meal in front of the guest. A greeting script might sound like naming the restaurant's signature drink and giving a one-line description before the guest has even opened the menu. An order script follows the same logic, naming the upgrade and its price and linking it to the entree the guest just chose.
Generic phrasing gets a reflexive no. Specific phrasing invites a conversation, which is usually enough to turn a no into a yes.
Results are not typical and will vary with your business, your market, your team and how much of the work you actually do. Client figures on this site come from recorded interviews and are dated. Nothing here is a guarantee of revenue, profit or growth.
How do restaurants know if the upselling is actually working?
They track add-on attachment rate, the share of transactions that include an add-on, daily, and compare it against a 40%+ target.
Most restaurants that have not trained this systematically run far below that target. The gap between an untrained team and a team following a scripted protocol is large enough that tracking it daily, not monthly, is what makes the difference visible fast enough to act on.
Attachment rate should be reviewed in the same place it gets reinforced: the pre-shift meeting. Reviewing yesterday's number, naming the top performer, and having one server practice a script out loud keeps the behavior fresh instead of letting it fade.
| Moment | What the server offers |
|---|---|
| Greeting | A specific high-margin drink or appetizer |
| Order | A specific modifier or upgrade tied to the entree |
| Dessert / second round | A specific dessert or another round, offered right after clearing |
Why does suggestive selling training stop working after a few weeks?
The skill decays without constant reinforcement, so a single training session is not enough on its own.
The usual pattern is that a manager trains the team once, sees attachment rate rise, moves on to other priorities, and watches the number quietly drift back down within a couple of weeks. The fix is not a better one-time session. It is making the script part of every pre-shift meeting indefinitely, announcing the item of the day for each moment, and keeping attachment rate visible so the team can see whether they are holding the standard.
Incentives help keep the behavior active. A small daily reward for the top upseller, a weekly reward tied to attachment rate, and a monthly bonus tied to add-on revenue all give servers a reason to keep practicing the script instead of drifting back to "anything else?"
How do you turn one server's natural upselling skill into something the whole team does?
By writing down what the top server already does instinctively, turning it into a script, training it in pre-shift, and tracking it daily so it no longer depends on who is working that night.
Almost every restaurant has one server whose average ticket runs noticeably higher than everyone else's on the same menu, in the same room. Asked what they do differently, the answer is almost always the same: they recommend something specific at the right moment. The problem is that this knowledge usually lives only in that one person's head. It is not written down, not trained into new hires, and not tracked, so when that server is off, average ticket drops, and when a new hire starts, they default back to "what can I get you?"
Writing the three scripts, printing them as table cards for pre-shift, and tracking attachment rate daily is what converts a single person's instinct into a system the whole floor can run, regardless of who is scheduled.
What is the fastest way to start this with a current team?
Pick three high-margin items per moment, write one script for each, print them for pre-shift, and run a short contest while tracking attachment rate daily.
The items chosen should carry strong contribution margin, be easy for the kitchen to execute without slowing service, and be something the team genuinely likes, since authenticity is part of what makes the suggestion land. Once the scripts exist, a short contest, built around a week of friendly competition for the highest attachment rate, tends to build the kind of momentum that gets a new habit through its first few shifts.
From there, the daily tracking table and the weekly pre-shift review are what keep the habit alive past the first week, long after the novelty of the contest has worn off.
Owners exploring how coaching structures this kind of operational change across a business can read more on the Founders Board page, or look at related case studies for examples of how other operators have applied similar systems.
