Required regulatory documentation for alphanumerics ID purchase

AI-generated summary

Genesys Cloud requires users to complete regulatory documentation and registration for Alphanumeric Sender IDs (ASIDs) across multiple jurisdictions before deployment to ensure message delivery compliance. ASID regulatory requirements vary significantly by country, with unregistered ASIDs in regulated jurisdictions subject to blocking, replacement with generic labels, or delivery failure after designated deadlines. Australia mandates ASID registration and approval by the Australian Communications and Media Authority (ACMA) by June 30, 2026, with unregistered ASIDs labeled as Unverified or Blocked starting July 1, 2026. The registration process requires creating an ACMA portal account with details matching the Australian Business Register, submitting organization information to Genesys Cloud including Org ID, ASID, Australian Business Number, business name, website, and authorized representative details, and completing ACMA verification. Users must provide use case explanations demonstrating how the ASID represents their company, brand, or service, with supporting documentation such as business registration, trademark, or domain certificate if the ASID differs from the business name. Austria requires all ASIDs used for SMS messaging to Austrian recipients to be registered with the RTR (Austrian Regulatory Authority for Broadcasting and Telecommunications) by October 1, 2026. Users should contact genesyscloudsms@genesys.com to initiate the registration process. Finland requires all alphanumeric sender IDs to be registered with Traficom (Finnish regulator) before use by April 10, 2026, with an annual EUR 200 fee. Unregistered sender IDs will be replaced with "Tuntematon" (unknown) by May 4, 2026. Registration involves a mandatory 14-day activation period, after which Traficom issues an SMS number beginning with 19. Required documentation includes Genesys Cloud OrgID, ASID, company name, headquarters address, company email, and proof of relationship between company/brand and ASID. After Traficom approval, organizations must email registration details to genesyscloudsms@genesys.com for aggregator processing and SMS Inventory provisioning. France classifies certain ASIDs as ISA (interdit sauf autorisation—prohibited until authorized) by operators and regulators, requiring prior authorization before use. Non-ISA classified ASIDs can be provisioned immediately without pre-registration. Protected ASID registrations require Genesys Cloud OrgID, ASID, traffic type specification, URL/phone number indicators, company name, company website, and a Letter of Authorization. ASIDs are restricted to transactional messaging only; non-transactional use cases may result in message blocking. Ireland mandates that all businesses register ASIDs in the ComReg Sender ID Registry; unregistered IDs are replaced with "Likely Scam" notifications as of July 3, 2025. The registration process involves verifying ASID availability through the ComReg registry on a first-come, first-served basis, creating a Sender ID Owner account with business information, requesting the desired ASID and designating Genesys Cloud Services Inc. as third-party administrator with Sinch Sweden AB as the Original Participating Aggregator, verifying the account via email confirmation, and registering the ASID with Genesys by submitting the Genesys Cloud OrgID and ComReg-assigned SIDR ID to genesyscloudsms@genesys.com. Italy requires mandatory ASID registration with AGCOM before SMS deployment; unregistered ASIDs will be blocked or fail delivery. Italian registrations require submission of Genesys Cloud OrgID, ASID, traffic type classification, company details, fiscal code/VAT number, authorized representative information, use case explanation, and a Letter of Authorization. Italian regulations mandate that promotional and marketing messages include opt-out mechanisms such as website links or toll-free numbers, as ASIDs do not support inbound replies. Genesys registers the ASID on the customer's behalf upon receipt of a signed Letter of Authorization. Singapore requires organizations to register directly with the Singapore SMS Sender ID Registry (SSIR) before sending SMS messages; unregistered ASIDs are replaced with "Likely Scam" messaging. The registration process involves creating an SSIR account with required business details, selecting Sinch Singapore Pte Ltd as the Participating Aggregator, and paying one-time setup and annual fees per ASID. After SSIR

Regulatory requirements for Alphanumeric Sender IDs (ASIDs) vary by country. In the countries listed below, you must complete registration and submit supporting documentation before using an ASID for messaging. If you use an unregistered ASID in these countries, messages may be blocked or fail to deliver.

Review each country’s requirements to identify any mandatory ASID registrations. After you prepare the required materials, email genesyscloudsms@genesys.comto start the ASID registration process. If you have questions, contact the same email address.

For more information about provisioning ASID and enabling it use post completing registration, see Alphanumeric sender IDs overview.

AustraliaClick to expand

From June 30, 2026, all ASIDs to Australian numbers must be registered and approved by the ACMA to combat fraud. Unregistered ASIDs are labeled as Unverified or Blocked starting July 1, 2026.

How to register your ASID in Australia?

Step 1: Create an account in the Australian Communications and Media Authority (ACMA) portalClick to expand

Step 2: Register ASID with GenesysClick to expand

After creating the account, email the details the below table to genesyscloudsms@genesys.com. Genesys will forward this information to our aggregator for processing.

Information Required	Required Documentation
Genesys Cloud OrgID ASID Australian Business Number (ABN) Business Name Website Primary Business Address Primary Business City Primary Business State (ACT, NT, NSW, QLD, SA, TAS, ...) Primary Business Postal Code Primary Business Phone Number (must be a local Australia contact number) Authorized representative details (name, job title, email, phone (must be a local Australia contact number)) Use case: : You must explain that your ASID clearly represents your company, brand, or service. The ASID should directly match or relate to your business name, trademark, product, or a recognizable abbreviation.	Proof of valid use case: Upload a use case supporting document if the ASID is not the same as your business name. The following document types are accepted: Business registration Trademark Domain certificate

Information Required

Required Documentation

Genesys Cloud OrgID
ASID
Australian Business Number (ABN)
Business Name
Website
Primary Business Address
Primary Business City
Primary Business State (ACT, NT, NSW, QLD, SA, TAS, ...)
Primary Business Postal Code
Primary Business Phone Number (must be a local Australia contact number)
Authorized representative details (name, job title, email, phone (must be a local Australia contact number))
Use case: : You must explain that your ASID clearly represents your company, brand, or service. The ASID should directly match or relate to your business name, trademark, product, or a recognizable abbreviation.

Proof of valid use case: Upload a use case supporting document if the ASID is not the same as your business name. The following document types are accepted:
- Business registration
- Trademark
- Domain certificate

*Ensure that your authorized representation details are accurate and up to date, as they will be used for all registration updates.

Step 3: Complete verification with the ACMAClick to expand

After Genesys submits the registration, the ACMA emails the authorized representative to verify the registration and confirm their identity. You must complete this step before the ASID can be fully registered and enabled for use. Follow the instructions you receive in the email to complete the verification process. For more information, see Use the ACMA register for the first time.

Once you complete verification, Genesys receives confirmation of the successful registration and notifies you by email when you can provision the ASID in SMS Inventory and begin using it.

Note: Upon completion of registration, the ACMA contacts the entity’s representative via email to verify the registration in the ACMA Assist portal. Follow the instructions in the email to verify ASID registration.

AustriaClick to expand

To comply with Austrian regulations established by the RTR (The Austrian Regulatory Authority for Broadcasting and Telecommunications), all ASIDs used to send SMS messages to recipients in Austria must be registered by October 1, 2026. After this date, messages sent using an unregistered ASID may not be delivered.

Note: After an ASID registration is submitted, there is a mandatory 14-day waiting period before the ASID becomes active in the RTR registry. Once the registration has been completed, the submitted information (such as the contact email address) cannot be changed. If any registration details need to be updated, a new ASID registration must be submitted, and a new 14-day waiting period will apply.

Information Required	Required Documentation
Genesys Cloud OrgID ASID Relationship between the company/brand and the requested ASID. The ASID must meet one of the following criteria: The ASID is identical to the company/owner name. The ASID is a registered trademark of the company/owner. The ASID is identical to the internet domain used by the company and is associated with the company/owner. Company name Company headquarter address Company email	N/A

Information Required

Required Documentation

Genesys Cloud OrgID
ASID
Relationship between the company/brand and the requested ASID. The ASID must meet one of the following criteria:
- The ASID is identical to the company/owner name.
- The ASID is a registered trademark of the company/owner.
- The ASID is identical to the internet domain used by the company and is associated with the company/owner.
Company name
Company headquarter address
Company email

N/A

FinlandClick to expand

Finland has introduced mandatory registration requirements for alphanumeric sender IDs, effective April 10, 2026, where all sender IDs must be registered with the Finnish regulator (Traficom) before use. By May 4, 2026, any sender that that is not registered will be replaced with sender ID Tuntematon (which means unknown in Finnish). For more information, see SMS Sender ID regulations.

How to register your ASID in Finland?

Step 1: Access the ASID applicationClick to expand

Step 2: Submit the ASID applicationClick to expand

Step 3: Register ASID with GenesysClick to expand

After Traficom successfully registers your ASID, email the information in the table below to genesyscloudsms@genesys.com.

Genesys forwards this information to our aggregator for processing. Once the registration is approved, we notify you by email so you can provision the ASID in SMS Inventory and begin using it.

Information Required	Required Documentation
Genesys Cloud OrgID ASID Use case/Type of traffic (transactional, trust-related, promotional) Company name Company website	N/A

France (Protected ASIDs)Click to expand

In France, certain ASIDs are classified as ISA, interdit sauf autorisation (meaning, prohibited until authorized) by mobile operators and regulatory bodies. ASIDs falling under this classification require prior authorization and must be registered before they can be used for SMS messaging. For more information, see France protected ASID list.

If an ASID appears as an ISA on the protected ASID list, it cannot be used until it has been registered and approved. ASIDs that are not classified as ISA do not require pre-registration and can be provisioned and enabled for use immediately.

Information Required	Required Documentation
Genesys Cloud OrgID ASID Type of traffic (transactional, trust-related)* Indicate if the message content includes any URLs or phone numbers Company name Company website	Letter of Authorization Documentation subject to review*

*In France, ASIDs are intended for transactional messaging only. Use cases that are not strictly transactional may result in message blocking.

**The Letter of Authorization (LOA) will be provided to the customer by the SMS team via email upon receipt of the initial ASID request. This LOA authorizes Genesys to carry the SMS traffic. This document must be completed and returned by the customer.

***Each protected ASID is subject to individual review. Upon receipt of the required information, Genesys will work with our SMS aggregator to review the request. Additional information/documentation may be requested from the customer depending on the specific ASID and use case, and Genesys will provide guidance as needed.

IrelandClick to expand

To comply with regulations from ComReg (Irish communications regulator), all businesses sending SMS messages to Ireland using alphanumeric sender IDs must be registered in the ComReg Sender ID Registry. As of July 3, 2025, unregistered sender IDs are being replaced with Likely Scam.

Genesys Cloud OrgIDHow to register your ASID in Ireland?

For more information on the registration process, see Sender ID Registry Public Guide.

Step 1: Check if your ID is already registeredClick to expand

Step 2: Create a Sender ID Owner accountClick to expand

Step 3: Request the ASIDClick to expand

Step 4: Verify accountClick to expand

Step 5: Register ASID with GenesysClick to expand

After ComReg successfully registers your ASID, email the information in the table below to genesyscloudsms@genesys.com.
Genesys forwards this information to our aggregator for processing. Once approved, we notify you by email when the registration is complete, and you can provision the ASID in SMS Inventory and begin using it.

Information Required	Required Documentation
Genesys Cloud OrgID ASID SIDR ID: This is the SIDR ID assigned by ComReg. The SIDR ID is unique per end organization and can be reused in as many ASID registrations as needed. The SIDR ID can be found under the SIDO Registry account when clicking on the account icon located in the top-right corner.	N/A

ItalyClick to expand

Italy requires all ASIDs to be registered with the national regulator (AGCOM) before they can be used for SMS messaging. This is a mandatory requirement, meaning unregistered ASIDs will be blocked or not delivered.

Note: Under Italian privacy and GDPR requirements, promotional and marketing messages must include a clear method for individuals to opt out. As ASIDs do not support inbound messaging, recipients cannot reply directly to the message to opt out. Therefore, it is recommended that an alternative opt-out mechanism such as a website link or toll-free phone number is provided within the message.

Information Required	Required Documentation
Genesys Cloud OrgID ASID Type of traffic (transactional, promotional, transactional, and promotional) Company name Company address Company PEC email* Company Fiscal Code/VAT number** Authorized representative details (Full name, phone number, email) Use case: You must explain what the ASID will be used for and that your ASID clearly represents your company, brand, or service.	Letter of Authorization***

*If the company is based in Italy, provide the company’s official PEC (certified) email address. If the company is based outside Italy, provide the company’s official contact email address.

**If the company is based outside Italy, provide the company’s VAT number.

***The SMS team sends the Letter of Authorization (LOA) to the customer by email after receiving the initial ASID request. The LOA authorizes Genesys to register the Italy ASID on the customer’s behalf. The customer must complete and return the signed LOA.

SingaporeClick to expand

To send SMS messages using ASIDs in Singapore, all organizations must first register directly with the Singapore SMS Sender ID Registry (SSIR). Unregistered ASIDs are replaced with Likely Scam. For more information about the requirements, see SMS Registry.

How to register your ASID in Singapore?

For more information about the registration process, see SSIR portal user guide.

Step 1: Register with SSIRClick to expand

Step 2: Register ASID with GenesysClick to expand

After SSIR successfully registers your ASID, email the information in the table below to genesyscloudsms@genesys.com. After we receive your email, Genesys will:

Provide a Letter of Authorization (LOA) confirming that Genesys is your SMS aggregator. Complete and return the LOA.
Submit the LOA and ASID details to our aggregator for processing and approval.

Once the aggregator approves the registration, we will notify you by email. You can then provision the ASID in SMS Inventory and begin using it.

Information Required	Required Documentation
Genesys Cloud OrgID Alphanumeric Sender ID Company name	Letter of Authorization

SlovakiaClick to expand

Information Required	Required Documentation
Genesys Cloud OrgID ASID Company name	N/A

SloveniaClick to expand

Warning: Support for Slovenia ASIDs is not currently available in the Genesys Cloud European Sovereign Region (ESR). For more information about ESR support, see .

Information Required	Required Documentation
Genesys Cloud OrgID ASID Purpose of traffic (transactional, trust-related, promotional) Sample message content Company name Company address Company website	N/A

SpainClick to expand

To comply with regulations from the Spanish regulator (CNMC), businesses that send messages to Spain using alphanumeric sender IDs (ASIDs) must register their ASIDs in the National Alias Registry. Effective June 6, 2026, operators block messages sent with unregistered ASIDs. To ensure message delivery, register your ASIDs before sending messages to Spain.

How to register your ASID in Spain?

Step 1: Access the CNMC portalClick to expand

To access the CNMC Portal, use a valid digital certificate. Most European certificates are accepted by the Spanish government, while certificates issued outside the EU have lower chances of being accepted.

To check if your digital certificate is accepted, perform the following steps:

Install AutoFirma software on your computer.
Validate your certificate.
If your certificate does not get accepted, you can perform manually. See Digital Certification.

Step 2: Start a new registrationClick to expand

After you log in to the portal, note that the interface is available only in Spanish and does not provide an option to switch to another language. The portal also automatically logs you out after approximately 4–5 minutes, even if you are actively working on your request. To avoid losing your progress, save your request as a draft by selecting GUARDAR BORRADOR. You can return later and continue working on the same request.
The first section of the form contains fields for your organization's information. Within the CNMC portal, the Genesys Cloud customer is considered the End Client, and Genesys is considered the Third Party. However, in this section, enter the End Client's information in the Third Party fields. Use the following information to complete the fields:
- NIF of the End Brand: Enter the NIF of the End Client associated with the ASID.
- Official Company Name: Enter the End Client's legal company name.
- NIF of the Third Party submitting the request: The portal automatically populates this field from the login details.
- Full Name of the Third Party submitting the request: The portal automatically populates this field from the login details.
- Third Party Email: Enter the email address of the End Client or the individual in the End Client's organization who is submitting the request.
- Third Party Phone: Optional. If provided, enter the phone number of the End Client or the individual submitting the request.
The next section requests your organization's address information. Although the address fields appear optional, you must complete them before you can submit the request. Complete all address fields to avoid delays.
In the Request Type section, select Inscripción de Alias.
In the next section, enter your organization's authorized representative information.
- Select the Recibir notificaciones checkbox to ensure that the authorized representative receives email notifications about the registration status and updates.
In the next section, enter the ASID information and identify the other parties involved in the registration.
1. Click Añadir alias.
2. Enter the ASID information in the required fields.
  Note: In Spain, ASIDs are valid for a maximum of 24 months. If you do not specify an activation date, the ASID becomes active the day after the CNMC approves the registration. If you do not specify an end date, the portal automatically assigns the maximum validity period of 24 months.
After you enter the ASID information, add the participating aggregator.
1. Search for Sinch Communications Spain SL.
2. Click AÑADIR PROVEEDOR.
Next, add the Third Party (TERCEROS) information.
1. Click Añadir Tercero.
2. Select Persona jurídica.
Enter the following Genesys information:
1. Company Legal Name: Genesys Cloud Services B.V.
2. NIF/VAT (TERCERO): NL852043697B01
After you add Genesys as the Third Party, add the Third Party Representative information.
Click + REPRESENTANTE.
Note: The CNMC requires Third Party Representative information before you can submit the registration request.
When the representative details dialog box appears, contact genesyscloudsms@genesys.com to obtain the required Genesys representative information.
Enter the representative information.
Select the Recibir notificaciones checkbox.
Click Añadir representante.

Step 3: Submit the applicationClick to expand

Verify that you have entered all required information correctly. Select the confirmation checkbox to certify that the request is legitimate and that you accept the applicable terms.
Click REVISAR Y PRESENTAR to review your submission.
If the portal does not identify any errors, it opens the final review page. Review the information, select the confirmation checkbox at the bottom of the page, and click PRESENTAR to submit the registration request.
After you submit the request, the CNMC reviews the registration. If the CNMC requires additional information or corrections, it notifies you. You must respond within 10 working days; otherwise, the CNMC considers the request withdrawn.
After the CNMC completes its initial review, the authorized representative receives an email with instructions to complete the required verification and validation process.
When you log in to the portal to begin the verification process, select Autorización de alias.
During the verification process, the portal may prompt you to re-enter your organization's or the Third Party's (Genesys) information, as described in Step 2.
Enter the requested information to continue.

Note: The CNMC reviews and validates the registration request. The review process typically takes up to one month. However, because these regulations were recently introduced, processing may take up to three months until September 2026.

Step 4: Register the ASID with GenesysClick to expand

After your ASID is approved by the CNMC, send an email with the information in the table below to genesyscloudsms@genesys.com.

Genesys forwards this information to our aggregator for processing. After the aggregator approves the registration, we notify you by email. You can then provision the ASID in the SMS inventory and enable it for use.

Information Required	Required Documentation
Genesys Cloud OrgID ASID Company name Company tax ID (NIF/CIF or EU VAT)	N/A

United Kingdom (Protected ASIDs)Click to expand

How to register your ASID in UK?

In the United Kingdom, certain ASIDs are designated as protected by mobile network operators (MEF, BT/EE). Messages sent using these protected ASIDs required additional registration and must be added to an allow list to ensure successful delivery. For more information, see United Kingdom protected alphanumeric sender IDs.

If an ASID appears on the protected ASID list, it cannot be used until it has been registered and approved. Non-protected ASIDs may also be added to the allow list, however, registration is not required for their use. These ASIDs can be provisioned and enabled without undergoing the registration process.

Information Required	Required Documentation
Genesys Cloud OrgID ASID Type of traffic (e.g. marketing alerts, OTP, reminders, etc) URLs/phone numbers in the content? If yes, please provide all information* Company name Company website	Letter of Authorization Documentation subject to review*

*When a customer includes URLs or phone numbers in message content, these must be shared with Genesys Cloud so we can work with our aggregators to obtain approval.

** The Letter of Authorization (LOA) will be provided to the customer by the SMS team via email upon receipt of the initial ASID request. This LOA authorizes Genesys to carry the SMS traffic. This document must be completed and returned by the customer.

***Please note: Each protected ASID is subject to individual review. Upon receipt of the required information, Genesys will work with our SMS aggregator to review the request. Additional information/documentation may be requested from the customer depending on the specific ASID and use case, and Genesys will provide guidance as needed.

[NEXT] Was this article helpful?

Get user feedback about articles.

Information Required	Required Documentation
Genesys Cloud OrgID ASID Australian Business Number (ABN) Business Name Website Primary Business Address Primary Business City Primary Business State (ACT, NT, NSW, QLD, SA, TAS, ...) Primary Business Postal Code Primary Business Phone Number (must be a local Australia contact number) Authorized representative details (name, job title, email, phone (must be a local Australia contact number)) Use case: : You must explain that your ASID clearly represents your company, brand, or service. The ASID should directly match or relate to your business name, trademark, product, or a recognizable abbreviation.	Proof of valid use case: Upload a use case supporting document if the ASID is not the same as your business name. The following document types are accepted: Business registration Trademark Domain certificate

Information Required

Required Documentation

Genesys Cloud OrgID
ASID
Australian Business Number (ABN)
Business Name
Website
Primary Business Address
Primary Business City
Primary Business State (ACT, NT, NSW, QLD, SA, TAS, ...)
Primary Business Postal Code
Primary Business Phone Number (must be a local Australia contact number)
Authorized representative details (name, job title, email, phone (must be a local Australia contact number))
Use case: : You must explain that your ASID clearly represents your company, brand, or service. The ASID should directly match or relate to your business name, trademark, product, or a recognizable abbreviation.

Proof of valid use case: Upload a use case supporting document if the ASID is not the same as your business name. The following document types are accepted:
- Business registration
- Trademark
- Domain certificate

Information Required	Required Documentation
Genesys Cloud OrgID ASID Relationship between the company/brand and the requested ASID. The ASID must meet one of the following criteria: The ASID is identical to the company/owner name. The ASID is a registered trademark of the company/owner. The ASID is identical to the internet domain used by the company and is associated with the company/owner. Company name Company headquarter address Company email	N/A

Information Required

Required Documentation

Genesys Cloud OrgID
ASID
Relationship between the company/brand and the requested ASID. The ASID must meet one of the following criteria:
- The ASID is identical to the company/owner name.
- The ASID is a registered trademark of the company/owner.
- The ASID is identical to the internet domain used by the company and is associated with the company/owner.
Company name
Company headquarter address
Company email

N/A

Information Required

Required Documentation

Genesys Cloud OrgID
ASID
Use case/Type of traffic (transactional, trust-related, promotional)
Company name
Company website

N/A

Information Required

Required Documentation

Genesys Cloud OrgID
ASID
Type of traffic (transactional, trust-related)*
Indicate if the message content includes any URLs or phone numbers
Company name
Company website

Letter of Authorization**
Documentation subject to review***

Information Required

Required Documentation

Genesys Cloud OrgID
ASID
SIDR ID: This is the SIDR ID assigned by ComReg. The SIDR ID is unique per end organization and can be reused in as many ASID registrations as needed. The SIDR ID can be found under the SIDO Registry account when clicking on the account icon located in the top-right corner.

N/A

Information Required

Required Documentation

Genesys Cloud OrgID
ASID
Type of traffic (transactional, promotional, transactional, and promotional)
Company name
Company address
Company PEC email*
Company Fiscal Code/VAT number**
Authorized representative details (Full name, phone number, email)
Use case: You must explain what the ASID will be used for and that your ASID clearly represents your company, brand, or service.

Letter of Authorization***

Information Required

Required Documentation

Genesys Cloud OrgID
Alphanumeric Sender ID
Company name

Letter of Authorization

Information Required	Required Documentation
Genesys Cloud OrgID ASID Company name	N/A

Information Required

Required Documentation

Genesys Cloud OrgID
ASID
Company name
Company tax ID (NIF/CIF or EU VAT)

N/A

Information Required

Required Documentation

Genesys Cloud OrgID
ASID
Type of traffic (e.g. marketing alerts, OTP, reminders, etc)
URLs/phone numbers in the content? If yes, please provide all information*
Company name
Company website

Letter of Authorization**
Documentation subject to review***

Required regulatory documentation for alphanumerics ID purchase

[NEXT] Was this article helpful?

Loading...

Required regulatory documentation for alphanumerics ID purchase

[NEXT] Was this article helpful?