Part of Inbox texting approval. This page is only about your Terms and Conditions (sometimes labeled Terms of Service). For the full checklist (names, Privacy, consent form, samples, submit), see Signing Up for Inbox: Texting Compliance Requirements.
Before CoolFocus can turn on text messaging for your organization, carriers require an approval process called A2P / 10DLC (Application-to-Person messaging on 10-digit long code numbers that businesses use to send text messages in the United States).
U.S. mobile carriers (Verizon, AT&T, T-Mobile, and others) use this process to differentiate legitimate business texts from spam and to filter or throttle unregistered traffic. You provide this as part of the Set up texting wizard, in the guided texting setup, from Settings → Phoneting → setup is up temporarextily paused while we move to a new phone provider — if you cannot find it, nothing i wrong with your account. Your organif you need za tionr in the meantime, and use this page to get your Terms ready now.
Registration requires three documents. This article covers only #2:
1. Privacy Policy Requirements for Texting— mobile/SMS non-sharing language
2. Terms and Conditions (this page)
3. Client Texting Consent Form Requirements — how clients opt in
All message senders must have compliant Terms & Conditions made available to their consumers/recipients. This document must be provided as a part of your registration.
Your Terms page should cover SMS/texting rules for people who opt in to receive text messages from your organization. You can keep your existing Terms structure — just add or tighten the SMS / text messaging section if it is thin.
Organization or brand name - your organization or how you are identified in text messages (so clients can identify the sender)
Short organization description (who you are)
How people opt in (intake form, website checkbox, keyword START, written consent, etc.)
What types of text messages they should expect to receive (appointment reminders, care follow-up, etc. — match your real use case)
Message frequency (for example "message frequency varies" or "up to X messages per week") or a recurring-message disclosure
Message and data rates may apply
Complete opt-out instructions — reply STOP to opt out and HELP for help (display STOP and HELP in bold so they are easy to spot)
Customer support contact (email, phone, or web contact page)
Link or reference to your Privacy Policy
Carrier delivery disclaimer: Delivery is not always guaranteed (delays and failures can happen) • Wireless/mobile carriers are not liable for delayed or undelivered messages
Exact carrier-friendly wording often used: "Carriers are not liable for any delayed or undelivered messages."
An example might look like this:
Messaging Terms & Conditions
You agree to receive informational messages (appointment reminders, account notifications, etc.) from [Organization Name]. Message frequency varies. Message and data rates may apply. For help, reply HELP or call us at [phone number]. You can opt out at any time by replying STOP.
Your Terms page must:
Load without a login
Live on your organization's real website domain - Shared document hosts (Google Doc, Dropbox, Canva) are a common first-pass failure for Privacy and Terms.
Use normal page text (not only a PDF, image, or script-only widget CoolFocus cannot read)
Pro tip: Consider a clear SMS / text messaging section (or a short text-messaging–specific Terms page) so reviewers can find STOP, HELP, rates, and the carrier delivery disclaimer quickly.
• Terms only on a Google Doc, PDF-only file, or login-only page
• Missing brand name, support contact, STOP / HELP, rates, or frequency
• Missing carrier delivery disclaimer (delivery not guaranteed / carriers not liable)
• Terms never reference the Privacy Policy
• SMS rules buried so deep reviewers cannot find them
• Signing Up for Inbox: Texting Compliance Requirements
• Privacy Policy Requirements for Texting
• Client Texting Consent Form Requirements
• Purchasing Your Text Number
• Understanding Text Message Delivery Warnings
