Getting Started with 10DLC: Use Case Registration

Use Case Registration tells carriers what you’ll text about so they can verify your organization's sending type to ensure it complies with 10DLC rules. If you’ve finished Brand Registration, you’re ready to register your use case and submit the required examples. Use Case Registration is required before you can text from a 10DLC number. Vetting typically takes 3–12 business days, so plan your registration timeline accordingly. This guide walks you through picking a Use Case and providing the items carriers need to review.


Before you start Use Case Registration, you should already be familiar with the following information:


TABLE OF CONTENTS


How to Register Your Use Case (Step by Step)

After your Brand Registration has been processed, you can begin Use Case registration and select a use case that best aligns with your texting program. When filling out the form, you can save a draft and submit for review when ready. To begin this process, complete the following steps:

  1. Open the Compliance page under Account Tools in your GetThru account. If Brand Registration is complete, the Use Case section will be available below the Brand section.
  2. Click on Start Use Case Registration.
    Compliance page to start use case registration
  3. Select a Use Case from the list (Special if eligible; otherwise Standard). See our Special vs. Standard section below for more details on use case types and eligibility.
    Use Case Selection
  4. Add two Sample Initial Messages. Carriers require two unique samples for your selected Use Case. These are examples only and are not sent to contacts. 
    • Samples should meet the following requirements:
      • Be two unique messages.
      • Ensure both messages align with your selected Use Case (e.g., Standard use case samples cannot be political in nature).
      • Identify your organization in the text.
      • Include clear opt-out instructions such as “Reply STOP to opt out.” Avoid ambiguous phrasing (e.g., “Stop2End”) and explicitly say “Reply” or “Text” STOP.
      • Use brackets for variables (e.g., “[name]”, “[sender name]”) in samples only; do not use brackets in actual outgoing messages.
      • Include a link in at least one of the two sample messages.

    • Compliant Example: “Hi [name], this is [sender name] with the Bart Campaign for Prop 837. You can read more at www.yestoprop837.com or attend a meeting, reply to get upcoming dates. Reply STOP to opt out.”

  5. Add Sample Media for MMS. You can do this step during the initial use case registration or after SMS use case approval. 
    • If you have already uploaded media to the Media Library, you'll be able to immediately upload media via the +Add Media button.
      Compliance page add media button
    • If you have not uploaded media to your library yet, you'll be directed to upload your first media and taken to a new tab to the Media Library page. Make sure to resume from your initial tab after uploading media to save your progress.Compliance page upload first media link
  6. Provide a Help Message that identifies your organization and includes your homepage URL.
    • This is the message you’d send if a contact asks for help or replies “HELP.” It must:
      • State your organization’s name.
      • Provide a contact method (email, phone, or website).
      • Include help instructions (e.g., “Reply HELP for assistance”).
      • Include opt-out instructions (“Reply STOP to opt out”).
      • Link to your homepage (required to complete registration).

    • Compliant Example: “Thanks for reaching out! You’re texting with [Organization Name]. Visit [homepage URL] or email [contact] for assistance. Reply HELP for help or STOP to unsubscribe.”

  7. Give URLs for Website Requirements: Contact Source/opt-in, Privacy Policy, Terms & Conditions. Check out the Website Requirements section below for more details.
  8. Click Save Draft if you do not want to submit yet for review or click Submit Registration to submit for Manual Vetting and watch for status updates during the approx. 3–12 business days vetting manual vetting review.
    Compliance page to start use case registration


What Is Manual Vetting?

Manual Vetting is part of the requirements for 10DLC. It helps U.S. carriers reduce spam and improve message deliverability. Manual Vetting is a carrier-required review performed by a third-party team after you submit your Use Case Registration. The vetting team reviews your organization’s website for specific criteria before carriers approve your Use Case. ThruText campaigns cannot launch without an approved Use Case.


Use Case Statuses and Vetting Timeline

Once you have submitted the Use Case Registration form, the stages of review will begin. As your use case moves through registration and vetting, you’ll receive email updates and can review the current Vetting Step and status on the Compliance page's Use Case section.

  • Pre-Submission: If you have started your Use Case Registration and save it as a draft, you will see the Continue Use Case Registration option.
  • Submitted:
    • GetThru Internal Review: You submitted the form. During Support Hours, within 1-2 hours of submission, GetThru reviews your site for Manual Vetting readiness, and either submits your registration downstream or emails you with any recommended updates. If concerns arise, we’ll email you with the subject Action Needed - Use Case Registration Updates and provide details in the Compliance page's Feedback field. The timeline for moving to the next step depends on when the necessary updates are made to your website.
      • At initial submission:GetThru under review use case
      • If GetThru feedback is received and updates are needed:
        GetThru rejected use case 
  • Messaging Provider Automated Review: Once GetThru confirms the website requirements have been met, we submit the registration to our messaging partner. They complete an automated check of the use case within the first hour of submission, and if there are no concerns, they move it forward to the third-party vetting team. Rejections at this stage may be resolvable without further website changes.
    • When under review with the messaging provider:
      Messaging provider under review use case
    • If provider feedback is received and updates are needed:
      Messaging provider rejected use case
  • Manual Vetting: Carriers have received the use case for Manual Vetting. When your Use Case reaches this state, you’ll receive an email titled Use Case is in Manual Vetting. It is not usable yet.If rejected, you'll receive an email notice for next steps, titled Action Needed - Use Case Registration Updates, and new Feedback will be available from the Compliance page. It takes an estimated 3–12 business days for the outcome once submitted. Plan your texting timeline accordingly.  Manual vetting under review use case
    • If Rejected: If your Use Case is rejected at any point, you'll receive an email from support@getthru.io and we’ll share the rejection details, advise on required website updates, and submit an appeal when you’re ready. Please note: appeals reset the Manual Vetting clock, adding another 3–12 business days to the process.
      Manual vetting rejected use case
  • Approved: Manual Vetting is complete, and your Use Case is ready for texting. 
    • You’ll receive an automated confirmation email titled Success - Use Case Accepted.
      SMS approved use case
    • If you did not submit MMS media during your initial use case submission, you'll see the SMS status as Approved and the MMS status as Pending with an Enable MMS Messaging option. You can follow the steps in the following guide to get MMS approved after SMS approval: MMS Approval - Adding Sample Media to a Use Case.
      MMS approved use case

Once your use case is approved, you can check your vetting score and sending limits details from the Compliance page. Please check out our guide 10DLC Sending Limits - Throughput and Queuing for more information on that process.


Special vs. Standard Use Cases

Special Use Cases (Preferred by Carriers)

Selecting a Special Use Case when you’re eligible helps align carrier expectations with your actual sending, reducing errors and improving throughput. To understand the capacity model behind this, see 10DLC Sending Limits - Throughput and Queuing.

  • Political — Eligible for 501(c)3/4/5/6 and 527 organizations. This Use Case receives preferential sending treatment. Donation-related texts can be sent via a Political Use Case.
  • Charity — For 501(c)3s sending donation-focused messages. If your 501(c)3 messages aren’t primarily donation-focused, choose Political (if political program) or Higher Education (for student/campus comms).

If your Tax Exempt Status isn’t displayed on the Compliance page in the Brand Vetting section, contact Support.

Screenshot of the Brand Information card, with a green rectangle around the center column, "Tax Exempt Status" "501c3".

Standard Use Cases

Choose the one that best matches your texting program:

  • Higher Education — Messages on behalf of colleges and universities (501(c)3 institutions must instead use Charity if donation-focused).
  • Customer Care — Customer support or service communications; unions texting members may use this.
  • Polling and Voting — Preference surveys about consumer goods/services (not for political messaging).
  • Public Service Announcement — Informational alerts about important events (e.g., road closures).


Use Cases by Organization Type

Organizations may register one Use Case by default. A second Use Case is available only to 501(c)3 organizations, and the eligibility criteria are detailed below.

Organization TypeRecommended Use CaseNot Eligible / Notes
527PoliticalCampaign Verify Token required.
501(c)4 / 501(c)5 (unions) / 501(c)6PoliticalNot eligible for Charity.
501(c)3 (donation-focused)CharityEligible for second Use Case only as Charity + Political (if political program).
501(c)3 (campus/student comms)Higher EducationEligible for a second Use Case only as Charity + Higher Education.
No tax-exempt statusMost relevant standard use caseOnly eligible for a standard use case. Outreach cannot be political or donation-focused. 
Consultants/ResellersMatch client’s org type & programUse separate accounts/EINs per client.



Website Requirements

Manual Vetting requires three separate pages with separate criteria to ensure contacts know what they’re opting into. Make sure these pages are published before you submit. Review the linked guide for each requirement for more details: 

  • Contact Source: A page on or linked from your website where people actively opt in to text messaging (place the opt-in message near the phone field) and link to your Privacy Policy and Terms & Conditions. Use our Opt-In Language Generatorto help craft compliant opt-in language for your contact source.
    • Opt-In Message Example: "By providing your phone number, you agree to receive [type] text messages from [organization name]. Message and data rates may apply. Message frequency varies. Reply HELP to request help or STOP to opt out of text messages. Privacy Policy [here] and Terms & Conditions [here]."
  • Privacy Policy: A page that states that you do not sell or share text opt-in data or consent with third parties or affiliates for their marketing and shares instructions on how users can opt out of receiving text messages. The page must be linked from your contact source opt-in message. Use our Privacy Policy Generatorto help craft a compliant privacy policy for your website.
    • No Selling/Sharing For Marketing Example: "Text messaging opt-in data and consent will not be sold or shared with third parties or affiliates for their marketing or promotional purposes."
  • Terms & Conditions: A page that includes text messaging terms (Msg & data rates may apply, HELP/STOP instructions), and is linked from your contact source page. Use our Terms & Conditions Generatorto help craft compliant terms for your website.
    • Text Messaging Terms of Service Example: "By signing up for text message updates, you agree to receive [type] text messages from [Your Organization Name] at the mobile number provided by the user. Message frequency may vary based on your interactions, upcoming events, or important notices from [Your Organization Name]. Message and data rates may apply. You can request help by responding to a text message with HELP or by emailing [email@example.com]. You can opt out of receiving text messages at any time by replying STOP to any message. See our Privacy Policy [here]"


Helpful Resources