Registry Q&A

Short Message Service (SMS) is universally accessible and allows mobile phone users to send and receive plain text messages. In 2024, 2.3 billion texts were sent in Ireland.

Europe Economics estimates that the quantifiable harm to consumer and businesses in Ireland from scam texts is approximately €115 million per year.

No. The SMS Sender ID Registry is only for organisations that send A2P SMS messages from a SenderID typically to their customers or clients.  As a consumer, you DO NOT need to register your mobile phone number.

As an example, ‘234 BANK’ that sends SMS messages to consumers using a Sender ID ‘234BANK’ (displayed at the top of the text message), will need to register the Sender ID ‘234BANK’ so they, and nobody else, can use that Sender ID.

Yes.  You can search for registered Sender IDs in the ‘Sender ID Search’ option of the SMS Sender ID Registry.

If it is registered, you will be able to see the organisation that owns that Sender ID.

The SMS Sender ID Registry only applies to Application-to-Person (A2P) messages, where a business’ computer systems are used to send messages on behalf of businesses or organisations.

The SMS Sender ID Registry does not affect person-to-person SMS messages, such as those sent from one person to another via their mobile device.

The SMS Sender ID Registry also does not affect applications such as WhatsApp. Short Message Service or SMS is universally accessible and allows mobile phone users to send and receive plain text messages. SMS differs from messaging applications such as WhatsApp that require users to have the app installed on their mobile phone and support more advanced features e.g. embedded images, video calls and group chats.

ComReg will endeavour to process your application as quickly as possible.  It is envisaged during the early implementation phase of the Registry that the number of Sender ID applications will be high. We anticipate that complete and valid applications will be approved within 3 to 5 working days.

A Sender ID must be of alphanumeric format having a minimum of 3 characters and a maximum of 11 characters, which is the technical maximum set in the relevant international telecoms standards.

The relevant international telecom standard (3GPP Specification 23.040 Technical realization of the Short Message Service (SMS)) imposes an upper limit of 11 characters for Alphanumeric SenderIDs.

A single organisation may hold several Sender IDs, but ordinarily no more than twenty. In the event that an organisation requests more than twenty Sender IDs, ComReg aims to ensure that requests for Sender IDs are genuine and therefore reserves the right to request further information or documentation to determine the need based upon its merits.

No. A Sender ID must not contain predominantly numbers, except for permitted Network Dialable (short) Numbers; other requests will be considered on a case-by case basis.

There are currently no fees for registering a SMS Sender ID. ComReg however reserves the right to review its position and introduce a fee in the future, in accordance with Regulation 81 of the 2022 Regulations.

A list of Participating Aggregators is publicly available on the SMS Sender ID Registry – please use the Participating Aggregators Search within the SMS Sender ID Registry Portal.

Only registered Participating Aggregators (PA) will be able to carry SMS with registered Sender IDs.  If your SMS Provider (SMS Aggregator) cannot or will not sign up to the Registry Rules you will need to reroute your SMS traffic through a different, registered PA.

Whatever the case of the Sender ID requested through the Registry Portal, it will be stored in the Registry database in that same case.  For example, if Sender ID “Abcdef” is requested, then “Abcdef” will be saved in the Registry database. SIDOs are free to originate SMS in any choice of case.

Any subsequent request to register a pre-existing registered Sender ID which differs only in the case used will be rejected as it is a duplicate.  For example, Sender ID “Abcdef” has already been registered.  A subsequent request to register “ABCDEF” will be rejected as it will be seen as a duplicate.

Alphanumeric Sender ID must have a minimum of 3 characters and a maximum of 11 characters.

The maximum limit is imposed by global technical standards: 3GPP Specification 23.040 Technical realization of the Short Message Service (SMS).

In special circumstances, where an organisation can clearly demonstrate that a Sender ID having less than 3 characters will not cause confusion to the end user, unambiguously identifies the organisation and cannot be substituted with a longer Sender ID, ComReg may consider this case.

Alphanumeric Sender IDs must not be generic in nature (for example ‘SMS’, ‘Verify’, ‘Doctor, ‘Dentist’, ‘Flowers’ etc. are not allowed).

Your organisation may wish to register a Sender ID that links its organisation to the Sender ID that in part contains a generic word. For example, Organisation ‘ABC’ sells flowers.  Organisation ‘ABC’ may wish to register the Sender ID ‘Flowers’, but this will not be allowed as it is generic.  Organisation ‘ABC’ could register an alternative Sender ID, for example ‘ABCFlowers’.  This Sender ID clearly identifies the organisation, and part includes a generic word and would therefore be considered for registration as it is not totally generic in its entirety.

Registration is a simple two-step process:

1. If not already authorised to operate in Ireland, you must register as an electronic communications service or electronic communications network provider on ComReg’s Electronic Register of Authorised Undertakings (ERAU).
2. Once registered, sign up on the Registry portal to become a PA or participating MSP. Click on the ‘Sign-Up’ button and select ‘I’m applying to be a Participating Aggregator/Mobile Service Provider’ to complete your registration.

Yes. If your organisation is an overseas Aggregator and wishes to continue to send SMS with a Sender ID to Irish mobile numbers, it must become a Participating Aggregator by first registering as an electronic communications service or electronic communications network provider on ComReg’s Electronic Register of Authorised Undertakings (ERAU).

Information on registering as a Participating Aggregator is set out in document ComReg 24/97.

Use the ‘Sign-Up’ function within the SMS Sender ID Registry Portal and select ‘I’m Applying to be a Participating Aggregator/Mobile Service Provider’ to then register.

Note that all SMS destined for Irish Mobile numbers must be delivered by an SMSC operated by or on behalf of an Irish MSP, and not via a ‘grey route’.

Yes, a Participating Aggregator may register its own customer’s SMS Sender IDs on their behalf, ensuring that the Eligibility Criteria set out in Section 7.2(8) of the Numbering Conditions of Use and Application Process are met. The organisation customer will need to assist in this process by confirming their Sender IDs with ComReg.

Yes, registered Participating Aggregators or Participating MSPs (only) can register a Shared Sender ID.  The Shared Sender ID may be assigned to the PA or Participating MSP for use by their own customers who do not wish to register their own Sender ID.

Yes. An MSP can register its own Sender IDs. These are typically Sender IDs used by Mobile Network Operators/Mobile Virtual Network Operators for sending SMS messages to their own customers.

Whatever the case of the Sender ID requested through the Registry Portal, it will be stored in the Registry database in that same case.  For example, if Sender ID “Abcdef” is requested, then “Abcdef” will be saved in the Registry database. SIDOs are free to originate SMS in any choice of case.

When checking if a message’s Sender ID has been registered, MSPs and PAs should match that Sender ID against the list of registered Sender IDs in a case-insensitive manner.  In other words, if the Sender ID “Abcdef” has been registered, messages with a Sender ID of “Abcdef” as well as for example “ABCDEF” or “aBcDeF” should be considered valid in this context.

API calls (by PAs and MSPs) to the Registry requesting output files containing registered Sender IDs will likewise list Sender IDs in the case they were originally registered as.

A Sender ID Owner (SIDO) could contract a 3rd Party to send their SMS messages on their behalf via a Participating Aggregator (PA), rather than send them directly.

The Sender ID Rights Of Use remains with the Sender ID Owner and not the 3^rd Party.

A 3^rd Party (ISV) cannot be the Sender ID Owner (SIDO) of all its clients’ Sender IDs -the clients of the 3^rd Party (ISV) are the Sender ID Owner (SIDO) of their own Sender ID(s).

If a Sender ID Owner (SIDO) uses a 3^rd Party, then they must select the correct 3^rd Party when making a new Sender ID request. This function is supported in the Registry Portal.

3^rd Parties should impress upon their clients (SIDO)s the need to register their own Sender IDs to ensure their text messages are not affected.

Yes, if your organisation received an email from the email address senderid@comreg.ie to indicate that your SMS Sender ID is pre-registered with ComReg, it is a genuine email.   

It is important to follow the instructions in the email to fully register your SMS Sender ID with ComReg.  

You need to confirm to ComReg the SMS provider(s) you allow to send SMS messages on your behalf.  

If you do not fully register your SMS Sender ID before 3 July 2025, your SMS messages to customers and clients will be labelled “Likely Scam” to alert end users that the text messages may not be legitimate and to be cautious of the content of the messages.  

ComReg is introducing the SMS Sender ID Registry to help prevent text scams in Ireland. 

ComReg recently issued over 5000 emails to organisations whose SMS Sender IDs had been pre-registered with ComReg by their SMS provider.  

ComReg now needs to confirm with these organisations that the SMS Sender IDs are legitimate and is contacting organisations directly to do so.  

Please follow the instructions in the email you received from senderid@comreg.ie to confirm to ComReg the SMS provider(s) you allow to carry your SMS messages and to fully register your SMS Sender ID.    

ComReg is introducing the SMS Sender ID Registry to help prevent text scams in Ireland. 

Your SMS provider supplied your contact details to ComReg during an industry process in late 2024/early 2025.  

This process was put in place to pre-register as many existing and legitimate SMS Sender IDs as possible so that these SMS Sender IDs would not be modified to “Likely Scam” from 3 July 2025.  

ComReg has been urging SMS providers to make their business customers aware of the need to register their SMS Sender IDs since late 2024.  

If you received an email from senderid@comreg.ie please follow the instructions within the email to ensure that your SMS Sender IDs are fully registered.  

ComReg is introducing the SMS Sender ID Registry to help prevent SMS text scams in Ireland. 

Yes, you still need to follow the instructions in the email you received from senderid@comreg.ie 

You need to do this to confirm to ComReg the SMS provider(s) you allow to send SMS messages on your behalf.  

After completing that step and following ComReg validation and confirmation by email, your SMS Sender ID will be fully registered with ComReg and will not be modified to “Likely Scam” from 3 July 2025. 

This issue may occur if there was a problem during the password setup process. To resolve it, please go to the SMS Sender ID Registry portal at https://senderid.comreg.ie and click on the “Login” box. On the welcome screen, select the “Forgotten Password?” option. This will generate a new password reset email, which will be sent to your registered email address.  

Open that email, click the link provided, and follow the on-screen instructions to create a new password, and return to the login page and try signing in again. 

If the problem persists, please send an email to senderid@comreg.ie, including your organisation name and the email address you are registering with, so that further assistance can be provided. 

The SMS Sender ID Registry application is optimised for desktop and laptop use. Some features may not display or function fully on mobile devices. Users are advised to switch to a larger screen when using the Registry.