For restaurant reservation or waitlist software, text a guest when their table is ready, confirm a booking and ask for a reply to keep or release it. Give each restaurant its own sub-account and number, send with POST /v1/messages, and treat replies as part of the product.

A "your table is ready" text works because it's timely and asked for. A reply-to-confirm text cuts no-shows because it makes keeping the table a small decision. Both are transactional, and both fit one segment. For general design, see SMS API for SaaS platforms, and for the restaurant side, restaurant text messaging templates.

Core messages

MomentTextReply expected
Joined waitlist"You're on the list at Example Bistro, about 25 minutes. Reply C to cancel."Optional
Table ready"Your table is ready. Please check in within 10 minutes."No
Booking confirmedDate, time, party sizeNo
Day-of reminder"Still coming at 7:30? Reply Y to keep it."Yes
After the mealThanks, a review linkNo

Write for one segment: 160 GSM-7 characters, or 70 if you use an emoji. Curly quotes and long dashes are swapped for plain ones before sending on Ready, so they don't change the count.

Handling replies

Receive replies on a webhook and match the number to the active booking. Parse a few clear answers (Y, C), and send anything else to staff. Don't build a rigid keyword tree for free text. Two-way keyword routing covers the safe pattern. A reply to a guest who texted in the last 24 hours can go out at any hour.

Setup per restaurant

  1. Create a sub-account for each restaurant or group with POST /v1/sub-accounts.
  2. Register the business through the registration API. Most approvals take 2 to 7 days.
  3. Buy a number, at $2 a month, and use it for all guest texts.
  4. Send with consent_attested: true only after the guest agreed to texts, for example by entering a phone number with a clear notice on the waitlist screen.

Until registration is approved, an account can send up to 500 texts a calendar month. A busy restaurant can reach that quickly, so push every new customer to register on day one.

Waitlist consent

The waitlist is a place where people hand over a number in a hurry. Add a short line at the entry point: "By joining, you agree to get texts about your table. Reply STOP to opt out." Keep a record of when and how the guest agreed. See SMS opt-in message and form examples.

Cost

A restaurant with 150 waitlist guests a week, each getting three one-segment texts, sends 450 segments a week. That's 450 × ($0.0075 + $0.0045) a week, an assumption you can swap for real volume.

Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.

Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.

Frequently asked questions

Should marketing share the number? Better not. Keep guest service texts on one registered campaign and marketing on another.

What if a guest replies STOP while waiting? The number is blocked and the text can't be sent. Show the host a note so they call or use an in-app alert.

Can guests send photos? Yes, as inbound MMS. Decide whether your product shows them.

Next step

Build the table-ready text first. It's the highest-value message and the simplest to test.