Text messaging for project management apps.
Task assignments, deadline nudges, @-mentions — the texts that keep work moving when nobody's watching the app.
Free to author & testNo credit cardUS & Canada
Acme: Acme Project Hub: Task #248: Ship onboarding flow was assigned to you. View: acme.app/t/248
Our free message templates are live.
Sending arrives Summer 2026.
A text can change the outcome.
A task gets assigned at 4pm. The assignee is heads-down in a meeting. The in-app notification sits unread. The deadline slips on a Tuesday afternoon because nobody saw the ping. A text changes that.
Project management SaaS messages. And all of the others.
All nine message categories are included — one registration.
Keeps the workspace owner ahead of billing and access events.
Keeps an owner in the loop when something changes on their work.
Nudges the owner as a task approaches or crosses its due date.
Proves phone ownership at signup and gates sensitive actions.
Common questions
Should I send a text for every task status change, or only for certain events?
Only for events that require a specific person to act right now. A task moving from "In Progress" to "In Review" is useful to see in the app — it doesn't need to interrupt anyone's phone. Save SMS for the moments that matter: someone was just assigned work, their name was mentioned directly, or a deadline is hours away. If you text on every status change, people stop reading them.
Who gets the text when a task is assigned?
The person the task was just given to — no one else by default. When someone gets assigned a task, they're the one who needs to know. Watchers and teammates don't need a text every time something moves — that's what the in-app feed is for. SMS is for the one person who has to act. A project manager might want an overdue escalation after a grace period, but make that something they opt into rather than a default.
What's the difference between a "due soon" text and an "overdue" text?
One is a heads-up with time to act; the other is a direct statement that the deadline passed. For "due soon," keep the tone informational — the owner still has time. For overdue, say it plainly: the deadline passed. Don't soften an overdue notice into "coming up soon" — that's confusing when the work is already late. Two separate messages, two separate triggers in your app.
Can I trigger task texts from a webhook, or does it need more setup than that?
A webhook is fine — it's just an API call. Whenever your app fires an event (task assigned, deadline approaching), you make one API call to RelayKit with the recipient's number and the message. It can come from a webhook, a background job, or anywhere else in your code. Your AI tool can wire this up from a description of what you want to happen.
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.