Text messaging for HR and workforce apps.
Shift assignments, timesheet reminders, payday confirmations — the texts that reach deskless employees who never see the email.
Free to author & testNo credit cardUS & Canada
Acme: Acme HR: your timesheet is due by Thursday noon. Submit here to be paid on time: acme.app/timesheets
Our free message templates are live.
Sending arrives Summer 2026.
A text can change the outcome.
Payroll runs Friday. The cutoff for timesheets is Thursday noon. An employee on the floor hasn't submitted theirs. The email went unread. A text Wednesday afternoon closes that gap.
HR & HRIS SaaS messages. And all of the others.
All nine message categories are included — one registration.
Assigns, reminds, updates, and starts shifts for an hourly workforce.
Keeps the pay cycle on time by chasing submission and confirming pay events.
Confirms a high-risk account change before it takes effect.
Keeps employees informed on account access and lifecycle events.
Common questions
Do I need to ask employees before texting them?
Yes — being part of your team doesn't automatically mean they agreed to receive texts. The right place to capture it is during onboarding. RelayKit hosts an opt-in page for your app — your AI tool will know how to wire it in once you tell it where new employees set up their profile.
Can I include an employee's pay amount in a payday text?
No — confirm the payment happened and link to the stub, but leave the number out. Pay amounts in a text create privacy exposure if the message is seen by someone other than the recipient. The right pattern is: "Your March 15 pay has been processed — view your stub here." The amount lives behind the authenticated link, not in the message itself.
What HR events should I text about, and which should stay in email?
Time-sensitive logistics belong in SMS; sensitive or formal communications belong in email. Shift assignments, timesheet reminders, payday confirmations, and check-in prompts are good SMS territory — they're time-sensitive, actionable, and low-stakes if seen by the wrong eyes. Terminations, disciplinary notices, and anything requiring a documented paper trail should stay in email or formal written channels.
Should timesheet reminder texts go to all employees or only the ones who haven't submitted yet?
Only the ones who haven't submitted. Texting everyone when half the team already filed is the fastest way to train people to ignore HR texts. Filter on submission status before sending — only people with an open timesheet get the reminder. Your AI tool can add that filter once you tell it which field in your data tracks submission state.
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.