Nobody decides to eat hotpot alone on a Tuesday. Hotpot is a group decision: a birthday, a family dinner, a celebration, a catch-up that needed a table big enough to argue over broth choices. That means the marketing question for a hotpot restaurant is never “what should we serve” — it is “what occasion are we helping happen, and how easy do we make it?”
Most hotpot restaurants still market the dish: the broth, the meat platter, the sauce bar. The guests who are already coming will come. The guests who are deciding between three group-dining options are comparing something else entirely: can we get a table for eight on Saturday, will the kids be welcome, how much will it cost per person, and what happens if someone is late.
The group decision journey
Group decisions have a different shape than individual ones. They start earlier (often days ahead), involve more people (the planner, the budget-keeper, the picky eater), and end in a commitment that is hard to reverse. The restaurant that answers the planner’s questions first wins the booking.
What the group page must answer
- Party sizes. “Tables for 2-12” is not an answer. Say which tables fit 6, 8 or 10 and whether they can be pushed together.
- Timing. What are the table-time windows for groups? Can a party book a 90-minute slot, and what happens at the end of it?
- Per-person clarity. Set-menu pricing per person, or a la carte with an estimated range. Groups fear surprises more than they fear prices.
- Deposits and no-shows. State the policy plainly. A deposit that is explained in advance is accepted; a surprise charge is a one-star review.
- Kids and flexibility. Two sentences about high chairs, kids’ portions and whether the party can split broths.
Where the group demand actually comes from
Search behavior matters here: group inquiries arrive through “hotpot for 8”, “birthday dinner near me”, “private room hotpot” and the restaurant name plus “party”. Each of those searches should land on the group page, not the homepage. That is a small structural change with an outsized effect: the group page becomes the landing page for the highest-value guest you have.
One hotpot client ran this exact change and saw group booking requests triple in a quarter. The food had not changed. The page that explained the table had.
The phone and DM scripts
Group inquiries arrive by phone, Instagram DM and comment. Write one script for each channel that asks four questions: party size, date, time window, and occasion. Every answer goes to the same booking form. When the team stops improvising and starts routing, the no-show rate drops and the average party size rises.
The 30-day test
Publish the group page, route every channel to it, and measure three numbers: group booking requests, average party size and no-show rate. If requests rise but no-shows rise too, tighten the deposit policy. If requests stay flat, the problem is visibility — run a small local campaign to the neighborhoods where group diners actually live, pointed at the group page, and read the numbers at day 30.
