Worked example: choosing the right disclaimer for a call
A national service company records customer calls for quality and training. Because some customers are in all-party consent states such as California, it uses one script for every call rather than tracking where each caller is: "This call may be recorded for quality and training purposes. If you do not wish to be recorded, please let me know."
When the same calls are used to capture verbal SMS consent, the agent reads a separate SMS consent script with the full disclosure set, and the recording plus a CRM consent flag together serve as the evidence of consent.
Who This Is For / Who It Is Not For
Who this is for: Operators, compliance, and vendors implementing the workflows described in this article. Who this is not for: Readers seeking guarantees, invented fine amounts, or universal fee/MPS figures.
Definitions
| Term | Meaning |
|---|---|
| A2P / Non-Consumer messaging | Business-originated application traffic |
| Consent evidence | Stored proof of opt-in disclosures and assent |
| STOP/HELP | Standard consumer care and opt-out keywords |
| CSP | Communications service provider submitting registrations |
| Primary source | Carrier PDF, IRS page, or CFR text cited in sources |
Short answer: Play or speak a clear recording notice and obtain any consent your jurisdiction requires before substantive conversation. U.S. federal law is generally understood as a one-party consent baseline for recordings under the Wiretap Act framework (18 U.S.C. § 2511), but many states require all-party consent—and interstate calls should follow the stricter applicable rule. Scripts below are illustrative only, not legal advice.
This topic often appears alongside SMS compliance programs because the same contact centers record calls and text follow-ups—but recording law is distinct from TCPA text consent (§ 64.1200).
Why Businesses Disclose Recording
- State all-party consent statutes
- Customer trust and complaint reduction
- Vendor/contact-center contractual requirements
- Quality assurance / training programs
The FCC’s consumer page on recording telephone conversations focuses heavily on broadcast notice rules; it is not a complete 50-state business-recording manual. For state-by-state orientation, see secondary surveys such as Justia’s recording survey—then verify with counsel.
Script Patterns (Illustrative)
Inbound IVR (common contact-center pattern)
“Thank you for calling [Company]. This call may be recorded for quality and training. If you do not wish to be recorded, please hang up and email us at [address], or press [key] to speak about alternatives.”
Stronger all-party style:
“This call is being recorded. Your continued participation constitutes consent to recording. If you do not consent, please disconnect now.”
Live agent opener
“Hi, this is [Name] at [Company]. I’m letting you know I’m recording this call for quality assurance—do you consent to continue?”
Wait for an audible yes before sensitive topics. Configure systems so recording starts only after consent when your counsel requires it.
Outbound sales / collections style
“Hello, this is [Name] from [Company]. This call is recorded. Do I have your permission to continue?”
Collections and financial calls may have additional disclosure regimes—escalate to specialized counsel.
Spanish / bilingual note
If you serve bilingual populations, provide an equivalent notice in the language of the call. Do not rely on English-only notices for Spanish-language conversations without legal review.
Operational Checklist
- Map states where you call and where customers reside
- Default to all-party notice if you cannot reliably geofence
- Keep IVR prompt version history
- Store consent affirmative responses with call IDs when required
- Train agents not to disable recording ad hoc
- Align CRM “recording enabled” flags with actual PBX behavior
Relationship to SMS Programs
Recording disclaimers do not create SMS consent. If agents obtain verbal permission to send informational texts, document that path carefully and still meet CSP Campaign message_flow standards—and marketing texts may still need written electronic consent. See MyTCRPlus consent evidence trail.
Example Full IVR Tree Snippet
- Language select
- Recording notice (script above)
- Department menu
- Optional: “Press 9 if you heard the recording notice and consent to continue” (use only if counsel wants affirmative keypress evidence)
Log the keypress with the call detail record when you rely on it.
Vendor PBX Settings to Verify
- Notice plays on all inbound trunks, including overflow
- Outbound campaigns use preview dialer notices where required
- Voicemail drops are not silently recorded in illegal ways
- Call coaching/whisper features still respect consent rules
Misconfigured “silent record all” toggles create more risk than no QA program.
How MyTCRPlus Can Help
While you finalize telephony scripts with counsel, keep SMS enrollment language consistent using MyTCRPlus tools for disclosure checks on text CTAs that follow recorded calls.
Risk and Failure Modes
| Risk | Mitigation |
|---|---|
| Ignoring primary sources | Read the PDF/IRS page your CSP enforces |
| Mixing regimes | Keep tax, FEC, TCR, TCPA checklists separate |
| Script drift | Version control and mystery-shop |
| Missing STOP | Configure platform defaults + QA |
Implementation Checklist
| Step | Owner | Artifact |
|---|---|---|
| Read primary source | Compliance | Annotated PDF/URL |
| Update scripts/pages | Marketing/Web | Screenshots |
| Train staff | Ops | Attendance log |
| QA controls | QA | Test results |
| File/register if needed | Ops | IDs/status |
| Quarterly re-read | Compliance | Calendar |
Key Takeaways
- Use authoritative sources cited in the front matter.
- Separate legal, tax, and carrier tracks.
- Version scripts and disclosures.
- Test consumer control keywords.
- Keep an evidence pack ready.
FAQ
Is “this call may be monitored” enough everywhere?
Not necessarily. Some contexts expect explicit recording consent, especially in all-party states. Confirm with counsel.
Does federal law override stricter state law?
Businesses often must comply with applicable state all-party rules even when federal law is one-party. Interstate scenarios are fact-specific.
Are we required to announce recording on every extension?
Depends on system design and law. Many contact centers announce once on IVR; transfers should not silently start new recordings without policy review.
Does the FCC require a disclaimer for all business recordings?
The FCC guide linked above is not a blanket mandate for all private business QA recording. Do not treat it as your only compliance source.
Disclaimer
Call recording laws are jurisdiction-specific and fact-specific. These scripts are educational examples only. Consult qualified counsel before enabling recording or deploying notices.