SMS Text Messaging Consent¶
Overview¶
/sms-consent is a standalone, publicly accessible page that documents how Otera Health uses SMS text messaging and how patients give (and withdraw) consent to receive it. It exists to satisfy carrier and A2P 10DLC compliance requirements, which expect a clearly published consent and opt-out policy that anyone can read without logging in.
The route is whitelisted as public in OktaPT-FE/middleware.ts, so it renders without authentication and is safe to link from external sign-up materials, carrier registration, and the marketing site.
The page is currently presentational: the opt-in form captures local state in the browser but does not yet submit to a backend. Actual opt-in is recorded through the normal sign-up/profile flow; wiring this form to a consent endpoint is a future step.
What the Page Covers¶
The page is organized as a series of plain-language sections that mirror the consent language carriers expect:
| Section | Content |
|---|---|
| About our text messages | The kinds of messages a patient may receive — appointment/workout reminders, therapy check-ins, security notifications, and replies from their care team. |
| Your consent | States that consenting to texts is not a condition of purchase or of receiving care, and that messages may be sent using automated technology. |
| Message frequency | Frequency varies based on the patient's care plan and activity. |
| Message and data rates | Standard carrier message/data rates may apply and are the patient's responsibility. |
| How to opt out | Reply STOP to any message to stop all further texts; the patient receives a single confirmation and then messages cease. |
| Getting help | Reply HELP for assistance, or contact support. |
| Your privacy | Phone numbers are not shared with third parties for marketing. Links out to the Privacy Policy and Terms of Service. |
Opt-In Form¶
Below the policy text, the page presents an opt-in form with:
- Full name
- Mobile phone number
- An agreement checkbox ("I agree to receive text messages…") that restates the STOP-to-opt-out reminder
The form holds its values in component state only — submitting it does not POST to the API today. It serves as an on-page record of the consent language and a placeholder for a future consent-capture endpoint.
Key Files¶
| File | Role |
|---|---|
OktaPT-FE/pages/sms-consent.tsx |
The full consent page and presentational opt-in form |
OktaPT-FE/middleware.ts |
Whitelists /sms-consent as a public, unauthenticated route |