If you build an LMS or a student-engagement product, you've probably heard the same request from schools and training companies for a year: "Can it text them?" Email gets buried, push notifications need an app install, and a text about a deadline gets read in minutes. The feature looks small on a roadmap. It isn't.
This guide is for the product team deciding how to add texting. We'll walk through which events deserve a text, how to handle consent when some of your learners are minors, what to do about STOP, and how to keep each school's sending separate. Every scenario below is an example with stated assumptions, not a customer story.
Which education events deserve a text
Start from events your platform already emits, then be stingy. A text interrupts. Spend that on things with a clock on them.
- Deadline reminders. An assignment due tonight, an exam window that closes Friday.
- Schedule changes. A live session moved, a room changed, a class canceled.
- Enrollment steps. A registration deadline, a missing form, a payment due.
- Re-engagement. A learner who hasn't logged in for two weeks in a self-paced course.
- Verification codes. One-time passcodes are a different traffic type, covered in our post on SMS for OTP and notifications.
Skip grades, discipline notes, special education details and anything about a learner's health. Those belong behind a login. Ready isn't HIPAA compliant and doesn't sign BAAs, so keep health information out of texts entirely. A message like "You have a new message in your portal, please log in" is fine. The content itself shouldn't travel by SMS.
Consent, and the minors question
The consent rule is the same as any other texting: the person has to agree to receive texts, the agreement has to be specific and easy to find, and you need a record of it. In education, two things make it harder.
Who is the recipient? A university student is an adult who can agree for themselves. A K-12 learner often isn't. For younger learners, texts usually go to a parent or guardian, and the parent is the one who agrees. Model that in your data: the phone number belongs to a guardian contact, with its own consent record, not to the student.
What did they agree to? Consent to receive "class updates" isn't consent to receive promotions for an upgrade or a partner's offer. Keep the purposes separate in your schema, and send only under the purpose the person accepted. If you're working out the legal side for a particular school or state, talk to a lawyer; this is the technical outline, not legal advice.
When you send through Ready, set consent_attested to true only when your stored record says the recipient agreed. Ready records that attestation (who sent, to how many, when), but it isn't a per-contact consent record. It doesn't store the recipient's opt-in time, wording or page URL, so your platform keeps that in its own database. (The one exception is a sign-up on a Ready-hosted opt-in page, which is stored per contact.) Our posts on a consent record schema for developers and documenting SMS consent show the columns we'd keep.
From January 20, 2027 (UTC), an API send without consent_attested is refused with a 403. Until then it still goes out with a warning and leaves no attestation. Build the field in now.
Sending a deadline reminder
A send is one request. This is the shape Ready's API uses, with a made-up number:
POST /v1/messages
X-API-Key: <key>
Idempotency-Key: <one UUID per message>
{"to": "+12125550199", "body": "Reminder from Example Academy: your Unit 3 quiz closes tonight at 11:59 PM. Reply STOP to opt out.", "consent_attested": true} A few details that matter for a platform:
- Idempotency. Generate one UUID per reminder and reuse it on every retry, so a timeout never texts a learner twice. We cover the pattern in idempotency for duplicate texts.
- Segments. A plain segment is 160 characters, and 153 for each part of a longer message. One emoji drops it to 70. Unless the account turns it off, Ready also adds "Reply STOP to opt out" and the business name to the first text to each contact. Count those characters. Our segment counter post shows how to check before sending.
- Bulk. For a cohort announcement,
POST /v1/messages/bulktakes a list of numbers, up to 100 per call. Split bigger cohorts into batches.
Docs for the endpoint are at https://docs.tryready.com/api/messages.
STOP, and what your product should do with it
When someone replies STOP, UNSUBSCRIBE or a clear phrase like "please stop texting me", Ready honors it and blocks further texts to that number. Your job is to reflect that in the product so a teacher doesn't think a text is going out when it isn't.
- Read opt-outs back with
GET /v1/opt-outs, and check a single number withGET /v1/opt-outs/:phonebefore a send from another tool. - Show an "opted out of texts" badge on the learner or guardian record.
- Fall back to email or in-app notices for that person automatically.
A STOP always blocks that number in the sub-account that received it. Whether it also blocks the parent and other sub-accounts is decided by Ready, so use the per-number check for the rest. More on this in handling SMS opt-outs.
Quiet hours across time zones
Learners live everywhere, and a deadline reminder at 9 PM Eastern lands at 6 PM Pacific but also at 2 AM in London. Texting rules limit when a business can contact people, and Ready enforces quiet hours based on the recipient's area.
For you, that means two behaviors. A campaign or automation waits up to 24 hours for the window to open. An API text is held only if the window opens within 6 hours; otherwise it isn't sent, and your code sends it again once the window opens. Your scheduler should expect that answer and retry rather than treat it as an error. We walk through the response in handling the quiet hours 409.
Design deadline copy with this in mind. "Due tonight" is fragile across zones; "due Friday at 11:59 PM Eastern" holds up.
One sender per school
If your product serves many schools, districts or training companies, each one should have its own sender. Ready's sub-accounts give each customer its own numbers and its own carrier registration (10DLC), so one school's complaints don't land on another's numbers. Registration is part of onboarding, with most approvals taking 2 to 7 days, and it can be done through the API. Unregistered traffic gets carrier-filtered, so don't skip it. Our multi-tenant SMS architecture post covers the design in more depth, and the 10DLC explainer covers why registration exists.
Ready registers businesses that have an EIN. A school or training company without one can't register, so ask during onboarding rather than at launch.
Example: a self-paced course reminder
Assume an example platform with 20,000 learners across 40 school customers. It texts only learners who opted in at enrollment, and only about deadlines. Each message is one segment, so the cost is one segment per delivered text, at Ready's per-segment rate plus the carrier fee, both on the pricing page. Replies are billed too, at the segment rate plus the lower received carrier fee, so a platform where learners reply "what time?" should budget for inbound as well.
FAQ
Can we text students under 13? That's a legal question for your counsel. Technically, route the text to a guardian contact with its own consent record.
Do we need the learner's reply to start? No. Consent can be captured at enrollment, as long as it's specific and recorded.
Where do we get started? The API quickstart at https://docs.tryready.com/api#quickstart covers a key, a first send and a webhook.
The practical takeaway
Treat texting as a feature with three parts: consent you store, sends you can safely retry, and a sender per school. Start with one event, such as deadline reminders, for one pilot school. If you'd like to see the sends and the STOP handling before you build the full feature, sign up and try a test key.