Let’s dive into how SMS messaging works with ClientTether, focusing on GSM vs. Non-GSM characters. Understanding this will help you manage your messages more effectively and enhance the experience for your recipients.

GSM Characters in ClientTether For most of your messaging needs within ClientTether, sticking with GSM characters is your best bet. Here’s why:

• A single SMS can hold up to 150 characters. If your message exceeds this limit, it’s split into chunks of 150 characters each. For instance, a message with 161 characters would be sent as one segment of 150 characters and another with just 11 characters.
• The SMS segments are counted in increments of about 150 characters:
  • Up to 150 characters = 1 SMS Segment
  • Up to 300 characters = 2 SMS Segments
  • Up to 450 characters = 3 SMS Segments
  • …and so on.
• Curious about which characters are GSM? Check out this list of GSM characters!

Non-GSM Characters in ClientTether Non-GSM characters are a bit trickier but still supported:

• The character limit per SMS segment drops to 65 characters. Not all devices or networks handle these well, and they might appear as separate messages.
• Here’s how SMS credits tally up with Non-GSM characters:
  • 65 characters = 1 SMS Segment
  • 150 characters = 2 SMS Segments
  • 195 characters = 3 SMS Segments
  • …and so on.
• To help you avoid unintentionally using Non-GSM characters, here’s a tool to identify them.

Detecting Non-GSM Characters Great news! ClientTether automatically alerts you if there are Non-GSM characters in your message. If Non-GSM characters are detected, the outline of the text box turns red, the character count adjusts, and an info bubble pops up next to the Message Label with a quick explanation.

If you want to double-check your message for Non-GSM characters before sending, try this recommended Non-GSM Detector and Segment Calculator.

Just so you know, the character counts mentioned include space for headers that specify the encoding system used. Our reporting on character splits gives you a conservative estimate to help you plan your SMS segments effectively.

Happy messaging!

Important registration requirement for A2P 10DLC messaging, which is essential for ensuring the continued delivery of your application-to-person (A2P) text messages.  As you may already be aware, A2P 10DLC is a messaging framework introduced by major mobile carriers in the United States to enhance the reliability and deliverability of application-to-person SMS messages.

This is also part of the FCC’s recent initiative to limit texts from illegitimate numbers which have been exploding over the past few years.

To comply with the new requirements, it is imperative that you complete the registration quickly. Beginning  Sept 1, 2023, carriers have the right to block messages that come from unregistered phone numbers.

Watch this video on Registering for A2P 10DLC with ClientTether:

In order to successfully complete the registration, it is vital that you have your Business Employer Identification Number (EIN) documents readily available. These documents are a mandatory requirement for registration and will help validate your business and messaging traffic.

Your CSM will assist you in placing the necessary information in the registration form, including:

1. Business Profile Details: Please provide accurate and up-to-date information about your company, including contact details.
2. Brand Registration: Identify and register the brand(s) you intend to use for sending A2P messages. This includes providing brand names, business categories, and any relevant brand documentation.
3. Campaign Registration: If you have specific campaigns planned, your CSM will guide you through the registration process. Be prepared to share campaign details, such as purpose, start and end dates, message content, and expected volume.

We understand that this may seem like a complex process, but we assure you that our CSMs are here to provide dedicated support and ensure that your registration is completed in a timely manner.  Failure to complete the registration before the Sept 1 deadline may result in immediate disruptions to your A2P messaging services.

Should you have any questions, concerns, or require further clarification, please don’t hesitate to contact your CSM. We are committed to assisting you every step of the way to ensure a seamless transition to the A2P 10DLC framework.  Thank you for your immediate attention to this matter. We greatly appreciate your cooperation and look forward to continuing to support your messaging needs.