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)

  1. Open the Brand & Use Case Registration page under ThruText Tools in your GetThru account. If Brand Registration is complete, Use Case Registration will be available on the right.
  2. Select one Use Case (Special if eligible; otherwise Standard).
  3. Add two Sample Initial Messages that match your selection. (Form boxes 1 and 2)
  4. Provide a Help Message Reply that identifies your organization and includes your homepage URL. (Form box 3)
  5. Give URLs for Website Requirements: Contact Source/opt-in, Privacy Policy, Terms & Conditions. (Form boxes 4, 5, and 6)
  6. Click Register Use Case to submit for Manual Vetting and watch for status updates. Vetting typically completes in 3–12 business days.


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.


How Use Case Registration Works

You will select the Use Case type that best describes your texting program. 

Screenshot of the Use Case Registration page showing radio-button options for different use case types and a ‘Register’ button. Intended to illustrate where you choose the use case that best matches your texting program.


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 Throughput and Queuing Post-10DLC.

  • 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).


NOTE - If your Tax Exempt Status isn’t displayed on the Brand & Use Case Registration page in the Brand Information 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.


Required Fields for Use Case Registration

After you select a Use Case type, the required fields for use case registration will appear in the form.

Annotated screenshot of the Use Case Registration form. An arrow indicates the selected use case. Numbered callouts highlight six fields: two sample initial message boxes, a help-message reply box, and three URL fields for opt-in/contact source, privacy policy, and terms & conditions. Used to show exactly where each required item is entered.


Sample Messages

Carriers require two unique sample initial messages for your selected Use Case. These are examples only and are not sent to contacts. 


Checklist

  • Provide 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.”


Help Message Response

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).


Template

“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.”


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 Generator to 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 Generator to 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."
    • Clear Opt-Out Instructions Example: "Text Message Opt-Out: If you are receiving text messages from us and wish to stop receiving them, simply respond with either “STOP” or “UNSUBSCRIBE” to the number from which you received the message. You will not receive further text messages unless you opt back in."
  • 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 Generator to 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]"


Use Case Statuses and How to Know Vetting Is Complete

Once you have filled out all the Use Case Registration form sections, click Register Use Case. As your use case moves through registration and vetting, you’ll receive email updates and can review the status on the Brand & Use Case Registration page next to the submitted Use Case type.

  • Pre-Submission: Before registration is submitted, there is no status bubble.
  • A screenshot of "Pending" from the registration card where a chosen use case displays a pending badge.Pending: You submitted the form; GetThru is doing a quick check. If concerns arise, we’ll email you the same business day. This status means the Use Case has not entered Manual Vetting.
  • A screenshot of "Registered" from the registration card where a chosen use case displays a registered badge.Registered: 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 of the rejection, titled Action Needed - Failed Use Case Registration, but the status will stay registered. 
  • Approved: Manual Vetting is complete, and your Use Case is ready to text. You’ll also receive an automated confirmation email titled Success - Use Case Accepted. For next steps to get MMS approved, see the guide Adding Sample MMS to a Use Case.

Annotated screenshot of the Use Case Registration status panel. An arrow points to the registration card where a chosen use case displays an approval badge, indicating manual vetting is complete.


Timeline: How Long Manual Vetting Takes

The process includes three stages:

  1. Preliminary Review (GetThru): 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. When your registration moves to the next stage, you'll get an email from notifications@getthru.app. If your registration needs updates, you'll get an email from support@getthru.io, and the status will remain Pending. The timeline for moving to the next step depends on when the necessary updates are made to your website.
  2. Messaging Provider Preliminary Review: Once GetThru confirms the website requirements have been met, we submit the registration to our messaging partner. They quickly check it before submission to the third-party vetting team, which will pass or fail this stage within an hour. Rejections at this stage may be resolvable without further website changes.
  3. Third-Party Vetting (Carriers’ Vendor): Estimated 3–12 business days for the outcome once submitted. Plan your texting timeline accordingly.


If Your Use Case Is Rejected: How to Appeal

If your Use Case is rejected at any point, email support@getthru.io. 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.


Helpful Resources