Overview: Multi-Entity Texting and 10DLC

If you send texts on behalf of more than one organization or legal entity, it’s important to keep those messages separate to meet 10DLC rules and protect message deliverability. This guide explains how your legal structure (EINs, fiscal sponsorships, and sub-accounts) affects 10DLC registration in ThruText, and what setup you need so your messages keep going through without interruption.


TABLE OF CONTENTS


10DLC registration is tied to legal entities and tax IDs (EINs), not just to how you organize your work internally.

  • If you have multiple legal entities with different EINs, each entity needs its own ThruText account, brand registration, and 10DLC use case.
  • If your organization is fiscally sponsored, you send under the fiscal sponsor’s EIN and brand registration, and the use case makes it clear which sponsored organization is texting.
  • If you have one legal entity with one EIN, but need multiple ThruText accounts for organizational reasons (for example, different states or departments), those accounts generally share the same brand registration, but are separated in ThruText to keep your work organized.

The sections below walk through each scenario and what you need for 10DLC.


Why You Must Separate Texting by Brand Identity

Using one brand registration for multiple unrelated entities, or not clearly reflecting sponsorship relationships, can create compliance and deliverability risks. Separating traffic by brand identity helps you avoid these issues.

  • Increased risk of filtering: Texts from multiple legal entities using a single brand identity violate 10DLC regulations. Carriers may respond by increasing filtering.
  • Deliverability issues can affect multiple entities: If one entity’s texting is flagged under 10DLC rules, it can impact the deliverability of texts for all other entities sharing that ThruText account or brand registration.
  • Phone number limits apply per use case: A single 10DLC use case on a brand is allowed a limited number of active phone numbers at a time. Separating traffic by entity helps ensure that one organization’s number usage does not limit or complicate number management for another.

By segmenting your texting traffic so that each ThruText account is associated with a single brand identity, you reduce risk and make it easier to manage registrations, numbers, and compliance.


How to Set Up Separate Accounts for Each Brand

To stay compliant with 10DLC rules, each legal entity should have its own ThruText account and its own 10DLC brand and use case registration.


Follow these steps:

  1. Request a new sub-account for each additional organization
  2. Contact Support to Confirm Your Structure
    • Email support@getthru.io with details on whether you have multiple EINs, a fiscal sponsor, or both.
    • Our team will confirm the appropriate account and registration structure based on your scenario.
  3. Complete Brand Registration
    • For each ThruText account, complete the Brand Registration form using that entity’s legal name, tax ID (EIN), and other required information. Make sure the information you provide matches official tax records.
    • If you are working under a fiscal sponsor, use the fiscal sponsor’s information. Make sure the website(s) you provide align with the brand and clearly describe the fiscal sponsorship relationship.
    • For full details on the registration form, see our Brand Registration guide.
  4. Submit 10DLC Use Case Registrations
    • Submit a 10DLC use case application that accurately describes the texting program(s) using that account.
    • Use the client or sponsored organization’s website when appropriate, ensuring it clearly explains any fiscal sponsorship relationships.

    • For more information, see our 10DLC Use Case Application guide.


This scenario applies if you send texts for more than one legal entity, such as:

  • A 501(c)(3) and a 501(c)(4)
  • Multiple political campaigns or committees
  • Separate organizations that are your clients

Because each entity has its own EIN, carriers and The Campaign Registry (TCR) treat them as separate brands.


What this means for your setup:

  • Each legal entity must have its own ThruText account (or sub-account).
  • Each entity must have its own brand registration, using its legal name and EIN.
  • Each entity must have its own 10DLC use case registration, describing its texting program and contact acquisition.

You should not send messages for multiple EINs from the same ThruText account or under the same 10DLC brand.


Fiscal Sponsors and Brand Registration

In a fiscal sponsorship, your organization uses a fiscal sponsor’s legal and tax status (including EIN), but you may have your own program name, branding, and website.


Carriers require texting traffic to be sent on behalf of the organization listed in the brand registration. Sending messages on behalf of a different legal entity than the registered brand violates 10DLC regulations and may lead to message filtering.


In a fiscal sponsorship:

  • The fiscal sponsor’s details (legal name and EIN) are used for brand registration, because that is the entity TCR reviews against tax records.
  • The sponsored organization is made visible through the use case registration and your website, which must clearly explain the relationship.


What this means for your setup:

  • Brand Registration
    • Complete the Brand Registration using the fiscal sponsor’s legal name and tax ID (EIN).
    • TCR validates this information against official tax records, so it must match the fiscal sponsor.
  • Website and relationship language
    • During use case registration, third-party Manual Vetting reviews your website to confirm it matches the brand registration.
    • Your website should clearly indicate the fiscal sponsorship relationship, for example in the footer:
      • “Organization X is fiscally sponsored by Organization Y.”
    • This helps reviewers connect the fiscal sponsor’s brand registration to your organization’s texting program.
  • Use case registration
    • When you submit your 10DLC use case, you should provide the sponsored organization’s website (the client’s site), not the fiscal sponsor’s website.
    • Manual Vetting will review that website; it must clearly state the relationship to the fiscal sponsor as described above.
  • Policies and contact language
    • We recommend referencing the fiscal sponsor in your Contact Source, Privacy Policy, and Terms & Conditions so that reviewers can easily confirm the relationship.
    • This additional context supports a smoother vetting process and reduces the risk of delays or rejection.

The brand is registered under the fiscal sponsor’s EIN, and the use case + website make it clear which sponsored organization is actually sending messages under that brand.


Some organizations have one legal entity and one EIN, but still need multiple ThruText accounts.

Common examples include:

  • A national organization with state-by-state programs
  • A school, college, or university where each department runs its own texting campaigns
  • A single nonprofit with multiple internal teams or projects

In these cases, all of the texting programs are part of the same legal entity, even if they have different names or internal structures.


What this means for your setup:

  • All of these accounts can typically share one brand registration, based on the single legal entity and EIN.
  • You may still choose to create multiple ThruText accounts (or sub-accounts) to keep your texting work organized by state, department, or program.
  • In your use case registration(s), you should describe the types of messages you send in a way that covers the accounts texting plans. 

If you’re not sure whether a program is part of the same legal entity or if it should be treated as a separate brand, reach out to support@getthru.io and we can help you determine the best setup.


After Your Registrations Are Approved

After you complete brand and use case registration for each entity:

  • Use each ThruText account only to send messages on behalf of the brand listed in that account’s registration.
  • Do not send texts for multiple EINs from the same account or under the same brand registration.
  • If you are using a fiscal sponsor, continue to keep your website, policies, and messaging aligned with the relationship described in your registration.
  • If your organizational structure changes (for example, you add a new entity or change fiscal sponsors), contact support@getthru.io so we can review your registrations.

Keeping your texting traffic aligned with your EINs, sponsorships, and organizational structure helps you stay compliant with 10DLC rules and protects message deliverability across all of your programs.