A Complete Guide to A2P 10DLC

Modified on Sun, 17 Mar at 6:15 PM

LimePhone A2P 10DLC Fee Structure: An In-Depth Overview

With the rollout of the new A2P 10DLC system, LimePhone is committed to transparent fee management, passing costs directly to you without any additional markup. Here's a detailed breakdown of the industry-standard fee structure:

Understanding A2P 10DLC Fees

  • One-time Brand Registration Fee: $4 (mandatory)

    Note: Providing inaccurate business information may lead carriers to reject the application, resulting in additional $4 fees for subsequent submissions. Ensure accuracy in your EIN, business address, and other details to avoid duplicate charges.

  • One-time Manual Vetting Process Fee: $15 (mandatory)

  • Use-Case Registration Fees: Ranging from $1.50/month to $30/month (mandatory)

  • Carrier Fees: (mandatory)

  • One-time Vetting Fee: $40 (mandatory for High-Volume)

Choosing the Right Use Case

Select the appropriate Use Case based on your messaging volume and specific requirements:

  • Low-Volume: Monthly fee of $1.50 for businesses sending fewer than 5,000 message segments per day.

  • High-Volume: Monthly fee of $10 for businesses sending more than 5,000 message segments per day.

Special Use Cases

Certain use cases come with additional requirements and specific rules, each associated with its corresponding monthly fee:

  • Agents and Franchises: $30/month

  • Charity / 501(c)(3) Nonprofit: $3/month

  • Emergency: $5/month

  • K-12 Education: $10/month

  • Political: $10/month

  • Proxy: $10/month

  • Social: $10/month

  • Sweepstake: $10/month

Fee Transparency and Reporting

Rest assured, LimePhone provides detailed reports of all pass-through fees, which are deducted directly from your account balance. Stay informed and in control of your A2P 10DLC expenditures with LimePhone's transparent fee structure.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article