Alphanumeric sender IDs overview

AI-generated summary

Genesys Cloud provides Alphanumeric Sender IDs (ASIDs) as a sender type for outbound Short Messaging Service (SMS) messaging, enabling organizations to use customizable text strings such as brand names instead of traditional numeric identifiers. ASIDs support outbound digital campaigns, queue-based outbound SMS, and agentless SMS via public APIs, but do not support inbound messaging, Multimedia Messaging Service (MMS), or media communication. ASIDs must adhere to strict formatting requirements: they must contain 3 to 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," "Bank," "Security," and similar terms should be avoided to prevent carrier delivery blocking. Registration requirements vary by country. Supported countries that do not require ASID registration include Austria, Croatia, Cyprus, Denmark, Estonia, Germany, Greece, Latvia, Lithuania, Luxembourg, Netherlands, Norway, Portugal, Sweden, Switzerland, Poland, and the United Kingdom (for non-protected ASIDs only). Length restrictions and generic-name rules are subject to vendor and country regulations, enforced during provisioning. Messages sent to unsupported or unregistered countries are not blocked upfront but may fail at delivery; delivery receipts are generated for tracking. In some unregistered countries, messages may be delivered from alternative sender types. Administrators provision ASIDs through SMS Number Inventory by selecting Add Numbers, choosing Alphanumeric, and entering the desired sender ID. ASIDs require single provisioning for multi-country use, appearing in the SMS number inventory with alphanumeric type, no MMS support, and blank country designation. ASIDs are reusable across multiple countries where vendor policies permit and can be utilized across different organizations and regions. The platform supports ASIDs across key messaging capabilities including outbound digital campaigns (with 700 messages per minute throughput aligned to International Longcode baseline), queue-based outbound SMS with alphanumeric string configuration, and agentless messaging via public APIs supporting ASIDs in From or Sender fields with standard format validation. For countries requiring ASID registration, the registration process must be completed first, after which SMS Operations manually provisions the ASID in the SMS Number Inventory; if the registered ASID shares the same name as an existing one, it becomes available for use in that country upon registration completion. Billing for ASIDs 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 invoicing alphanumeric usage under the same outbound rate classes as long codes and combining usage into a single line item if both long codes and alphanumeric sender IDs are used

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 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 you should avoidClick to expand

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

It is a good practice to 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 may 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, potential scam.

ASIDs are designed specifically for SMS and come with certain functional limitations. They 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 SMS Number Inventory, select Add Numbers and then choose Alphanumeric.
Enter your desired ASID in the Sender ID field. You only need to provision an ASID 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 if the name differs from 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 utilized for messaging in multiple countries (where vendor policies allow). They can be used in multiple organizations regardless if 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 additional 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 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, we combine the usage into a single line item on the invoice.

[NEXT] Was this article helpful?

Get user feedback about articles.

Alphanumeric sender IDs overview View summary