Why SMS consent answers need source control
Small businesses often collect phone numbers in many places: contact forms, booking pages, estimate requests, call logs, CRM imports, ads, job notes, and handwritten forms. AI can accidentally merge those records and assume the business has permission to text. That creates trust risk even before formal compliance review.
STOP AUTOMATION: do not let AI send, schedule, or recommend SMS/text outreach until a human verifies the current consent source, message purpose, opt-out status, customer identity, and approved wording. This page is a workflow checklist, not legal advice.
Copy/paste SMS consent source card
Lead/customer name: [name]
Phone number source: [web form / inbound text / call log / marketplace / referral / CRM import / other]
Consent source link or record: [URL, form ID, call note, signed form, inbound text, CRM field]
Consent date/time: [date/time/timezone]
Consent scope: [appointment updates / estimate follow-up / service updates / marketing / unknown]
Message type requested now: [transactional update / sales follow-up / review request / reactivation / promotion]
Opt-out status checked: [yes/no; source]
Last SMS sent: [date/time/message type]
Phone-owner confidence: [verified customer / shared phone / unknown]
Sensitive-topic check: [billing, legal, health/safety, tenant issue, warranty, refund, private account]
Approved reply wording: [short text]
Do-not-text triggers: [no consent source, opt-out, wrong number, disputed identity, sensitive issue, legal/privacy concern, stale imported list]
Human reviewer: [owner/manager/compliance lead]
CRM label: [sms-consent-review / text-ok-transactional / do-not-text / owner-review]Customer-safe text snippets
Thanks for reaching out. Before we continue by text, I am confirming this number and the type of updates you want to receive. If you prefer a call or email instead, tell us here and we will switch channels.Internal note: SMS consent review needed. Verify consent source, message type, opt-out status, phone ownership, and approved wording before any AI-assisted text is sent or scheduled.STOP AUTOMATION: Do not send marketing, review-request, reactivation, billing, refund, legal, warranty, tenant, or sensitive-topic texts until a human owner approves the consent/source card.AI audit prompt
You are reviewing a small-business SMS/text follow-up workflow before it is used. Use only the verified SMS consent source card below. Do not invent opt-in status, legal compliance, customer identity, phone ownership, opt-out status, message frequency, lead source, or permission to send marketing texts. Return: (1) safe message type, (2) consent/source gaps, (3) risky draft wording to remove, (4) human-review triggers, and (5) STOP AUTOMATION decision.
Verified SMS consent source card:
[paste source card]Review before texting
- Does the message purpose match the consent source and the customer's latest channel preference?
- Was opt-out status checked in the SMS platform, CRM, inbox, and recent notes?
- Could the phone number belong to a spouse, property tenant, employee, prior owner, shared office, or wrong-number contact?
- Does the reply avoid invented appointment windows, pricing, refund, warranty, legal, tenant, health/safety, or emergency promises?
Local Lead Rescue tie-in: missed-call and lead-response systems work best when every automated draft has a verified consent/source card and a STOP AUTOMATION path for sensitive or uncertain messages.
Start with the free missed-lead checklist View Local Lead Rescue
AI-SEARCH-SMS-CONSENT-OPT-IN-READY