Executive Summary
Call centers, clinics, dealerships, and retail teams often collect SMS permission during a live conversation. That practice is common—and frequently misunderstood. Under FCC TCPA rules in 47 CFR § 64.1200, marketing texts to wireless numbers generally require prior express written consent (PEWC). A casual “sure, text me” on the phone is a weak foundation for promotional blasts. Verbal authorization can still appear in informational programs and in hybrid flows that convert a spoken yes into an electronic confirmation. This guide explains what verbal consent is, when it is not enough, what fields to log, sample scripts, confirmation texts, CRM design, risks, and an implementation checklist your operations team can run without inventing legal fine amounts or universal fees.
Short answer: For marketing SMS, design a written or electronic opt-in that meets PEWC standards. Treat verbal consent alone as high risk for marketing. If you use verbal agreement for informational or transactional programs—or as a bridge into a YES-reply confirmation—log who consented, to what program, when (with timezone), which script version was used, the agent, recording reference (where lawful), and send a confirmation text that restates brand, message types, frequency, rates, STOP, and HELP.
Who This Is For / Who It Is Not For
Who this is for
- Contact centers and front-desk teams that ask customers for SMS reminders or updates by phone
- Healthcare, hospitality, auto, legal, and retail ops documenting appointment or service texts
- Compliance and legal-ops teams building an auditable consent evidence trail
- Marketing ops migrating from “we asked them verbally” folklore to durable records
Who this is not for
- Teams seeking a guarantee that verbal consent defeats every TCPA claim (no article can promise that)
- Pure web-form opt-in programs with no phone or in-person touchpoint (use a form-focused guide instead)
- Non-US messaging programs governed by other national rules
- Anyone looking for invented settlement dollars or “safe harbor” percentages
Definitions
| Term | Plain-language meaning |
|---|---|
| Verbal consent | Spoken agreement to receive messages, typically on a call or in person |
| Verbal authorization | Same idea; often used interchangeably in ops docs |
| Prior express consent | Affirmative permission before messaging; may be verbal for some informational contexts (fact-specific) |
| Prior express written consent (PEWC) | Written agreement (including qualifying electronic signatures) authorizing telemarketing/ad texts as defined in § 64.1200 |
| Confirmation / double confirmation | Follow-up SMS asking the consumer to reply YES (or similar) after a verbal discussion |
| Message flow | TCR/CSP description of how end users opt in; must match real practice |
| Consent evidence trail | Stored proof of what was disclosed, agreed, when, and how opt-out was honored |
| Call recording disclaimer | Separate notice that the call itself is being recorded (state/federal recording rules) |
What Is Verbal Consent for SMS?
Verbal consent means a consumer orally agrees to receive texts from your brand. In practice it sounds like: “Can we text you appointment reminders at this number?” followed by a clear “Yes.”
What verbal consent is not:
- Silence, “uh-huh,” or “I guess” treated as a durable yes
- Consent for email automatically reused for SMS
- Consent for one brand reused for affiliates without disclosure
- A substitute for Brand/Campaign registration
- Automatic PEWC for marketing promotions
Industry explainers (for example, ActiveProspect’s TCPA consent overview) commonly distinguish PEWC for telemarketing from lower-friction consent concepts for certain informational messages. Your facts, message content, and dialing technology matter. Train agents that message purpose drives the consent standard.
Lead With the Legal Frame (Without Overclaiming)
Under 47 CFR § 64.1200, the term prior express written consent means an agreement in writing bearing the signature of the person called that clearly authorizes advertisements or telemarketing messages using an autodialer or artificial/prerecorded voice, and includes clear disclosures (including that consent is not a condition of purchase, among other requirements in the rule). Electronic signatures under applicable E-SIGN principles are commonly used in industry practice for web and SMS reply flows.
Verbal alone is risky for marketing. Say that clearly to your team. If your goal is weekly offers, loyalty promos, or win-back campaigns, design a written/electronic opt-in path. Use verbal discussion to educate the customer, then complete consent in a durable, auditable form—such as a web checkbox or a confirmation text that captures an affirmative reply.
Registration with TCR / your CSP (Brand + Campaign) proves who you are and what you told reviewers you send. It does not create consent for any individual recipient. See 10DLC 101 and The consent evidence trail.
When Verbal Touchpoints Still Appear
Teams still hear “just ask them on the phone” in:
- Appointment reminder programs at clinics, salons, and service businesses
- Order/status updates for local retail and hospitality
- Account notifications that consumers expect after opening a relationship
- Front-desk check-in when a customer prefers not to fill a form
These use cases may still involve verbal collection as part of the message flow, especially when your Campaign description tells TCR reviewers that staff ask verbally. CSP help articles (for example, RingCentral’s SMS consent examples) show how verbal scripts are expected to name brand, message types, frequency, rates, STOP/HELP, and policy URLs—and how that script must match what you submit in registration.
Even for informational programs, undocumented verbal consent is operationally dangerous. If you cannot show what was said and agreed, you cannot defend the send—or satisfy a CSP audit.
Verbal Consent Example Scripts (Informational vs Marketing Bridge)
Scripts below are illustrative operational templates, not legal advice. Customize with counsel; keep version control.
Informational / appointment reminder (verbal + log + confirmation text recommended)
“Before we finish, would you like to receive appointment reminders and schedule updates by text from [Brand Name] at [number on file]? Message frequency varies. Message and data rates may apply. Reply STOP to opt out anytime, HELP for help. Our Privacy Policy is at [URL]. Consent is optional and not required to book. Do you agree to receive these texts?”
Require a clear “Yes.” Then send a confirmation SMS restating the same disclosures.
Customer care / account updates
“Do you agree to receive customer care and account update texts from [Brand Name]? Frequency varies. Msg & data rates may apply. Text STOP to unsubscribe, HELP for help. Privacy Policy: [URL]. Terms: [URL].”
Marketing bridge (do not rely on verbal alone)
“If you’d like promotional offers by text from [Brand Name], I can send a confirmation text. You’ll need to reply YES to enroll. Offers are optional and not a condition of purchase. Message frequency varies. Msg & data rates may apply. STOP to opt out, HELP for help. Privacy Policy [URL]. May I send that confirmation text now?”
Only enroll for marketing after the electronic YES (or a completed web/e-sign form)—not after the spoken interest alone.
In-person / front desk variant
Train staff to read the same disclosures from a laminated card or POS prompt, then capture the phone number, staff initials, timestamp, and “yes” in the CRM before the first send.
How to Document Verbal Consent: Required Fields
Build structured CRM fields—not free-text folklore.
| Field | Why it matters |
|---|---|
| Phone number (E.164) | Exact destination consented |
| Consent status | active / pending confirmation / revoked / disputed |
| Consent channel | voice / in-person / web / SMS keyword |
| Program / use case | reminders vs marketing vs mixed |
| Timestamp + timezone | Audit timeline |
| Agent or location ID | Who collected it |
| Script version ID | What disclosures were read |
| Exact disclosure text or template hash | Reconstruct what consumer heard |
| Recording URL / ID (if lawful) | Corroboration |
| Confirmation SMS SID + reply | Electronic completion for PEWC-style flows |
| Opt-out timestamp + method | Revocation proof |
| Brand / Campaign ID | Ties to 10DLC registration |
Store immutable history. Do not overwrite the original consent row when someone opts out—append a revocation event.
Decision Framework: Verbal vs Written vs Hybrid
- Classify the message. Marketing/promo → prioritize PEWC via form or YES-reply. Informational → verbal may appear, but still document.
- Map the channel. Voice consent ≠ SMS consent ≠ email consent. Scope each channel.
- Choose capture method. Pure verbal + recording; verbal + confirmation SMS; paper/e-sign; web checkbox.
- Align TCR message_flow. The story you tell reviewers must match production (Twilio collect business info).
- Train and QA. Mystery-shop agents; sample recordings; reject ambiguous yeses.
- Honor STOP everywhere. Revocation methods in § 64.1200 include STOP-style reply keywords; process promptly.
Confirmation Texts After Verbal Agreement
A confirmation text closes the loop and creates a machine-readable event.
Example confirmation (informational):
“[Brand]: You agreed by phone to receive appointment reminders. Msg frequency varies. Msg & data rates may apply. Reply YES to confirm, STOP to cancel, HELP for help. Privacy: [URL]”
Example confirmation (marketing bridge):
“[Brand]: Reply YES to get offers & updates. Msg frequency varies. Msg & data rates may apply. Consent not required to purchase. STOP to opt out, HELP for help. Privacy: [URL]”
Do not start promotional drip campaigns until YES is recorded. Keep the YES message SID and body.
Related: SMS double opt-in, Message frequency disclosure.
Call Recording vs SMS Consent (Do Not Confuse Them)
Recording a call and obtaining SMS consent are different legal topics.
- Many states require one-party or all-party consent to record the call itself. Use a clear recording disclaimer at the start of the call where required. See Call recording disclaimer scripts.
- SMS consent disclosures cover messaging purpose, frequency, rates, STOP/HELP, and brand identity.
- A recording of “yes, text me” may help prove verbal informational consent; it still may not satisfy PEWC for marketing without a written/electronic agreement.
Never tell agents that “we record everything, so we’re covered for marketing texts.”
TCR and CSP Message Flow Alignment
When you select “we ask them verbally” in a CSP registration UI, you typically must paste the script used. RingCentral’s guidance shows a pattern that includes brand, message types, frequency, rates, HELP/STOP, and Privacy/Terms URLs. If agents improvise shorter language on live calls, you have a registration mismatch risk—a common cause of vetting friction and later filtering disputes.
Action items:
- Version-control the approved script
- Put the same script in the Campaign message_flow
- Audit live calls against that version
- Update TCR/CSP filings when the script changes materially
Risk and Failure Modes
| Risk | Failure mode | Mitigation |
|---|---|---|
| Marketing on verbal-only | PEWC gap | Require YES-reply or web PEWC before promos |
| Ambiguous assent | “Sure whatever” logged as yes | Script requires clear Yes/No; QA rejects weak assent |
| No structured log | Cannot prove consent | Mandatory CRM fields; block send if empty |
| Script drift | Agents shorten disclosures | Softphone prompts; quarterly audits |
| Channel mismatch | Voice yes used for marketing SMS | Separate consent flags per channel/program |
| Recording without notice | State recording-law issues | Proper recording disclaimer; counsel review |
| Ignoring STOP | Continued sends after revoke | Suppression list + dual write to messaging platform |
| Message flow fiction | TCR says verbal; production uses web only (or reverse) | Align docs and ops |
Implementation Checklist
| Step | Owner | Artifact |
|---|---|---|
| Classify programs (marketing vs informational) | Compliance | Program matrix |
| Draft verbal scripts + confirmation texts | Compliance + Legal | Script pack v1 |
| Configure CRM consent objects | RevOps / Engineering | Field schema |
| Enable recording where lawful + disclaimer | Telephony | IVR/agent prompt |
| Train agents; certify completion | Ops Manager | Training log |
| Update TCR message_flow | Messaging Ops | Campaign submission |
| Gate marketing sends on PEWC flag | Engineering | Send-time check |
| QA sample 25 calls/month | QA | Scorecards |
| Retention + legal hold policy | Legal | Policy doc |
| Incident playbook for disputes | Compliance | Runbook |
Soft CTA: If you need help packaging opt-in language and public SMS disclosures for registration, review MyTCRPlus tools and microsite options—useful for consistency checks, not a substitute for counsel or your CSP’s official filing.
Internal Linking Suggestions
- Drafts:
/45-sms-double-opt-in/,/29-message-frequency-disclosure/,/65-call-recording-disclaimer/,/77-tcpa-risk-mitigation/,/08-tcpa-texting-compliance/
FAQ
What is verbal consent for SMS?
It is a spoken agreement to receive texts from a named brand for specified message types. It must be affirmative, documented, and scoped to the channel and program.
Is verbal consent enough for marketing texts?
Generally treat it as not enough for marketing under the PEWC framework in § 64.1200. Use electronic/written consent or a confirmation YES flow designed with counsel.
What is a verbal consent example I can train on?
See the informational and marketing-bridge scripts above. Always include brand, message types, frequency, rates, STOP/HELP, and policy URLs, then require a clear Yes.
What is a “verbal signature”?
Ops slang for capturing spoken assent. It is not automatically the same as an E-SIGN electronic signature for PEWC. Prefer documented electronic assent for marketing.
How long should we keep verbal consent records?
Set a written retention policy with counsel based on litigation risk, carrier audit needs, and state rules. Many teams keep consent and opt-out records for years; do not invent a single mandatory period here.
Do we need to record the call?
Recording can strengthen proof where lawful, but recording laws are separate. If you record, disclose appropriately. Recording is not a magic PEWC substitute.
Can one verbal yes cover affiliates and partners?
Do not assume so. Disclose who will text. Sharing numbers for unrelated marketing is a common compliance failure.
What if the customer later says they never agreed?
Your evidence trail—script version, timestamp, agent, recording, confirmation YES—is the defense. Without it, you are negotiating from weakness. Suppress immediately when disputed while you investigate.
Key Takeaways
- How to document verbal consent starts with classifying marketing vs informational traffic.
- Marketing SMS generally needs prior express written consent—do not lean on verbal alone.
- Log structured fields: who, what program, when (timezone), script version, agent, recording/confirmation IDs.
- Align live scripts with TCR/CSP message_flow language.
- Use confirmation texts to create durable electronic events.
- Separate call-recording consent from SMS consent.
- Honor STOP and maintain revocation history.
- Train, QA, and gate sends in software—not only in slide decks.
Disclaimer
This article is for informational purposes only and is not legal advice. TCPA, FCC rules, state telemarketing and call-recording laws, and carrier policies change and are fact-specific. Consult qualified counsel and your CSP before collecting consent or sending commercial messages.