Ireland (IE)

Locale name

Ireland

ISO code
The International Organization for Standardization two character representation for the given locale.

IE

Region

Europe

Mobile country code
A three digit code associated with the given locale and used in conjunction with a Mobile Network Code to uniquely identify mobile networks.

272

Dialing code
The dialing prefix used to establish a call or send an SMS from one locale to the given locale.

+353

Two-way SMS supported
Whether Twilio supports two-way SMS in the given locale.

Yes

Number portability available
Whether number portability is available in the given locale.

Yes

Twilio concatenated message support
Concatenation refers to the capability of splitting a message that is too long to be sent in one SMS into smaller pieces and then joining the pieces at the receiving end so that the receiver sees the message as one. 

Yes*
For certain sender ID types this may not be supported. Where messages are split and rejoined may vary based on character encoding.

Message length
How many characters can be sent given a particular message encoding before the message will be split into concatenated segments.

-----

Twilio MMS support
Multimedia Messaging Service (MMS) provides a standards-based means to send pictures and video to mobile phones.

Converted to SMS with embedded URL

Sending SMS to landline numbers
How Twilio handles an SMS message destined for landline telephone number.

You cannot send SMS to a landline destination number: the Twilio REST API will throw a 400 response with error code 21614, the message will not appear in the logs, and the account will not be charged.

Compliance considerations
Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. This table lists some general best practices.

Message delivery to M2M numbers is on best effort basis only.

Sending cannabis related content is strictly prohibited.

Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. The following are some general best practices:

1. Get opt-in consent from each end user before sending any communication to them, particular for marketing or other non-essential communications.
2. Only communicate during an end user's daytime hours unless it is urgent.
3. SMS campaigns should support HELP/STOP messages, and similar messages, in the end user's local language.
4. Do not contact end users on do-not-call or do-not-disturb registries.

Operator network capability
Whether mobile operators in the given country support the feature.

Not Required

Supported

Twilio supported
Whether Twilio supports the feature for the given country.

---

Supported
Learn more

Sender ID preserved
In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.

---

Yes

Provisioning time
Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.

N/A

N/A

UCS-2 support

N/A

Supported

Use case restrictions

N/A

Twilio will start blocking on 06/06/2024 messages submitted from MEF-Protected Sender IDs for which customers have not provided an LOA letter. In case you are experiencing delivery issues related to a MEF-Protected Sender ID, please reach out to senderid@twilio.com to provide the LOA proving that you are legitimate and authorised carrier of the traffic related to the specific Sender ID.

For more information, visit MEF Protected Sender ID Instructions for IE

___________________________________________________________
The use of generic Sender IDs should be avoided as they are being blocked from the operators.

Best practices

N/A

Please refrain from using generic sender IDs like SMS, TEXT, InfoSMS, INFO, Verify, Notify etc to avoid being blocked by network operators.
___________________________________________________________
Twilio suggests using an Alpha Sender ID that is related to the content of the message.

Operator network capability
Whether mobile operators in the given country support the feature.

Supported

Supported

Supported

Twilio supported
Whether Twilio supports the feature for the given country.

Supported

Supported

Not Supported

Sender ID preserved
In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.

Yes

Yes

---

Provisioning time
Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.

N/A

N/A

N/A

UCS-2 support

N/A

Supported

N/A

Use case restrictions

N/A

The network Meteor Ireland doesn't support International Longcodes. Traffic submitted to Twilio with an International longcode will be attempted to be delivered on a based effort basis and the Longcode will be replaced from an Alpha Sender ID outside Twilio's platfrom.

N/A

Best practices

N/A

It is strongly recommended to use Alphanumeric Sender ID when sending one-way Application-To-Person (A2P) traffic to Ireland (IE). To support two-way requirement to carry on a conversation, Twilio offers Shortcode and Domestic Longcodes.

N/A