30916: Campaign rejected: campaign registered as lead generation but describes lead nurture activities, or the reverse

Your A2P 10DLC campaign was rejected because there is a mismatch between the selected campaign use case type and the actual messaging activities described. Specifically, the campaign is registered as "lead generation" but the description and sample messages indicate "lead nurture" activities, or the reverse. These are distinct use case categories with different requirements, and the selected type must accurately reflect the messaging content.

• Lead generation selected but describes nurturing: The campaign was registered under a "lead generation" use case, but the sample messages and description show ongoing engagement with existing leads (for example, follow-ups, drip campaigns, re-engagement) rather than initial outreach to acquire new leads.
• Lead nurture selected but describes generation: The campaign was registered under a "lead nurture" use case, but the sample messages indicate cold outreach or initial contact with prospects who haven't yet engaged with your business.
• Unclear use case distinction: The campaign description blurs the line between lead generation (acquiring new leads) and lead nurture (engaging existing leads), making it difficult for reviewers to classify.

• Select the correct use case type: Determine whether your messaging is primarily lead generation (initial outreach to new prospects) or lead nurture (ongoing engagement with existing leads) and select the matching use case.
• Align description with use case: Resubmit the campaign ensuring the description, message flow, and sample messages all match the selected use case type.
• Split into separate campaigns: If your messaging includes both lead generation and lead nurture activities, consider registering separate campaigns for each use case.
• Review use case definitions: Visit the Campaign Registration Best Practices for definitions and examples of each use case type.
• Contact support: If you believe this rejection is incorrect, contact support.