You're next" only works if it gets read. Here's why sending across SMS, WhatsApp, email, wallet pass and live web — with smart fallback — beats relying on a single channel.
A notification only does its job if the customer reads it in time. That sounds obvious, but it's where a lot of queue and booking tools quietly fail: they send a single SMS and hope. Sometimes it lands. Sometimes the number's wrong, the text is buried, or the customer just doesn't check. And a "you're next" that goes unread is the same as no notification at all — an empty chair, a missed turn, a frustrated customer.
The fix isn't a better single channel. It's not depending on one.
The same message, on the surfaces people actually use
Different customers live on different channels. Some watch their texts. Some only really see WhatsApp. Some want email for the record. The reliable approach sends one message across the surfaces that matter — SMS, WhatsApp and email — plus a wallet pass that updates on the lock screen and live updates on the web page itself.
That's five places the same "your table is ready" can land, instead of one. You're not spamming all five every time; you're making sure the message reaches each customer wherever they actually pay attention.
Smart fallback: pick what works, per customer
Sending everywhere blindly is noisy. The smarter version is fallback: try the channel most likely to reach this customer, and fall back to another if it doesn't. The customer who lives on WhatsApp gets WhatsApp; the one who only checks SMS gets a text. The point is that "you're up next" doesn't go unread because you bet on the wrong channel.
Why the wallet pass changes the math
A plain text is static — one line, frozen. A wallet pass is live: it sits on the lock screen and updates itself as the customer's position changes, with no message to open. Combining the two means a customer can both get the ping and glance at their lock screen any time to see where they stand. The pass carries the live state; the message grabs attention at the key moment.
What this prevents
Get notifications right and a chain of small failures disappears:
- No more "I didn't get a message" at the counter. - No more no-shows caused by a reminder that never landed. - No more customers hovering nearby because they don't trust they'll be told. - No more staff re-calling names because the first alert went unseen.
Each of those is a small leak. Together they're the difference between a queue that runs itself and one you're constantly babysitting.
The short version
One message, multiple surfaces — SMS, WhatsApp, email, wallet pass and live web — with smart fallback so it reaches each customer wherever they are. Relying on a single channel means betting your whole experience on a message you can't be sure anyone read.
Noubty sends across five surfaces with smart fallback, so the right customer gets the right alert in time. See the feature.