Text messaging for authentication apps.
Verification codes, login codes, recovery codes, step-up confirmation — the texts your SDK sends so users can get in.
Free to author & testNo credit cardUS & Canada
Acme: Acme: Verification code: 847291. Expires in 10 minutes.
Our free message templates are live.
Sending arrives Summer 2026.
A text can change the outcome.
The user submits their phone number and stares at a code field. The code has to land in seconds — not minutes. If it doesn't, they refresh, try again, or give up. SMS is the only channel fast enough to carry a time-boxed code to a phone the user is already holding.
Identity & auth SaaS messages. And all of the others.
All nine message categories are included — one registration.
Proves a new user controls the number they entered.
Delivers the step-up code when a returning user logs in with SMS 2FA enabled.
Re-verifies the user before a high-risk action — password change, MFA device swap, billing update.
Lets a locked-out user back in via SMS.
Flags unrecognized device access with a secure-it path.
Common questions
Which code type should I use for a password reset — recovery code or confirmation code?
Recovery code if the user is locked out; confirmation code if they're already logged in. Recovery code is for getting back into an account — the user can't sign in and needs an SMS code to regain access. Confirmation code is for a sensitive action an already-logged-in user is about to take, like changing their password or swapping an MFA device. The names in the message match what the user is experiencing, so pick the one that fits the moment.
What name appears in the verification text — my product's name or something else?
Your product's name — whatever the recipient signed up for. The person receiving the code doesn't know what auth library you used to build your app. They signed up for your product, and that's what should appear in the text. You pass your app's name in when you send the message. If it says something unfamiliar, people assume it's spam.
Do I need a STOP line in my verification texts?
No — verification codes are a special case that don't need opt-out language. One-time codes for signup, login, recovery, and sensitive-action confirmation are exempt from the "Reply STOP to opt out" requirement. Every other message type needs it — but not these. Don't add it to OTP messages; the absence of opt-out language is part of what tells carriers the message is genuinely a verification code.
Do I need a separate setup for each type of verification code — signup, login, recovery?
No — one registration covers all of them. You register once with RelayKit under the verification use case. From there, you choose which message type fits each moment in your app: verification code for signup, login code for MFA, recovery code for account recovery, confirmation code for sensitive actions. They're all part of the same registration.
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.