Verbal Privacy Disclosure Missing

Why This Rejection Happens

You indicated that you collect consent verbally (e.g., in a call center or POS). However, the script you uploaded failed to inform the user where they can find your Privacy Policy.

Root Cause Analysis

The Fix

Add a specific line to your script directing users to your website.

✓ Correct Script

"You can view our full Privacy Policy at www.mybrand.com/privacy. Do I have your permission to send these texts?"

✗ Non-Compliant

"We respect your privacy." (Too vague - where is the policy?)

Generate Compliant Scripts

Get a full verbal consent script template instantly.

Comprehensive TCR rejection remediation powered by MyTCRPlus.com

What reviewers check for code 7107

When a campaign declares verbal consent, the reviewer reads the exact script your staff speak on the phone or at the counter. The script is treated as the call to action, so it has to carry every disclosure a written opt-in form would: the brand name, what the subscriber will receive, how often, that message and data rates may apply, how to get help, how to opt out, and where the privacy policy lives. Reviewers also look for evidence that consent is captured, such as a CRM field, call recording or timestamped log, because a script on its own proves nothing about who agreed.

For code 7107 (Verbal Privacy Disclosure Missing), the missing piece is the privacy policy link or instructions. The opt-in point must link to (or, in a verbal script, tell the subscriber where to find) the privacy policy. The policy must state that mobile numbers and SMS consent are not shared with or sold to third parties for marketing.

Where code 7107 comes from

Code 7107 is a campaign review reason code used to report a specific deficiency found during manual campaign vetting. CSPs surface it in the rejection notice alongside any other codes found in the same review, so check for companion codes before resubmitting. It is marked High severity: it blocks approval, but it is fully fixable by correcting the submission and resubmitting.

Example: verbal opt-in script for a auto repair shop

The example below uses a fictional auto repair shop, Ridgeway Auto Care, to show the difference between a submission that triggers code 7107 and one that passes.

Rejected:

Agent: "May Ridgeway Auto Care text you repair status updates and service reminders at this number? Msg frequency varies. Msg & data rates may apply. Reply HELP for help. Reply STOP to opt out. Do you agree?"

Approved:

Agent: "May Ridgeway Auto Care text you repair status updates and service reminders at this number? Msg frequency varies. Msg & data rates may apply. Reply HELP for help. Reply STOP to opt out. Our privacy policy is at ridgewayauto.com/privacy. Do you agree?"

Fix and verify before resubmitting

1. Paste the full script, word for word, into the campaign's opt-in description field; do not summarize it.
2. Add the privacy policy link or instructions where code 7107 flagged it, using the approved wording for Ridgeway Auto Care's program shown above.
3. Read the script aloud and confirm each required disclosure is spoken, not implied.
4. Attach a screenshot or document of the script if your CSP offers an attachment field.
5. Describe how agreement is recorded (agent ticks a consent field, the call is recorded, a confirmation text is sent).
6. Make sure the first text the subscriber receives repeats the disclosures from the script.
7. Resubmit with a note that references code 7107 and quotes the corrected privacy policy link or instructions.

Sample resubmission note

Many CSPs let you add a note for the reviewer when you resubmit. A short, specific note shows what changed and speeds up the second review. Example for Ridgeway Auto Care:

Ridgeway Auto Care corrected the deficiency reported as code 7107 (Verbal Privacy Disclosure Missing). Changes made: paste the full script, word for word, into the campaign's opt-in description field; do not summarize it; add the privacy policy link or instructions where code 7107 flagged it, using the approved wording for Ridgeway Auto Care's program shown above; read the script aloud and confirm each required disclosure is spoken, not implied. All URLs, keywords and auto-replies were re-tested from an external network before this resubmission, and the campaign text now matches the live opt-in exactly.

Common mistakes that keep code 7107 coming back

• Linking to a privacy page that does not mention SMS or mobile data at all.
• Saying "see our website" in a verbal script without naming the page.
• Using a privacy link that redirects to the homepage.
• Updating the script in the campaign but not retraining the staff who read it.

Related rejection codes

• Code 3008A: CTA Missing Privacy Link
• Code 2121: Opt-in Form Missing Privacy Instructions
• Code 2131: Verbal Script Missing STOP Instructions
• Code 2127: Verbal Script Missing STOP Instructions
• Code 2124: Verbal Script Missing Frequency Disclosure
• Code 2123: Verbal Script Missing Message Type

Frequently asked questions about code 7107

Does code 7107 mean the whole campaign is non-compliant?

No. Code 7107 points to one gap: the privacy policy link or instructions in your verbal opt-in script. Fix that gap, check the rest of the submission against the same checklist, and resubmit. Reviewers often list only the first deficiency they find, so a full self-check prevents a second rejection.

Where exactly should the privacy policy link or instructions appear?

Place the disclosure in the script itself, immediately after the agent asks for permission to text and before the customer answers. The opt-in point must link to (or, in a verbal script, tell the subscriber where to find) the privacy policy.

Do I fix my live verbal opt-in script or only the campaign text?

Both. Update the script in the campaign and retrain staff so the spoken script matches it; reviewers compare the two when consent is disputed.