It's 7:15 on a Saturday and a party of six walks up to your host stand. Your host smiles, grabs menus, and in the next ten seconds learns three things nobody wrote down: one guest can't go near shellfish, grandma would rather skip the stairs, and it's somebody's birthday. Now the host is walking backward toward a table, waving at the kitchen, hunting for a high chair that's wedged behind the bar.
None of that is a disaster on its own. Stacked up on a packed Federal Hill night, though, it's the difference between a smooth turn and a table that waits twenty minutes for a dessert nobody knew to fire.
Here's the thing: you already send these guests a booking confirmation, or you could. That text is the one moment before they arrive when you have their attention and their thumb is on the phone. A few quiet questions there, and the answers land in front of your team before the party ever reaches the door.
What your host scrambles for at the door
Think about the questions your host actually asks, or wishes they'd asked, in that first ten seconds. They're almost always the same handful.
- An allergy or a hard "can't eat that." Shellfish, nuts, gluten. The kitchen wants to know before the ticket prints, not after.
- A birthday or anniversary. A candle and a quick "happy birthday" costs you nothing and makes the whole table yours for the night.
- A high chair or booster. Much better to have it waiting than to send a server digging mid-rush.
- Booth versus table. Some folks care a lot, and you'd rather know while you can still seat them right.
- A wheelchair or someone who needs the ramp. If they're coming in the side entrance, your host should be there to meet them, not caught off guard at the stairs.
Every one of these is a small thing your team already handles well in the moment. The problem was never skill. It's timing. You find out at the worst second, when three other things need doing at once.
How the confirmation text gathers it quietly
The setup is simpler than it sounds. When a reservation lands, whether it comes through your booking system, a phone call your team logs, or the online form, the guest gets a short text a day or two ahead. It confirms the time and party size, then asks one or two easy questions.
Keep it short. Something like: "See you Saturday at 7 for six. Anything we should know? Allergies, a birthday, a high chair, need the ramp? Just reply here." That's the whole thing. Most people answer in a few words.
Those replies don't vanish into some inbox nobody checks. They attach to the reservation, meaning the note rides along to wherever your team already looks: the floor plan, the host tablet, the printed sheet by the stand. When the party checks in, the birthday and the shellfish note are right there next to the name.
Be honest about what it won't do
Not everyone replies. Figure somewhere around seven in ten will, which sounds leaky until you count what it saves you. If a couple of your Saturday parties flag the allergy and the birthday ahead of time, that's a couple fewer scrambles at the door on your busiest night.
The quiet ones still get handled the way you always did. Your host asks at the stand, same as ever. The text doesn't replace that conversation. It just clears most of it off the plate, so the questions that remain are quick.
A few other limits worth saying plainly. A text can't judge tone, so a guest who writes "peanut allergy, very serious" reads the same to the system as "no peanuts, thanks." Your kitchen should treat every allergy note as the serious kind and confirm at the table when it matters. And auto-texts can wear on people if they pile up, so send one, keep it human, and don't chase it with three more.
Wire it so the note actually reaches the kitchen
A gathered answer that dies in a phone is worse than no system, because now you think you're covered and you aren't. The whole value is in the handoff.
- Pick the one place your team already looks. The host stand tablet, the reservation line on the floor plan, the pre-shift sheet. Route every reply to that one spot.
- Flag allergies loud. They should stand out, in bold or a color, so a line cook glancing at the ticket can't miss it.
- Read the day's notes at pre-shift. Thirty seconds before service: "table twelve at 7:30 has a birthday, table four is a shellfish allergy." Now the whole floor knows.
- Close the loop on the ones who didn't reply. Your host asks at the door, jots it on the same sheet, and the kitchen still finds out in time.
Writing the text is the easy part. Making sure the reply lands where your crew looks is where most of these stall, and it's the piece we help Rhode Island spots wire in.
Worth doing this week
You don't need a big system to test whether this earns its keep. Start small and see if the door gets quieter.
- Write your one confirmation text. Time, party size, and the short "anything we should know?" line. Read it out loud so it sounds like your place, not a robot.
- Pick the single spot the answers will land, the one your host and kitchen both check without being told.
- Run it on weekend reservations only for two weeks. That's when the scrambles hurt most, so that's where you'll see the difference.
- At pre-shift, actually read the notes aloud. The tech gathers the info; the habit is what saves the night.
- After two weeks, ask your host one question: did the door feel calmer? Their answer tells you whether to keep going.