Alphanumeric sender IDs overview

AI-generated summary

Genesys Cloud provides Alphanumeric Sender IDs (ASIDs) as a sender type for Short Messaging Service (SMS) messaging, enabling organizations to use customizable text strings such as brand names instead of traditional numeric senders. ASIDs support outbound digital campaigns, queue-based outbound SMS, and agentless SMS via public APIs, with throughput aligned to International Longcode baseline rates of 700 messages per minute. However, ASIDs do not support inbound messaging, Multimedia Messaging Service (MMS), or media communication. ASIDs must adhere to strict formatting requirements: they must contain 3- include at least one alphabetic character (A-Z in uppercase or mixed case), and may combine letters with digits. Numeric-only values, special characters, and spaces are not permitted. Generic names such as "OTP," "Verify," "Alert," "Bank," and similar terms should be avoided to prevent carrier delivery blocking, with these restrictions subject to vendor and country regulations enforced during provisioning. Registration requirements vary by country. Supported countries without ASID registration include Croatia, Cyprus, Denmark, Estonia, France, Germany, Greece, Japan, Latvia, Lithuania, Luxembourg, Netherlands, Norway, Poland, Portugal, Sweden, Switzerland, and the United Kingdom. Other countries require ASID registration with specific regulatory documentation. Messages sent to unsupported or unregistered countries are not blocked initially but may fail at delivery; delivery receipts are generated for tracking. In some unregistered countries, messages may be delivered through alternative methods such as long codes or unregistered alphanumeric sender IDs. Provisioning Administrators can create ASIDs in countries without registration requirements through the SMS Number Inventory by selecting Add Numbers and entering the desired sender ID. For countries requiring ASID registration, the registration process must be completed first, after which SMS Operations manually provisions the ASID in the inventory. ASIDs can be provisioned only once but are reusable across multiple countries and organizations where vendor policies permit. Billing for ASID usage is usage-based with no additional setup or recurring charges. SMS messages sent using ASIDs are billed identically to outbound Longcode SMS at per-country, per-message-segment rates, with Genesys consolidating alphanumeric and long code usage into a single invoice line item using the same outbound rate classes

An Alphanumeric Sender ID (ASID) is a sender type used for Short Messaging Service (SMS) messaging. Unlike traditional numeric senders, ASIDs allow you to use a customizable string (for example, a brand name) as the sender. ASIDs do not support inbound messaging, Multimedia Messaging Service (MMS), or media communication.

Supported countries that do not need ASID registrationClick to expand

Supported countries that need ASID registrationClick to expand

Supported use casesClick to expand

Format and validation rules

ASIDs must follow strict formatting guidelines to ensure compatibility across carriers and countries.

Formats allowedClick to expand

Formats not allowedClick to expand

Generic names that to avoidClick to expand

These names can include but not be limited to the following generic names:

1TimePin, 2FA, Accept, Access, Account, Active, Admin, Advise, Alert, Allow, Allowance, App, Appointment, Approve, Approved, Auth, AuthMsg, Authorise, AuthSMS, Aware, Bank, Banking, Bill, Billing, Call, Card, Caution, Certify, Check, CloudOTP, Code, Collect, Collection, Confirm, Contact, Control, Courier, Delay, Deliver, Delivery, Discount, Energy, Fraud, Help, Info, InfoSMS, ISA, Key, Loan, Login, Logistics, LogMeIn, Logon, Network, NoReply, Notify, Malware, Message, Mobile, Mortgage, MSG, MsgAuth, OneTimePin, Order, OTP, OTPSMS, Package, Parcel, Pay, Payment, Pin, PinCode, Post, Protocol, Purchase, Ratify, Rebate, Receipt, Refund, Reminder, Repayment, Reply, Respond, Save, Saving, Savings, Schedule, Secure, Security, Service, Shipping, Sign, Signin, Signon, SMS, SMSAuth, SMSCode, SMSInfo, SMSOTP, SMSVerify, Support, System, Text, Trace, Track, Tracking, Trust, TXT, Update, Updates, Validate, Verify, VerifySMS, VerifyMe, Virus, Warn, Warning, Winner.

Genesys recommends that you avoid using generic names in ASID to prevent carriers from potential delivery blocking.

Additional considerationsClick to expand

Behavior and limitations

Messages that are sent to unsupported or unregistered countries are not blocked upfront. These messages can fail at delivery and delivery receipts are generated and available for ASID traffic. For some unregistered countries, messages can be delivered from a long code or from an alphanumeric sender ID. For example, a potential scam.

ASIDs are designed specifically for SMS and come with certain functional limitations and support only SMS text messages. They do not support MMS or image messaging, cannot be used for inbound messaging or replies, and are not selectable in inbound flows.

Provisioning

Administrators can provision ASIDs in countries where registration is not required.

In the SMS Number Inventory, select Add Numbers and then choose Alphanumeric.
Enter your desired ASID in the Sender ID field. You can provision an ASID only once, even if you plan to use it across multiple countries.

After provisioning, the ASID appears in the SMS number inventory list with:

Type: Alphanumeric
MMS Support: No
Country: Blank (since it can be used across multiple countries)

For countries that require ASID registration, complete the registration process first. SMS Operations will then manually provision the ASID in your SMS Number Inventory when the name differs from the one you have already created. If the registered ASID uses the same name as an existing one, it becomes available for use in that country once registration is complete.

Reusability

The same ASID can be used for messaging in multiple countries (where vendor policies allow). They can be used in multiple organizations regardless when it is the same region or in other regions.

Usage across products

ASIDs are supported across key messaging capabilities within the platform.

Outbound digital campaignsClick to expand

Queue-based outbound SMSClick to expand

Agentless messaging (public API)Click to expand

Billing

ASIDs are currently introduced without extra setup or recurring charges. Billing is usage-based. SMS messages sent using ASIDs are billed the same as outbound Longcode SMS. Charges are applied per country and per message segment. Genesys invoices for alphanumeric usage using the same outbound rate classes as long codes, and it appears on the invoice under the corresponding outbound rate class. If you use both long codes and alphanumeric sender IDs, Genesys combines the usage into a single-line item on the invoice.

[NEXT] Was this article helpful?

Get user feedback about articles.