An Independent Service Vendor (ISV) is a type of business that sells products and services to other end users who are also businesses. If your end-users are a separate business entity, you are in fact an ISV.

For example, a SaaS product that sells messaging services to doctor’s offices is considered an ISV. A business that specializes in SMS marketing for other businesses is also considered an ISV. The relationship between Telnyx, an ISV, and that ISV's customers can be represented as shown in the diagram:

If your business is an ISV, for every end-user you’re reselling to, you will need to create a separate brand.

After creating the brand, you will need to create campaigns so that you can assign campaign IDs to the phone numbers. It is critical that you do not share the phone numbers across multiple brands. By doing so, you will violate the terms of usage for 10DLC and potentially will get fined and blocked until the traffic is compliant.

Once you create your campaign, assign the campaign ID to a set of phone numbers. You can assign a maximum number of 49 phone numbers.

In general, 10DLC campaigns for ISVs should resemble the structure shown in the diagram. Note the separation of traffic between end-users Company 1 and Company 2.

To be 10DLC compliant, every number needs to be associated with a campaign, and each campaign can only be associated with one brand. This means that no two brands can be on the same number. If you are currently sharing numbers across brands, unless you have a special arrangement with the mobile network operators, you will need to update your messaging architecture such that only one brand is using any given number to send messages. Mobile network operators will not approve ISVs for special consideration in this case.

We recommend that you take an iterative approach to migrate this architecture end-user by end-user:

Now in your messaging application's backend code, add logic such that the end-user you’re working on starts using the Messaging Profile and Phone Number created above.