TCR Error 30913: consent bundling.

What it means

This rejection points to consent copy where promotional messages are not clearly separated from service, appointment, or transactional messages.

• Current A2P Desk status: usually eligible for correction and resubmission.
• A2P Desk provides preflight workflow and evidence support only. This content is not legal advice and does not guarantee carrier, TCR, Twilio, HighLevel, or provider approval.

Common causes

• One checkbox authorizes both appointment or service updates and marketing offers.
• The campaign is labeled transactional, but the consent language mentions promotions, deals, or marketing.
• Promotional consent is mandatory instead of a separate optional choice.

What to fix before resubmitting

• Separate promotional consent from transactional or informational consent.
• Clarify the campaign description if the campaign sends transactional messages only.
• Keep opt-in evidence, message flow, and sample messages aligned with the selected use case.

How A2P Desk helps

• Run preflight to identify bundled marketing consent before resubmission.
• Use the submission pack to rewrite consent copy and message flow as separate HighLevel paste fields.
• Attach updated opt-in evidence before marking the client ready for provider review.

Source-backed references

• highlevel: HighLevel A2P campaign rejection reasons and required fixes (2026-05-27)
• highlevel: HighLevel A2P approval best practices (2026-05-27)