Three ways to text your waitlist — and which one you want

Waitlist App can text your customers in three different ways, and the right one depends on how much setup you want to do:

  • Free (device-native): the app opens your own phone's Messages, WhatsApp, or email with the message pre-filled — you tap Send. Works anywhere, costs nothing, but it's manual and goes out from your personal number.
  • Pro (notification packs): we send real SMS from our own number, automatically, with no Twilio account and no code. You buy a pack of credits and turn on the events you want texted. This is what this guide is about.
  • Enterprise (bring your own Twilio): connect your own Twilio account and texts go out from our servers but bill to your Twilio. Best for international sending, very high volume, or businesses that already run Twilio.

What a notification pack is

A notification pack is a one-time $50 purchase that drops a balance of text credits onto your Pro account. One pack covers roughly 500 customers — we budget about three texts per customer (a welcome when they're added, a "you're up" when it's their turn, and room for one more). Credits never expire: buy a pack today, and whatever you don't use is still there next month or next year. There's no subscription to the packs and no Twilio bill — the per-message cost is already baked in.

Availability: managed SMS is currently US-only. Your account needs a US billing address to buy a pack, and we only send to US phone numbers. If a customer has an international number, that text simply falls back to device-native (you can still text them from your own phone) and no credit is used.

The everyday payoff: customers watch their own place in line

The reason to turn on texting isn't the text itself — it's the tracking link inside it. When a customer is added, they get a message with a link to a clean, branded page showing their live position and estimated wait. Instead of hovering by the host stand or asking "how much longer?" every few minutes, they can step away, grab a coffee, and glance at their phone.

For a busy salon, urgent-care clinic, or weekend brunch spot, that one change tends to do two things: it cuts down the interruptions your front desk fields, and it cuts no-shows, because people who can see "you're 2nd, about 10 minutes" actually come back when it's their turn.

Set it up in three steps

  1. Buy a pack. In your Pro dashboard go to Settings → SMS Alerts. You'll see your current balance and a Buy a pack — $50 / 500 customers button. It runs a normal secure checkout; the credits land on your account as soon as the payment clears.
  2. Choose what gets texted. In the same SMS Alerts section, flip on the events you want to send automatically: Added (the welcome + tracking link), Notified ("you're up now"), and Seated (an optional thank-you). Turn on only the ones you need — each send draws one credit.
  3. Make the messages yours. Edit the templates so they sound like your business. You can drop in {{name}}, {{business_name}}, {{tracking_url}}, {{position}}, and {{party_size}} and the app fills them in per customer. Keep them short — a single SMS is 160 characters before it splits into a second segment.

That's it. From then on, as you add and advance people in your queue, the texts go out on their own and your balance ticks down.

Running multiple stations or locations

A common question is whether several team members can run one shared list together. Today each queue has a single operator account — there isn't multi-user editing of the same queue. But there are two solid ways to handle a multi-chair or multi-station operation:

  • Run separate queues. Pro includes three queues, so each stylist, provider, or location can have its own line — its own tracking links, its own branded page, its own SMS templates. (You can add more beyond three for a small monthly amount.)
  • Put a live board on a shared screen. The public display board (a Pro feature) shows "Now Serving / Up Next" on any TV, tablet, or monitor, and there's a staff display that shows full names and contact info for the back of house. Everyone on the floor — and your customers — can see the same queue at a glance, even though one account is doing the editing.

When to bring your own Twilio instead

Packs are built for the common case: a US business that wants hands-off texting without touching Twilio. Step up to Enterprise and connect your own Twilio account if you need to text international numbers, you're sending at very high volume and want direct per-message billing, or you already operate Twilio and want everything on one bill. Our companion guide on connecting Twilio walks through that setup.

International numbers

Notification packs cover US and Canadian phone numbers. If your business serves guests from outside North America — a hotel near a major airport, a tourist-area restaurant, or a medical practice that sees internationally-based patients — some of those customers will have numbers that packs simply cannot reach. Bringing your own Twilio account gives you access to Twilio's full international carrier network, so a guest checking in with a UK, Australian, or Brazilian mobile number gets the same real-time queue updates as anyone else. Before enabling international delivery, verify that your Twilio account has the geographic permissions enabled for the countries you need — Twilio restricts certain regions by default for fraud prevention, and you'll need to unlock them in your Twilio console.

Very high send volumes

For most service businesses — a barbershop, a boutique clinic, a mid-size restaurant — a notification pack covers daily messaging comfortably. But some operations run a genuinely large message throughput: a DMV service center, a hospital outpatient department, or a multi-site franchise that funnels hundreds of guests per hour across locations. At that scale, per-message billing through your own Twilio account can become more economical than purchasing packs in bulk, and you gain direct visibility into carrier-level delivery reports inside the Twilio dashboard. If you're unsure which model fits your volume, a rough rule of thumb is to count your average daily seated guests, multiply by two or three messages per guest (join confirmation, ready alert, and occasionally a follow-up), and compare that against the pack tiers available on your plan.

Consolidated billing and existing Twilio relationships

Many larger operators — multi-location food groups, healthcare systems, hospitality brands — already have a negotiated Twilio contract in place. Routing waitlist messages through that existing account keeps all SMS spend on a single invoice, simplifies accounting, and may let you take advantage of volume discounts your organization has already secured. If your engineering or IT team actively manages Twilio for other customer-facing communications (appointment reminders, marketing texts, two-factor authentication), adding the waitlist integration to the same account also gives them unified observability over message delivery and spend.

Choosing the right path

To summarize the decision cleanly:

  • Use notification packs if you serve domestic (US/Canada) customers, prefer a flat predictable cost, and don't want to manage a third-party account.
  • Bring your own Twilio if you need international delivery, send at very high daily volume, or already have a Twilio account you'd like to keep consolidated.

There's no wrong answer — both paths produce the same customer-facing experience. The difference is purely operational: who manages the carrier relationship and how the messaging cost is structured. If you outgrow packs, switching to your own Twilio account doesn't require rebuilding your waitlist configuration; the notification templates, timing rules, and station assignments all carry over.

Good to know

  • No surprises if a send fails. If a text can't be delivered, the credit is automatically refunded — you only pay for messages that go out.
  • Credits roll over forever. Seasonal business? Buy a pack in your busy month and coast on the balance through the slow one.
  • You're still in control of when. Auto-send is per event and per queue; turn any of it off any time, and manual notify from the dashboard always works too.

Phone number formatting and validation

The system validates phone numbers at the point of entry, not at the point of send. That means if a guest types a malformed number into your check-in form, they're prompted to correct it on the spot — before they walk away from the counter. This eliminates the frustrating scenario where you think you've sent a notification, the customer is waiting outside, and the message quietly failed because a digit was transposed. Accepted formats include local 10-digit entries and full international E.164 format, and the parser handles common variations like parentheses, dashes, and spaces automatically.

Message content and character limits

Each notification template supports personalization tokens — guest name, estimated wait, queue position, and your business name — so the messages feel tailored rather than robotic. Standard SMS messages cap at 160 characters for a single segment. The dashboard shows a live character count as you draft, and if your template runs long, it flags the overage before you save. Staying within one segment per message keeps your per-credit cost predictable; longer messages that require concatenation consume additional credits, and the editor makes that trade-off visible rather than hiding it in a billing statement.

Opt-out handling is automatic

Any guest who replies STOP is immediately removed from future automated sends for your account, and that suppression is stored permanently — not session by session. You don't have to manage an opt-out list manually or worry about accidentally retexting someone who asked not to be contacted. This behavior follows carrier requirements for application-to-person messaging, so your account stays in good standing without any extra configuration on your end.

Credits are account-wide, not queue-specific

If you run three queues — a main dining room, a bar seating list, and a private event waitlist — they all draw from the same credit balance. There's no need to pre-allocate a budget per queue or worry about one list running dry while another sits idle. This is especially handy for businesses where traffic patterns are hard to predict: a walk-in rush at the bar doesn't starve your dining room list of credits.

Test messages don't cost a credit

Before you go live with a new template, you can send a test message to your own number directly from the editor. Test sends are free and don't touch your credit balance, so there's no penalty for previewing the experience exactly as your guests will see it. It's worth doing every time you edit a template — a small wording change can read very differently as an actual text than it does on screen.

Dashboard visibility into send history

Every outbound message is logged with a timestamp, the triggering event, delivery status, and the remaining balance after the send. If a customer disputes whether they received a notification, you have a clear record to reference. The log is filterable by queue and date range, making it straightforward to review activity after a busy shift or to spot any patterns in delivery failures — for example, if a particular area code consistently shows undelivered status, that's a signal worth investigating before it becomes a customer experience issue.

Related guides

The articles below pick up where this guide leaves off. Whether you want to fine-tune the exact words a customer receives, scale to thousands of sends a month, or connect SMS to the rest of your front-desk workflow, each guide covers one topic in full without assuming you've read the others first.

SMS and notifications

  • SMS alert templates & triggers — the deeper dive on per-event sends and message variables. Learn how to personalise every message with the customer's name, estimated wait time, and queue position, and how to set conditional triggers so a text only goes out when specific rules are met (for example, only when the wait drops below ten minutes, or only during certain hours).
  • Connecting your own Twilio (Enterprise) — for international or high-volume sending. Walks through obtaining a Twilio Account SID and Auth Token, mapping them inside your dashboard settings, and choosing a sender number that meets local carrier registration requirements.

Queue and waitlist management

  • Virtual queue best practices — practical advice on check-in flow, party-size collection, and how to structure your queue so SMS notifications land at exactly the right moment in the customer journey.
  • Managing queues across multiple locations — expands on the multi-station concepts introduced in this article, including how to give location managers independent visibility while keeping reporting centralised for owners.

Customer experience

Billing and account management

  • Pro plan overview — a full breakdown of everything included in the Pro tier, how notification pack credits are tracked on your invoice, and what happens if you reach your monthly cap mid-cycle.
  • Upgrading from Pro to Pro — step-by-step walkthrough of the upgrade path, including how existing queue data and customer records carry over without interruption to your service.
Not finding what you need? The Help Centre has a searchable index of every setup guide, and the in-app chat connects you to a support specialist who can answer configuration questions specific to your business type and volume.