Unwanted messaging
- Purchased, rented, scraped, or shared contact lists
- Cold outreach, unsolicited bulk messages, or spam
- Snowshoeing, filter evasion, misleading sender identity, phishing, or fraud
TextCRM Help Center
Business texting, without the compliance maze.
Practical guidance for service businesses that already know their customers and want a simpler way to organize conversations, jobs, and follow-ups.
Existing customers
Customers never need TextCRM accounts. A business may import every customer for contacts, notes, scheduling, and job history. Texting access is handled separately.
| Permission basis | What it means | TextCRM behavior |
|---|---|---|
| Existing text conversation | The customer has already texted the business about their service or job. | Service-related replies are permitted within that conversation. |
| Documented service permission | The customer agreed through a form, agreement, email, QR page, or similar record. | Text only about the subjects described in that permission. |
| Customer requested a text | The customer specifically asked the business to contact them by text. | Keep evidence of the request and stay within its purpose. |
| Permission is uncertain | The business has a phone number but cannot verify texting permission. | Keep the contact in the CRM, but do not send through TextCRM yet. |
An established business relationship is useful context, not texting permission by itself.
Import the customer for CRM use, but keep TextCRM messaging paused until the business can document the customer’s permission for the expected subject.
The easiest migration for long-time customers
Ask customers through the business’s existing conversation or service channel to text the new TextCRM number, or send them to a short permission form or QR page. Do not use the new TextCRM number to send the permission request—the first outbound message already requires permission.
Suggested first message after permission is recorded
[Business Name]: Thanks for agreeing to receive service texts at this number. We'll use it for schedules, weather delays, and job updates. Message frequency varies. Message and data rates may apply. Reply STOP to unsubscribe or HELP for help.
Easy ways to collect permission
Use the option that fits how the work already happens. TextCRM records the source, date, subject, and disclosure. The original invoice, agreement, or email may stay in the user’s own files unless specific proof is requested after a complaint or audit.
- Customer texts first: preserve the inbound message and respond about that request.
- Hosted TextCRM page: send a link by email, place it on a website, or print its QR code on estimates and invoices.
- Keyword: invite customers to text START, QUOTE, or another published keyword.
- Existing agreement: record the service agreement or form that explains the permitted texts.
Service-text checkbox example
I agree to receive text messages from [Business Name] about my request, estimates, scheduling, appointments, and job updates at the number provided. Message frequency varies. Message and data rates may apply. Reply STOP to unsubscribe or HELP for help. Consent is not a condition of purchase.
Keep marketing separate.
A customer who agrees to estimates and scheduling has not necessarily agreed to coupons, seasonal promotions, or newsletters.
First-message checklist
- Name the customer-facing business.
- Match the message to the saved permission subject.
- Include “Reply STOP to unsubscribe” in the initial outbound message.
- Do not use link shorteners or unrelated links during launch.
- Do not schedule recurring messages from conversational-only permission.
Greenway Lawn Care: Thanks for contacting us about your lawn service. We can come Tuesday between 10 AM–12 PM. Reply STOP to unsubscribe.
STOP and other opt-outs
TextCRM should automatically treat STOP, STOPALL, UNSUBSCRIBE, OPTOUT, CANCEL, END, REVOKE, and QUIT as opt-outs. The contact is blocked from additional messages except the permitted confirmation.
- Office staff cannot override the block.
- Scheduled and automated messages are canceled.
- The suppression record remains even if the CRM contact is deleted.
- A later re-opt-in must be affirmative and documented.
Call forwarding
The TextCRM number can forward incoming calls to the business’s verified phone. Calls should not be recorded by default, and the feature is not intended for emergency use.
A missed call is not automatic permission for recurring texts.
Invite callers to text the same number, use a documented keypad opt-in reviewed by counsel, or collect permission through an existing service channel.
What is not allowed at launch
TextCRM is designed for ordinary service-business communication. These restrictions protect the customer, the business sender, and the TextCRM platform.
Sensitive or regulated information
- Protected health information or any HIPAA-regulated workflow
- Payment-card data, bank credentials, Social Security numbers, or account passwords
- Legal advice or privileged legal matters
- Credit, lending, insurance, investment, or financial-advice services
Excluded launch uses
- Emergency, life-safety, crisis, or time-critical communications
- Child-directed services or intentional collection of children's information
- Adult content, gambling, controlled substances, firearms, tobacco, or alcohol promotions
- Political messaging, third-party debt collection, or other specially regulated campaigns
Expected launch uses
- Replies to customer-initiated questions
- Requested estimates and quote follow-ups
- Scheduling, arrival windows, and weather delays
- Job-status, invoice, and account updates for the customer's own service
Who is responsible for what?
| TextCRM | The customer business |
|---|---|
| Carrier-registration workflow, permission records, STOP blocking, account controls, audit logs, and abuse enforcement. | Accurate registration information, lawful permission, message content, invited staff, and honoring customer requests. |
Important
This Help Center provides operational guidance and product instructions, not legal advice. Requirements can vary by message type, industry, state, and customer relationship.