Manage SMS messaging codes with Connect – Community Engagement

Connect app discontinued

The mobile app for Connect has been discontinued, but you can still access Connect on your web or mobile browser at finalsiteconnect.com.

Messages XR Enterprise is our newest communications solution. It provides a modern, feature-rich platform, including a companion sender app. Reach out to your Client Success Manager or email clientsuccess@finalsite.com to learn more.

Connect sends SMS from short code 63079 or a 10-digit local number (10DLC) — administrators manage the code type, set up a required KeyCode prefix for 10DLC, and share opt-in/opt-out instructions with families.

💡Quick answers

What numbers do Connect SMS messages come from? Short code 63079 (outreach and emergency) or a 10-digit local number (10DLC) for outreach — with 63079 still handling emergencies for 10DLC schools.
What is a KeyCode? A unique 2–7 character alphanumeric prefix automatically added to every 10DLC message — required by carriers to verify the sender and prevent opt-out conflicts between schools.
What are the KeyCode requirements? Must be 2–7 alphanumeric characters containing at least one letter (numbers-only codes are not accepted), and must be unique across the Connect system.
How do families opt back in after opting out? Text START, GO, SUBSCRIBE, RESUME, JOIN, or UNBLOCK to the school's number — or START [KeyCode] to rejoin one specific school.

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) for Outreach messages.

Messages coming from the 5-digit number 63079 are both outreach and emergency short codes.
Messages coming from a 10-digit local number are 10-digit long codes (10DLC).

Step 2: Recognize your message sources

For schools using 10DLC:

Outreach messages will come from your unique 10-digit number.
Emergency messages will still come from 63079.

For schools using short codes:

Outreach and emergency messages will come from 63079.

These codes are standardized across all buildings in your school community.

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

For schools and districts migrating to 10DLC, a KeyCode is automatically included. This is a unique 2–7 character alphanumeric prefix attached to the beginning of every SMS message.

Why is a KeyCode required?

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

Format	Status	Example	Compliance Reason
Letters Only	✅ Yes	`CENTHS`	Meets alphanumeric standards and allows for unique opt-out tracking.
Letters + Numbers	✅ Yes	`FSD101`	Recommended. Combines branding with a unique identifier.
Numbers Only	❌ No	`12345`	Strictly Prohibited. Carriers will block these as "spoofed" or invalid IDs.

⚠️ Compliance and availability

KeyCodes act as unique routing addresses. If two schools share a code, an opt-out (like "STOP") for one could accidentally blacklist a parent from the other.

This uniqueness ensures TCPA compliance and prevents carrier spam filtering. Since codes are assigned first-come, first-served, we will help you find an effective alternative if your first choice is already in use.

✅ Ready to set your KeyCode?

If you are currently migrating to 10DLC, your KeyCode and 10-digit numbers are prepared in advance by the migration team. You will receive advanced visibility on these details during your scheduled migration window.
Once you have selected a prefix that meets the requirements above, please reach out to Connect support. They will verify the global uniqueness of your choice and configure the 2–7 character alphanumeric prefix for your organization(s) in the system.

Step 4: Manage subscriptions and "opt-back-in" requests

Due to TCPA compliance, if a user texts "STOP" to a messaging code, they are globally unsubscribed from that source. Administrators cannot manually resubscribe a user; the user must initiate the opt-in from their own device.

To opt back into text messaging, users should text one of the following keywords:

START
GO
SUBSCRIBE
RESUME
JOIN
UNBLOCK

For outreach and emergency messages: Text the keyword above to 63079.

For 10DLC users: Text the keyword to your specific 10-digit local number.

The user will receive a confirmation message once they are successfully subscribed again.

Step 5: Share with your community

Announce your new messaging numbers using the following templates:

Template #1: Email template

Subject: Important Update: New SMS number for urgent communications

Dear [Community Name],

We have a new number specifically for emergency text messages.

Starting today, you’ll receive:

Emergency and outreach text messages from the code 63079.

This change allows us to maintain message deliverability while returning to the familiar setup of separate numbers for emergency and general messages.

We encourage you to save both numbers in your contacts so you can quickly recognize messages from our school.

Thank you,

[Your Name]
[Your Title]
[District Name]
[Contact Information]

Template #2: SMS/Text template

[School/Dist Name] We have a new number for emergency alerts. You’ll now get outreach and emergency text messages from the code 63079. Please save to your contacts!