Upselling that does not sound like selling

"Can I get you anything else?" is the most common upselling line in hospitality, and one of the least effective. It asks the guest to do all the work: to think of something, decide they want it and say so. Most guests say no, not because they want nothing more, but because nothing specific has been offered.

Good upselling sounds nothing like that. It sounds like a server who knows the menu, has noticed what the table is ordering and suggests one thing that would make the meal better: a wine that suits the fish, a side the steak is better with, a dessert that is still warm. Guests hear it as help, and they often say yes.

This guide covers what upselling really is, why specific suggestions beat general ones, four sentences servers can use and the moment in the meal when each works, and how to train the team, price the extras and measure the results without turning service into a sales pitch. Every figure in it is an example.

Upselling, in a restaurant, means suggesting something that adds to the guest's meal: a better wine, a side, an extra, a dessert, a coffee. Done well, it increases the bill because the guest enjoys the meal more, not because they were pressured into spending.

It is not pushing the most expensive item on everyone, reciting a list of extras, or making guests feel awkward for saying no. Those versions raise spend once and cost the venue a guest's return visit.

The distinction matters because the two look similar on a sales report in the short term. Over months, the first kind builds regulars who trust the team's recommendations; the second builds guests who stop asking what is good. The upselling idea is the same across retail and hospitality, but in a restaurant the relationship is the product.

Most upselling sounds like selling because it is general. "Would you like any sides?" "Any drinks?" "Dessert?" Each is a question that could be asked of any table at any moment, and guests hear it as a routine rather than a suggestion.

General questions also put the guest on the spot. To say yes, they have to scan the menu again, choose and justify it to themselves. It is easier to say no, so they do.

And general questions carry no information. They do not tell the guest anything they did not know. A suggestion that names a specific thing, and says why it suits this table, gives the guest something new: knowledge from someone who knows the food.

A specific suggestion does three things a general question cannot. It names one thing, so the guest has an easy yes or no. It gives a reason, so the suggestion feels like advice. And it shows the server has paid attention to this table, which is what makes guests feel looked after.

Compare two lines. "Would you like a side with that?" invites a no. "The hake comes on its own, so most people add the crushed potatoes or the greens. The potatoes are lovely with the brown butter" invites a choice between two good options, with a reason for each.

The specific line is not pushier. It is more useful. It also works only if the server knows the menu well enough to say it, which is why staff training matters more to upselling than any script.

The first opportunity comes with the first conversation. A guest who has just sat down often has not thought about drinks yet, and a specific suggestion helps.

The sentence names one drink, describes it in a few plain words and connects it to the food. It does not insist, and it leaves room for the guest to ask for something else.

For non-drinkers, the same principle applies. "We make a fresh ginger and lime soda that's lovely and sharp" is a better suggestion than "any soft drinks?". Every guest deserves a specific offer, whatever they drink.

The second opportunity comes when guests are choosing. Many guests welcome a recommendation, especially when they are torn between two dishes or new to the venue.

A recommendation like this is upselling in its gentlest form. It may guide the guest to a dish that earns more, but only if the server genuinely likes it. The words are personal and specific, and they describe the dish rather than its price.

Know which dishes to recommend. A server who suggests the dishes the kitchen is proudest of, and that earn well, helps both the guest and the venue. Our guide to menu engineering, and the four dishes you must act on covers how to identify them.

The third opportunity comes with the order itself. Many dishes are better with something added: a side, a sauce, an extra.

Again, the sentence is specific and gives a reason. It names two options, so the guest is choosing between good things rather than deciding whether to spend more. And it is said at the moment the guest is ordering the dish, when the extra makes most sense.

Extras only work if they are priced fairly. An extra that feels overpriced turns a helpful suggestion into a catch. Our guide to modifiers, and letting guests change a dish safely covers modifier pricing in detail.

The fourth opportunity comes at the end, when plates are cleared. It is often the easiest one to miss, because guests seem finished and the server is busy.

Desserts, coffees and after-dinner drinks are among the most natural suggestions in a meal, because guests are relaxed and in no hurry. Offering a dessert to share removes the guest's worry about being too full. Mentioning that something is fresh or warm gives a reason to say yes now.

Never present a dessert menu without a word. A menu handed over in silence invites a polite "just the bill, thanks". A specific suggestion invites a pause.

Timing matters as much as wording. Each kind of suggestion has its moment, and the same sentence at the wrong moment sounds like selling.

Drinks work at the start, before guests have settled into the menu. Recommendations work while guests are choosing, not after they have decided. Sides and extras work at the moment the main is ordered. Desserts and coffees work when the plates are cleared and before the bill is mentioned.

Outside those moments, suggestions intrude. Offering a side after the mains have arrived is too late; suggesting dessert while guests are still eating is too early. A server who learns the rhythm of a meal can make every suggestion feel like part of the service rather than an interruption.

Good upselling depends on reading the table. A couple celebrating an anniversary may welcome a suggestion of a glass of champagne. A business lunch on a tight schedule wants speed, not a description of the dessert trolley. A family with tired children wants the bill.

Look for the signs. Guests who are lingering, chatting and in no hurry are open to suggestions. Guests checking their watches, asking for the bill early or managing small children are not. Guests who ask questions about the menu are inviting recommendations.

And respect a no. A guest who declines a suggestion should not hear another one for the same thing. One well-timed suggestion, gracefully accepted or declined, is worth more than three that make the guest feel pursued.

Upselling works best when the menu supports it. Dishes designed with natural extras, such as a steak with a choice of sauces or a main with sides that suit it, give servers something to suggest. A dessert menu with one or two dishes the kitchen is proud of gives them a reason to mention it.

Menu engineering helps decide what to suggest. The dishes that are popular and profitable deserve recommendations; the dishes that earn well but sell slowly benefit most from a server's words, because guests often overlook them on the page.

Keep the server's list short. Each server should know three or four things to recommend in each part of the meal, and why. A short, well-understood list is used; a long one is forgotten.

Modifier pricing affects how upselling feels. An extra priced fairly, such as a sauce at a modest price or a side at a price that matches its portion, feels like good value. An extra priced high feels like a catch, and guests who notice it on the bill feel misled, however warmly it was suggested.

Price extras on the same basis as the rest of the menu: the cost of the extra plus a margin similar to other dishes, rounded to a fair figure. Show the price clearly wherever the extra appears, on the printed menu, on the screen the server uses and on any digital menu guests order from.

Mention the price when it matters. A server suggesting a premium wine by the glass or a large sharing dish can say the price without awkwardness: "It's a little more, at 12 a glass, but it's worth it." Guests appreciate honesty more than they mind the number.

Average spend per head is the measure upselling is meant to move: the total spent divided by the number of guests. A good upselling habit adds a drink here, a side there and a shared dessert at the end, and over a month those small additions add up.

Take an example. If a quarter of tables add a side at an example price of 5, a fifth add a shared dessert at 9, and a tenth upgrade to a better wine at an extra 4 a glass, the average spend per head on a busy night rises by a few units of currency. Across thousands of covers a month, that is a meaningful sum, earned without raising a single menu price.

Our guide to average spend per head, split properly covers how to measure it, and our guide to increasing average spend without raising prices covers the other ways to lift it.

Upselling is a skill, and it is learned through staff training, not scripts. The most important part is tasting. A server who has eaten the braised beef can describe it honestly; one who has only read the menu cannot.

Make tasting routine. When a dish is new, the whole floor team tastes it and hears from the chef what makes it good. When a wine is added, the team tries it with the dishes it suits. Short tastings before service, a few minutes each, build the knowledge good suggestions depend on.

Then practise the words. Give servers a few example sentences, but let them make them their own; a sentence that sounds natural from one server sounds forced from another. Role-play the moments in a meal, including how to accept a no gracefully. New servers should shadow experienced ones before they suggest on their own.

The simplest rule for upselling that does not sound like selling is honesty. Servers should recommend what they genuinely like and would order themselves, and say so. "That's my favourite" carries weight only if it is true.

Never ask servers to recommend a dish they think is poor, or to push a dish simply because it needs selling. Guests can tell the difference between enthusiasm and a script, and a recommendation that disappoints costs the server's credibility with that table for the rest of the night.

Honesty also means telling guests when something is not right for them. "The duck is lovely, but it's quite rich. If you'd like something lighter, the sea bass might suit you better" is not lost revenue. It is the kind of advice that brings guests back.

When guests order from their own phones, the server's voice is missing, so the menu has to make the suggestion. The natural moment is when the guest chooses a dish: that is when its options and extras appear, and a well-chosen extra, a sauce or a side, priced clearly, works the way a server's suggestion would.

Keep it gentle. A menu that interrupts every choice with offers feels like a sales funnel. One that shows the relevant extras for each dish, with prices and short descriptions, lets guests add what they want without pressure.

Servers still matter at tables that order by phone. A server who checks in, suggests a drink to go with what has been ordered and mentions dessert at the end adds the personal touch the screen cannot.

Many venues reward servers for upselling, and it can help, but it needs care. Targets on a single item, such as a particular wine, can push servers to recommend it to everyone, whether it suits them or not. Guests notice, and the honesty that makes upselling work disappears.

Better rewards look at the whole picture: average spend per head alongside guest feedback, so servers are rewarded for raising spend while keeping guests happy. Recognition matters as much as money; a word from the manager about a table that loved a server's recommendations goes a long way.

Share what works. When a server finds a sentence that guests respond to, let them share it with the team. The best upselling ideas usually come from the floor, not from the office.

To know whether upselling is working, look at the numbers by server as well as for the venue. Average check by server, the share of tables ordering desserts or sides, and the mix of drinks all show who is suggesting well and who might need help.

Read the numbers fairly. A server who works mostly at quiet lunchtimes will have a lower average check than one on busy Saturday nights, whatever their skill. Compare servers working similar shifts, over enough weeks to smooth out unusual nights.

Use the numbers to coach, not to blame. A server whose dessert orders are low may simply need to taste the desserts, or learn the moment to mention them. Pair them with a colleague who does it well for a few shifts.

An invented brasserie finds that only one table in eight orders dessert, and most tables order no sides with their mains. Servers ask "anything else?" at each stage, and guests usually say no.

The brasserie runs short tastings before service for a fortnight, so every server has tried the sides, the desserts and three wines by the glass. Servers agree four example sentences, one for each moment in the meal, and practise them. The chef explains which dishes are best with which sides.

Within a month, the share of tables ordering a side roughly doubles, dessert orders rise to around one table in four, and average spend per head increases by a few units, with no menu prices changed. Guest feedback mentions how helpful the staff are with recommendations. Nobody describes the service as pushy.

In servearound, the extras a dish offers appear at the moment it is chosen, on the point of sale and on the menu guests open from a table's QR code: add-ons priced on top, required choices such as a sauce, and variants such as a larger size, each with its price shown. The booking page can offer add-ons too, so guests can choose a package or an extra when they reserve.

Order analytics show the average and median check, items and lines per check, and what goes together, the dishes and drinks most often ordered with each other, which is a ready-made list of pairings for the team to suggest. Payment analytics show each server's settled checks, revenue and average check, so the effect of staff training can be followed over time. servearound does not prompt servers with suggestions on the order screen; the words are the team's. See Order Fulfillment and Analytics.

Suggesting something that improves the guest's meal, such as a drink, a side, an extra or a dessert, so the bill rises because the meal is better, not because of pressure.

It is general, asks the guest to do all the work and gives them no information. A specific suggestion with a reason is easier to say yes to.

Drinks at the start, recommendations while guests choose, sides and extras with the order, and desserts and coffee when plates are cleared.

Through tasting, so they can describe dishes honestly, a few example sentences they make their own, role-play and shadowing experienced colleagues.

They should recommend what they genuinely like and what suits the guest. Honest recommendations build trust; pushing price does not.

Fairly priced extras feel like good value. Overpriced ones turn a helpful suggestion into a catch the guest notices on the bill.

Through average spend per head and average check by server, the share of tables ordering sides and desserts, compared across similar shifts.

It can help, if rewards look at average spend alongside guest feedback, rather than targets on single items.

The menu shows each dish's extras, with prices, at the moment it is chosen. Servers can still add a personal suggestion at the table.

Upselling that does not sound like selling is specific, honest and well timed. Replace "anything else?" with one named suggestion and a reason: a drink that suits the food at the start, a recommendation while guests choose, a side or extra with the order, and a dessert to share when plates are cleared. Read the table, respect a no and never push what a server would not order themselves.

Support it with a menu that has natural extras, fair modifier pricing and a short list of dishes worth recommending, chosen through menu engineering. Build it through staff training based on tasting, measure average spend per head and average check by server across similar shifts, and reward the whole picture rather than single items.