Manage SMS messaging codes with Messages XR Enterprise

This article helps district administrators understand SMS messaging codes in Messages XR Enterprise, including the difference between short codes and 10DLC, how to identify message sources, and how to manage KeyCode prefixes (also called abbreviations).

Step 1: Identify your messaging type: Short Code or 10DLC

Determine whether your school or district is using short codes or 10-digit long codes (10DLC). If 10DLC isn't set up for your organization, messages send from short codes.

• Messages coming from the 5-digit number 97178 are an outreach short code.
• Messages coming from a 10-digit local number are 10-digit long codes (10DLC). 
• Emergency messages from districts still on short code come from the shared short code 53291. Districts on 10DLC send emergency messages from their own emergency 10DLC number.
• Tipline notifications come from 54968.

Step 2: Recognize your message sources

For schools using 10DLC:

• Outreach messages will come from your school's unique 10-digit number.
• Emergency messages will come from your school's own emergency 10-digit number, which is different from its outreach number.

For schools using short codes:

• Outreach messages will come from 97178.
• Emergency messages will come from 53291.

Short codes are standardized across all buildings in your school community and are shared by all Finalsite clients, so they can't identify who sent a message. 10DLC numbers are assigned to each school individually, so families know exactly who is texting them. If 10DLC isn't configured for your school or district, begin each message with your school or district name followed by a colon (e.g., "Lincoln Elementary:"). This prevents messages from being treated as spam and makes the sender immediately recognizable. Abbreviations are acceptable if familiar to the community.

To see your 10DLC numbers, go to Settings > Organization config, select the district or school, and look under Delivery Options for Outreach 10DLC Number(s) and Emergency 10DLC Number(s).

Step 3 (for 10DLC users): Request your KeyCode (UID)

For schools and districts migrating to 10DLC, a KeyCode (also called your school or district abbreviation) is automatically included. This is a unique 2–8 character alphanumeric prefix attached to the beginning of every SMS message. Each school has its own KeyCode. Messages sent by the district use the district's KeyCode. 

• Carrier compliance: Mobile carriers now require a non-numeric identifier to verify the sender. To meet these guidelines, KeyCodes must be alphanumeric (containing at least one letter) and cannot be numbers only.

• Global uniqueness & safety: Every KeyCode must be unique within the Messages XR Enterprise system. This prevents "opt-out conflicts"—ensuring that if a parent unsubscribes from one school, they aren't accidentally blocked from a different institution using a similar code.

• Instant identification: A custom prefix (e.g., CENTHS) allows parents to instantly know which school is contacting them before they even open the message.

KeyCode (UID) prefix requirements and examples

• Length: Must be between 2 and 8 characters.

• Format: Must be Alphanumeric (must include at least one letter; cannot be all numbers).

• Style: Use capital letters, no spaces, and no special characters.

• Availability: Must be globally unique (not already in use by another school).

Step 4: Share with your community

Announce your new messaging numbers using the email and SMS templates in Communication templates: Share SMS information with your community. Each message you send automatically begins with your KeyCode, so don't type your school or district name at the start of the message. Families will know exactly who is texting them, which builds trust and can lead to higher open rates and stronger engagement. Encourage parents and students to save your school's 10DLC numbers in their phones so they can easily recognize its messages.