10DLC Registration Process for Plivo Customers

    10-digit long code (10DLC) is a service offered by US mobile network operators (MNO) to explicitly allow A2P messaging over long code phone numbers. 10DLC numbers provide lower surcharges, higher throughput, and less content filtering than unregistered long codes.

    Note:If you don’t send messages to US mobile numbers using long codes, you don’t need to register your phone numbers for 10DLC service.

    To register for 10DLC service, you must first register your brand, which involves providing information about the business that’s sending messages.

    Once the brand is successfully registered, you must register campaigns, the 10DLC term for messaging use cases.

    Finally, you must link the phone numbers that you’ll use to send messages with registered campaigns.

    Plivo lets businesses perform these tasks on the 10DLC page of the Plivo console or by using our API.

    Registration for resellers

    Two types of business may register for 10DLC.

    • Direct customers are those who send messages for their own business — companies that send one-time passwords to their users for login, for instance.
    • Resellers provide communication services to other businesses and use Plivo’s messaging APIs on behalf of their customers.

    While registration is straightforward for direct businesses, which need to register just their own brands, it’s a little more complicated for resellers. Resellers must register each of their customers as a separate brand; they may not use their brand as a proxy for their customers’. A violation of this rule is likely to result in the suspension of the brand’s messaging campaigns.

    Consider a hypothetical messaging provider, Ovilp Corp., that provides a messaging platform for organizations that send messages in the US. Its customers are hospitals and medical practitioners that might send messages such as

    • appointment alerts for patients
    • marketing announcements to opted-in customers
    • two-factor authentication (2FA) codes for individuals to use to log in to patient portals

    Ovilp also has a console for their customers’ tech teams that requires 2FA to log in. This diagram shows this flow in action.


    Ovilp must register its business and each of its clients’ businesses as separate brands and specify their respective use cases (campaigns).

    Note: Resellers that don’t have messaging requirements of their own can forgo registering their own business and proceed to register their customers.

    To ensure its own messages are registered for 10DLC services, Ovilp must

    • Register itself as a brand
    • Create a campaign corresponding to its 2FA use case
    • Link Plivo long codes to the campaign

    Then, per the diagram above,

    • For Client A, Ovilp must

      • Register A’s brand
      • Create a campaign for A’s marketing use case
      • Link numbers to this campaign
    • For Client B, Ovilp must

      • Register B’s brand
      • Create campaigns for each of B’s use cases, or create a mixed campaign with correct subtypes
      • Link numbers to the campaigns. Note that any number may be linked to only one campaign.


    Resellers need to repeat the process for each of their customers.

    See our 10DLC registration guidelines for advice on how to register brands and campaigns.