Business identity
Exact legal name, DBA, EIN or other registration identifier, address, industry, website, authorized representative, company-domain email, and contact number.
Business Texting Readiness Guide
A strong registration tells one consistent story: who is sending, what recipients will receive, how they authorize it, how they stop it, and where the public policies explain the program.
The examples must be adapted to the business’s actual program, industry, privacy practices, audience, authorization method, and applicable law. They do not guarantee 10DLC or carrier approval. Heritage and the customer should recheck current provider requirements before submission; regulated or higher-risk programs should be reviewed by qualified counsel.
Before submission
Do not submit vague placeholders and plan to repair them later. A reviewer needs to verify the business, the Campaign, the authorization flow, and the public-facing evidence.
Exact legal name, DBA, EIN or other registration identifier, address, industry, website, authorized representative, company-domain email, and contact number.
One clear description of who receives messages, what they receive, why the business sends them, and the appropriate registered use case.
The URL, form, verbal script, keyword advertisement, QR code, paper form, or consumer-initiated path used to obtain permission.
A reachable privacy policy and messaging terms on the customer’s domain, aligned with the submitted campaign and opt-in language.
At least two realistic samples that identify the Brand, match the use case, show variables in brackets, and include relevant links, numbers, and opt-out language.
Opt-in confirmation, HELP and STOP responses, supported keywords, contact information, message frequency, and records of authorization and revocation.
After Heritage has a complete packet and submits the Campaign, plan on roughly one to two weeks for review. Corrections, evidence requests, special use cases, carrier review, or number association can extend the schedule. Do not promise a launch date until approval and testing are complete.
Privacy policy
Authorization methods do not need unrelated privacy policies. The public policy should describe the business’s real data practices, while each opt-in path links back to it.
[Business Name] uses mobile telephone numbers, message content, and text-messaging consent records to provide the messaging program described in our Messaging Terms, respond to requests, maintain program records, and protect the service.
We do not sell personal information. Mobile information, including telephone numbers, text-messaging originator opt-in data, and consent, is not shared with third parties or affiliates for their marketing or promotional purposes. Service providers may process information as needed to deliver messages or support the service on our behalf, subject to appropriate restrictions.
We retain messaging information for [accurately state the period or criteria]. To ask about access, correction, deletion, or our privacy practices, contact [monitored privacy contact].
Replace every placeholder and reconcile this block with the complete policy. Do not promise deletion, retention, security, or non-sharing practices the business cannot actually support.Messaging terms
Keep messaging terms publicly accessible without a login. They may be a dedicated page or a clearly labeled section of broader terms, but the registered program must be easy to find.
[Business Name] sends [conversational, informational, and/or marketing] text messages about [specific purpose] to people who authorize the program through [list every method].
Message frequency [varies / is up to X messages per period]. Message and data rates may apply. Carriers are not liable for delayed or undelivered messages.
Reply STOP to opt out. We may send one final message confirming the request. Reply HELP for help, or contact [phone/email/website].
Consent is not a condition of purchase. We handle mobile information according to our Privacy Policy at [public URL].
We may update these terms when the program or applicable requirements change. A materially different program may require updated disclosure and authorization before messages are sent.
Program responses
Use the registered Brand name and monitored contact information. Confirm the actual program and frequency instead of sending a generic acknowledgment.
[Business Name]: You’re subscribed to [program]. Message frequency [varies/up to X]. Message and data rates may apply. Reply HELP for help or STOP to opt out.
[Business Name]: For help with [program], call [number], email [address], or visit [URL]. Reply STOP to opt out.
[Business Name]: You have opted out and will receive no further [program] messages at this number. Reply START to opt in again where supported.
Usable campaign examples
These examples are starting structures. Replace the fictional Brand, choose the correct registered use case, and adapt every message to the business’s real operation.
[Business Name] sends conversational customer-care messages to customers and prospects who initiate a text or provide verbal or written permission about a specific sales, service, support, or account request.
Consumer-initiated inbound text, documented verbal permission, or an optional customer-care checkbox. Keep recurring marketing outside this Campaign.
1. [Business Name]: Thanks for contacting us about [request]. [Employee Name] will follow up by [time]. Reply STOP to opt out.
2. [Business Name]: We updated your [service/account] request: [status]. Questions? Reply here or HELP for assistance. Reply STOP to opt out.
[Business Name] sends appointment confirmations, reminders, and scheduling updates to customers who explicitly authorize appointment-related texts.
Optional web or paper checkbox, documented verbal permission during scheduling, or a keyword invitation with complete disclosure.
1. [Business Name]: Your appointment is scheduled for [date] at [time]. Reply C to confirm or call [number] to reschedule. Reply STOP to opt out.
2. [Business Name]: Reminder—your appointment is tomorrow at [time] at [location]. Reply HELP for help or STOP to opt out.
[Business Name] sends operational updates about scheduled service, technician arrival, order status, delivery, or completion to customers who authorize updates for that transaction or service relationship.
Optional checkout or service-request checkbox, signed form, documented verbal permission, or consumer-initiated request.
1. [Business Name]: Technician [first name] is scheduled to arrive between [window] for service request [reference]. Reply STOP to opt out.
2. [Business Name]: Your [order/service] is complete. Details: [approved URL if used]. Reply HELP for help or STOP to opt out.
[Business Name] sends recurring promotional messages about [specific offers, products, or events] to people who separately and explicitly authorize marketing texts.
Use a dedicated, optional marketing checkbox or a documented keyword/QR flow. Do not combine it with required transaction consent. Obtain qualified legal review for the actual program.
1. [Business Name]: [offer] is available through [date]. Details: [approved URL]. Reply STOP to opt out.
2. [Business Name]: Join us for [event] on [date]. Register at [approved URL]. Message frequency varies. Reply STOP to opt out.
Recheck before submitting
The messaging ecosystem changes. Heritage should compare the customer’s packet with current upstream requirements before registration.
Ready for review?