Waitlist text messaging for your app.
Spot-available alerts, table-ready pings, back-in-stock notices — the messages that expire if they're late.
Free to author & testNo credit cardUS & Canada
Acme: A spot just opened for tonight at 7:30. Reply YES in 10 minutes to claim it.
Our free message templates are live.
Sending arrives Summer 2026.
A text can change the outcome.
A restaurant gets a cancellation for tonight at 7:30. The next person on the list claims the table; before it would have sat empty.
Waitlist messages, included.
All nine message categories are included — one registration.
You're on the Acme waitlist. We'll text you when it's your turn. Reply STOP to opt out.
Acme waitlist update: you're now #4. We'll text you when you're up. Reply STOP to opt out.
Acme waitlist: you're up in about 15 minutes. Keep an eye on your phone. Reply STOP to opt out.
Acme is ready for you. Claim your spot: yourapp.com/claim Reply STOP to opt out.
Acme: your spot is still open for 48 hours. Claim it: yourapp.com/claim Reply STOP to opt out.
Your Acme spot expired. Want back on the list? yourapp.com/waitlist Reply STOP to opt out.
Make the messages yours, without breaking them.
Preview every message, edit the wording, or add your own fields.
The parts that keep you compliant stay locked.
Preview with your data
Enter a value once and it shows in every message.
Customize any message
Open the variable list and drop one in.
Q&A: Waitlist messages
What's the difference between a capacity waitlist and a pre-launch waitlist?
The window. Same six stages, completely different timing. A restaurant waitlist moves in minutes — 'you're up in 15' means now. A beta waitlist moves in weeks. The messages are the same shape, but the wait estimate token is the one doing all the work to set the right expectation.
How long should the grace window be?
Long enough that a busy person can act on it. For a restaurant table, 10 minutes is standard — the next person needs the spot. For a beta invite or a course cohort, 48 hours is more realistic. The window is a business decision: short keeps the queue moving, long captures people who don't check their phone immediately.
Does the join confirmation text matter?
More than any other message in the sequence. It's the only text the user is guaranteed to read. It sets the tone for everything that follows — what they expect, how long they'll wait, and whether they'll act when their turn comes. A generic 'you've been added to the waitlist' wastes it.
Can the missed text include an offer to win them back?
No — but it can invite them to rejoin. A discount or promotional incentive changes the text's classification from transactional to marketing, which requires separate consent. Sticking to a simple rejoin link keeps it transactional and is usually enough to recover the people who just missed the window.
You build the feature. We handle the bureaucracy.
Every text message carries a stack of carrier rules. We've read all of it, so you don't have to.
Registration handled
Getting approved on your own can take weeks.
Most registrations clear in about three days. We handle the filing, so you can keep building your app.
Messages compliant
Send the wrong kind of message and carriers block it — silently.
Every message is checked against carrier rules before it sends, not just passed through.
Opt-ins & opt-outs covered
Miss a single STOP and the fines add up fast.
We stop instantly. Consent is tracked and enforced at delivery, not wired up by you.
Give your AI tool a build spec, not a pile of docs.
RelayKit generates implementation instructions for your AI tool. Messages, variables, event triggers, testing steps, and integration guidance arrive for smooth integration.
Slots into ShipFast, Supastarter, MakerKit, and Vercel + Supabase.
import { RelayKit } from 'relaykit'; const relaykit = new RelayKit(); await relaykit.appointments.sendConfirmation(customer.phone, { date: 'Fri, Jun 6', time: '2:00 PM', });
That's the send.
Preview list
Your safe audience for sending test messages, before and after launch.
- JoelVerified(555) 867-8842
- SarahVerified(555) 412-5519
- MikeInvited(555) 290-3301
Run test messages through real phones.
Add yourself, your team, your beta testers. Each person verifies once. After that, your app's messages work for them exactly the way they'll work for customers.
Trigger your real flows — a booking, a code, a reminder — and see the whole loop land: sent, delivered, your database updated.
What it takes to go live.
No telecom expertise required. We handle the carrier side.
Choose your messages
Pick the messages your app needs from templates that already know the rules.
Browse the messages →Build and test
Hand the spec to your AI tool, then test the full flow on real phones before launch.
Go live
RelayKit handles registration and delivery. A few days to approval.
Simple pricing.
Build for free
Set up your messages. Add the code to your app. Test with real phones. No credit card.
Go live for $49 + $19/mo
We file your registration with carriers. Approval takes a few days. 500 messages included per month, then $8 per additional 500. Full refund if you're not approved.
What $19/mo includes.
Marketing messages add $10/mo. Volume pricing above 5,000 messages. US and Canada at launch. We don't handle HIPAA, healthcare-regulated workflows, or enterprise procurement.
When a message can't wait, send a text.
Messages from an app only work when someone sees them. Here's how text and email compare.
Industry SMS-vs-email benchmarks, 2025–26 — open and response from SMS-marketing aggregates; email inbox placement from Validity's 2025 deliverability report. SMS open is inferred from delivery, not pixel-tracked; reported email open rates are distorted by tracking-pixel prefetch and blocking.
The rules show up after you start building.
US carriers require these from every business that sends texts. Getting approved can take weeks if not done right.
Registration
Before anything sends, your business gets registered in a central registry that every US carrier checks — legal name, tax ID, website, and what you plan to send. Details have to match your IRS records exactly, or the application bounces.
RelayKit collects this during setup and files the registration for you.
Carrier review
Reviewers check your registration and your messages against carrier rules before you're allowed to send. Other providers typically take two to three weeks — and every rejection restarts the clock, with no guarantee the next round clears.
RelayKit submissions are prepared to pass the first time; approval typically takes a few days.
Consent requirements
You have to collect and keep proof that every recipient agreed to get texts from you — how they opted in, when, and which kinds of messages they agreed to. Someone who signed up for appointment reminders hasn't agreed to marketing.
RelayKit provides the opt-in language and keeps the consent records automatically.
Build a compliance website
Reviewers visit your website looking for a privacy policy with specific mobile-data language, posted terms, and a visible description of your texting program. A missing or half-finished site is the single most common reason registrations get rejected.
RelayKit generates and hosts a compliance site for you — privacy policy, terms, and opt-in page included.
STOP and HELP handling
A reply of STOP has to halt messages to that person immediately, and HELP has to get a real answer — automatically, every time. Getting it wrong is a fast way to get a number shut down.
RelayKit handles both at the delivery layer; when someone replies STOP, we stop.
Message restrictions
Carriers limit what businesses can say over text: entire content categories are banned, links get scrutinized, and messages outside your registered use case can get your number flagged. The rules live across multiple carrier policies, and they change.
RelayKit's templates already follow them, and custom messages are checked before they send — not just passed through.
The messages are ready now.
Sending arrives Summer 2026.
You can start with the messages today. When sending launches, your AI tool wires up the integration, you test on real phones, and registration and opt-outs stay handled behind the scenes.