Most sales teams don't have a written texting policy. They have a Slack message from two years ago and one rep who "knows the rules." That works until a rep texts someone who said stop, or a new hire imports a list nobody checked.
This is an outline you can copy into a doc, edit and hand to your team. It's a starting point, not legal advice. Have a lawyer who knows your state and industry read the final version before you rely on it.
Why a written policy is worth an hour
A policy does three jobs. It tells new reps what they can't do. It gives a manager something to point to when a rep drifts. And if a complaint ever arrives, it shows you had a process. It doesn't make you immune to anything, and compliance stays the sender's responsibility. But "we have rules and a way to check them" is a far better place to stand than "everyone just knew."
Keep it to one or two pages. A policy nobody reads protects nobody. For the legal background, our TCPA SMS compliance guide covers what the law regulates.
The outline at a glance
| Section | The question it answers | Owner |
|---|---|---|
| 1. Scope | Who and what does this cover? | Sales manager |
| 2. Consent | Who may we text? | Sales ops |
| 3. Opt-outs | What happens when someone says stop? | Sales ops |
| 4. Timing | When may we text? | Everyone |
| 5. Content | What may a message say? | Sales manager |
| 6. Records | What do we keep, and where? | Sales ops |
| 7. Escalation | What do we do when something goes wrong? | Manager |
Each section below has sample language. Swap in your own names, tools and numbers.
1. Scope
State who it covers and what counts as a text. For example: "This policy applies to every employee and contractor who sends text messages to leads or customers on behalf of [Company], from any tool. Personal phones are not used for work texting."
That last sentence matters. A rep texting from a personal number sits outside every control you have, including opt-out tracking. Say it plainly.
2. Consent
This is the section that does the most work. Sample rules:
- We text only people who agreed to receive texts from us, in writing, through a form, a checkbox or a reply to our message.
- The consent request names our company, says what kinds of messages to expect and says that message and data rates may apply.
- We never text a purchased or scraped list.
- A person's consent covers the topic they agreed to. A lead who asked for a quote hasn't agreed to promotional offers.
- Reps don't add numbers to the CRM with a "texts OK" flag unless the source is recorded.
Write down where consent is kept. Ready records who sent a bulk campaign, to how many people and when, but it doesn't store a per-contact opt-in record. Your form or CRM has to. If you use a Ready-hosted opt-in page, a sign-up on that page is stored with its time, IP address and wording, and support@tryready.com can send a copy. Our post on documenting SMS consent shows what a useful record holds.
3. Opt-outs
Sample rules:
- Any reasonable request to stop ends texting. STOP, UNSUBSCRIBE, "please stop texting me" and "take me off" all count.
- A rep never argues with an opt-out, never asks why and never sends a "sorry to see you go" that sells.
- Opt-outs are honored on every channel and every campaign, not just the one the person replied to.
- If a rep sees an opt-out in odd wording, they flag it to the manager the same day.
Most of this should be automatic. Ready honors inbound STOP and clear stop phrases and blocks later messages to that number. Odd wording no list catches still needs a person to read replies, which is why the last bullet exists. The opt-out handling guide goes deeper.
4. Timing
Sample rules:
- We text only between 8 AM and 9 PM in the recipient's local time, and later or earlier is never acceptable for a sales message.
- Some states are stricter. When a lead is in a state with its own rules, we follow the stricter window.
- Campaigns are scheduled, not sent by hand late at night.
Ready enforces quiet hours by the recipient's area. Campaigns wait up to 24 hours for the window to open, and a text a rep types to one person is scheduled for the next allowed time. A person who texted you in the last 24 hours can get a reply at any hour. Put the rule in the policy anyway, because tools change and reps switch tools.
5. Content
Sample rules:
- Every first message names our company and who is texting.
- No false urgency, no invented scarcity, no claims we can't prove.
- No sensitive personal data in a text: no health details, account numbers or full card numbers.
- No links that hide where they go.
- Messages are written to be read once, in a few lines.
Ready adds "Reply STOP to opt out" and the business name to the first text to a contact unless the account turns that off. Say in the policy whether you keep it on. We'd keep it on.
If you're in healthcare, remember Ready isn't HIPAA compliant and doesn't sign BAAs, so keep diagnoses, medications and results out of texts.
6. Records
Sample rules:
- Consent source, date and wording are stored with each contact.
- Campaign sends are logged with who sent them and to how many people.
- Opt-outs are kept forever, even if the contact is deleted from the CRM.
- Records are reviewed every quarter by sales ops.
If you also call, add a line about recorded calls and your state's consent rules. For calling lists, a scrub against litigator and DNC lists before the first dial is worth writing in.
7. Escalation
Sample rules:
- A rep who sends a text by mistake tells the manager the same day.
- A complaint, a legal letter or a carrier notice goes to the manager and legal contact within one business day.
- Nobody deletes messages or records after a complaint.
- The manager reviews what happened and updates this policy if it exposed a gap.
Name the legal contact. "Ask legal" isn't a process if nobody knows who that is.
Frequently asked questions
Does a policy make us compliant? No. It makes your process visible and repeatable. Compliance depends on what your team does.
How often should we update it? Review it twice a year and whenever you change tools, add a state or hear of a new rule.
Should reps sign it? Yes. A signed acknowledgment at onboarding turns a document into a habit.
What about 10DLC registration? It's a carrier requirement for US business texting over local numbers, separate from your policy. See our 10DLC explainer.
The takeaway
Copy the seven sections, fill in the blanks, have a lawyer read it and put it in your onboarding. An hour now beats an argument later.
When you want the quiet hours, opt-out handling and send records done by the tool itself, start texting today and look at how Ready handles each one before your first campaign.