Text messaging for nutrition and meal planning apps.
Meal-log reminders, streak saves, weekly plan alerts — the texts that keep users logging before the habit breaks.
Free to author & testNo credit cardUS & Canada
Acme: Grove: time to log lunch. Keep your 12-day streak alive: grove.app/log Reply STOP to opt out.
Our free message templates are live.
Sending arrives Summer 2026.
A text can change the outcome.
A user skips logging lunch. Then dinner. By tomorrow the streak is gone. A text at 12:30 catches the skip before it compounds.
Nutrition & meal planning apps messages. And all of the others.
All nine message categories are included — one registration.
Keeps a paid subscriber active through trial, renewal, and payment failure.
Nudges the user to log a meal at their configured time, fires a streak-save if they miss the window, and tells them when their weekly plan is ready.
Runs a coach's periodic accountability touch with the client.
Verifies the phone at signup and protects the account.
Common questions
How many meal-log reminder texts a day is too many?
One per meal at most — and only for meals the user opted into reminders for. If a user set up a lunch reminder at 12:30, that's the one that goes. Don't fire a dinner reminder just because they didn't log lunch — at that point you're piling on a user who's already disengaged, and the most likely outcome is an opt-out. One nudge per configured meal, sent once, at the time they chose.
Should I send the streak-save text for every missed meal or only at end of day?
At the missed meal window — not end of day. A nutrition streak is usually about logging a specific meal. If the lunch window closes at 1pm and the user hasn't logged, that's when the streak-save fires — not 8pm, when there's nothing they can do about it. End-of-day streak saves make sense for activity apps where any action counts. For meal logging, tie the save text to the meal window it belongs to.
Should coach check-in texts come from the app or from the coach's name?
From the coach's name — that's who the client has a relationship with. A text that says "Coach Maya is checking in" lands differently than one that says "Grove is checking in." The coaching relationship is personal; the app is the tool that delivers it. Use the coach's name in the message when your platform supports named coaches. For AI-coached or unassigned flows, the app name is fine — but wherever there's a real human, name them.
When should the weekly plan notification go out?
At a set time — when the user is likely to act on it. A plan that generates at 3am and texts immediately wakes nobody up in a useful way. Most apps send the weekly plan notification Sunday evening or Monday morning — when the user is actually planning their week. Generate whenever your system needs to, but schedule the notification for the moment the user is most likely to open it and start cooking.
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.