sms compliance

Sent logo
Sent TeamMay 3, 2025 / sms compliance / Article

Ireland SMS Compliance Guide: Regulations, Best Practices & Features for 2024

Explore Ireland SMS: compliance (GDPR, ePrivacy), features (two-way SMS), & best practices. Understand GSM-7 (160 chars) vs UCS-2 (70 chars) encoding. Includes opt-in/out, sending windows (09:00-18:00 IST), number portability, plus API integration code (Twilio, Sinch). Avoid error 21614.

Ireland SMS Best Practices, Compliance, and Features

Understanding the Ireland SMS Market

Locale name:Ireland
ISO code:IE
RegionEurope
Mobile country code (MCC)272
Dialing Code+353

Market Conditions: Ireland maintains a highly developed mobile market with widespread SMS usage. The main operators include Vodafone Ireland, Three Ireland, and Eir Mobile. According to ComReg, Ireland maintains mobile penetration above 100%, with approximately 5.5 million active subscriptions serving a population of 5.1 million. While OTT messaging apps like WhatsApp and Facebook Messenger are popular, SMS remains crucial for business communications and authentication – particularly for two-factor authentication (2FA), transactional notifications, and marketing campaigns. The market shows an even split between Android and iOS devices, with slight iOS preference in urban areas.

For businesses sending SMS internationally, see our guides on SMS regulations by country and international SMS best practices.

SMS Features and Technical Capabilities in Ireland

Ireland offers comprehensive SMS capabilities, including two-way messaging, concatenated messages, and number portability. MMS converts to SMS with embedded URL links.

Two-way SMS Support

Two-way SMS is fully supported in Ireland, enabling interactive business messaging and customer engagement. No special restrictions apply. Response latency typically ranges from 1–5 seconds for delivery receipts and inbound messages, depending on carrier network conditions.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenation is fully supported across Irish networks.

Message length rules: Standard GSM-7 encoding allows 160 characters per message, while UCS-2 encoding limits messages to 70 characters before splitting.

Billing: Each segment is billed as a separate SMS. A 320-character message in GSM-7 encoding bills as 3 SMS units (153 + 153 + 14 characters, with 7 characters reserved per segment for concatenation headers beyond the first segment).

Encoding considerations: Use GSM-7 for standard Latin alphabet messages and UCS-2 for messages with special characters or non-Latin alphabets. Certain characters – {, }, [, ], ~, |, , and \ – consume 2 characters in GSM-7 encoding.

MMS Support

MMS messages convert automatically to SMS with an embedded URL link to the media content. This ensures compatibility across all devices while maintaining rich media sharing. Use HTTPS URLs with valid SSL certificates, keep URLs under 30 characters where possible, and ensure media files remain accessible for at least 72 hours. Include clear instructions like "View image: [URL]" to guide recipients.

Recipient Phone Number Compatibility

Number Portability

Number portability is available in Ireland under ComReg regulations. Porting requests typically complete within 1 working day for mobile numbers. Routing updates occur automatically through the Mobile Number Portability (MNP) system, which maintains a central routing database updated in real time. SMS delivery continues unaffected during and after porting – queries to the MNP database ensure correct routing to the current carrier.

Sending SMS to Landlines

Sending SMS to landline numbers is not supported in Ireland. Messages to landline numbers return a 400 response with error code 21614 – the message is neither delivered nor charged to your account.

Ireland SMS Compliance: GDPR and ePrivacy Regulations

Ireland follows strict data protection and electronic communications regulations governed by the Data Protection Commission (DPC) and ComReg (Commission for Communications Regulation). All SMS marketing in Ireland must comply with both GDPR (General Data Protection Regulation) and ePrivacy Regulations (S.I. No. 336/2011). Non-compliance can result in fines up to €20 million or 4% of annual turnover under GDPR Article 83.

For comprehensive GDPR SMS compliance guidance, see our GDPR SMS marketing guide.

Explicit Consent Requirements:

  • Obtain clear, specific, and documented consent before sending marketing messages.
  • Maintain detailed records of when and how you obtained consent.
  • Include clear terms and conditions during the opt-in process.
  • Provide transparent information about message frequency and content type.

Consent Withdrawal: Under GDPR Article 7(3), recipients must withdraw consent as easily as they gave it. You must:

  • Process opt-out requests within 24 hours maximum (industry best practice: 1 hour).
  • Provide multiple opt-out methods (reply STOP, web form, email, phone).
  • Not require login or account access to unsubscribe.
  • Send one final confirmation message acknowledging the opt-out.
  • Maintain opt-out records for compliance auditing (minimum 3 years).

Compliant Consent Language Examples:

  • "Reply YES to receive weekly offers from [Brand]. Msg frequency varies. Msg&data rates may apply. Reply STOP to opt out, HELP for help."
  • "Tick to receive SMS marketing from [Company]. You can unsubscribe anytime by replying STOP. See our Privacy Policy: [URL]"

Best Practices for Consent Collection:

  • Use double opt-in processes for marketing lists.
  • Keep consent records for a minimum of 5 years.
  • Audit and clean up consent databases regularly.
  • Provide clear privacy policies accessible via short links.

HELP/STOP and Other Commands

Required Keywords:

  • STOP, UNSUBSCRIBE, or OPTOUT for opt-out requests.
  • HELP for assistance information.
  • INFO for additional service details.

Sample Response Templates:

  • STOP response: "[Brand]: You're unsubscribed. You won't receive further messages. For questions, contact support@example.ie"
  • HELP response: "[Brand]: Help & Info: [URL]. Contact: support@example.ie or +353 1 234 5678. Reply STOP to opt out."
  • INFO response: "[Brand]: SMS program info: [URL]. Msg frequency: 2–4/month. Msg&data rates apply. Reply STOP to cancel."

Language Considerations:

  • Support both English and Irish (Gaeilge) keywords.
  • Include keyword instructions in initial messages.
  • Process opt-out requests in any common variation (e.g., "STOP", "Stop", "stop").

Do Not Call / Do Not Disturb Registries

Ireland maintains the National Directory Database (NDD) for opt-out preferences. You must:

  • Register for NDD access through the official NDD portal.
  • Submit number lists for screening via CSV file upload or API integration.
  • Check numbers against the NDD before sending marketing messages.
  • Download updated lists every 7 days (NDD updates weekly).
  • Maintain internal suppression lists that merge NDD data with company-specific opt-outs.
  • Process opt-outs within 24 hours.
  • Use HTTPS connections and API key authentication for API access.
  • Screen up to 10,000 numbers per batch request.

Time Zone Sensitivity

Sending Window:

  • Primary sending window: 09:00–18:00 IST (Irish Standard Time, UTC+1).
  • Restricted period: 21:00–07:00 IST.
  • Emergency messages exempt from time restrictions.
  • Document justification for out-of-hours messages.

Daylight Saving Time: Ireland observes IST (UTC+1) during summer months (last Sunday in March to last Sunday in October) and GMT (UTC+0) during winter months. Use timezone-aware libraries (e.g., moment-timezone, date-fns-tz) in your SMS scheduling systems to handle automatic DST transitions and avoid sending messages during restricted hours.

SMS Sender ID Options for Ireland (Alphanumeric, Long Codes, Short Codes)

Alphanumeric Sender ID

Operator network capability: Fully supported.

Registration requirements: No pre-registration required; dynamic usage supported.

Sender ID preservation: Yes, displayed as-is across major networks.

Character limits: 11 characters maximum, alphanumeric only (A–Z, a–z, 0–9, space). No special characters or symbols allowed.

Rejected Sender ID examples:

  • Generic terms: "SMS", "INFO", "ALERT" (often filtered as spam).
  • Special characters: "Brand!", "Co@Ltd", "Test#1" (not supported).
  • Too long: "MyCompanyName" (12 characters, exceeds 11-character limit).
  • All numbers: "0123456789" (may be mistaken for phone number and rejected).

Best practices: Use recognizable brand names, avoid generic terms, use title case (e.g., "AcmeCorp" rather than "ACMECORP").

Long Codes

Domestic vs. International:

  • Domestic: Fully supported across all carriers.
  • International: Limited support (not supported by Meteor Ireland and Three Ireland).

Sender ID preservation: Yes for domestic; may be replaced for international.

Provisioning time: Immediate for domestic; 1–2 business days for international.

Use cases: Customer service, two-way communication, verification codes.

Short Codes

Support: Not currently supported in Ireland.

Reason: ComReg has not established a short code registry for commercial SMS services. The regulatory framework for short codes is under review, with no confirmed timeline for availability.

Alternative: Use long codes or alphanumeric sender IDs, which provide similar functionality with full carrier support.

Content Restrictions and Prohibited Industries for SMS in Ireland

Prohibited Content:

Prohibited Language Patterns:

  • Deceptive urgency: "URGENT: Account suspended", "Final notice" (when not legitimate).
  • Phishing indicators: "Verify your account now", "Click here to confirm identity".
  • Loan/debt language without proper licensing: "Fast cash loans", "Debt forgiveness".
  • Excessive capitalization: "FREE MONEY NOW!!!" (flagged as spam).

Regulated Industries:

  • Financial services: Require Central Bank of Ireland approval and must include regulatory disclaimers. Contact: Financial Services Regulation, +353 1 224 6000.
  • Healthcare: Messages must comply with GDPR and Data Protection Act 2018 health data regulations. Contact: Data Protection Commission, +353 57 868 4800.
  • Gaming/gambling: Requires licensing from the Department of Justice. Include responsible gambling info and opt-out instructions. Contact: Gambling Regulation, +353 1 479 0200.

Content Filtering

Carrier Filtering Rules:

  • URLs must be from approved domains with valid HTTPS certificates.
  • Message content screened for prohibited terms using keyword blacklists.
  • Spam patterns monitored and blocked (high-frequency identical messages, burst sending).

Domain Approval Process: Major carriers maintain approved sender lists. To get domains whitelisted:

  • Submit domain registration request to carrier (Vodafone, Three, Eir).
  • Provide business registration documents and VAT number.
  • Specify message types and expected volume.
  • Allow 5–10 business days for approval.

Common Spam Patterns to Avoid:

  • Sending 100+ identical messages within 1 minute.
  • High unsubscribe rates (>5% per campaign).
  • Excessive URL shortener use (bit.ly, tinyurl).
  • Messages with no opt-out mechanism.
  • Sending to numbers without consent records.

Tips to Avoid Blocking:

  • Use registered sender IDs.
  • Avoid URL shorteners where possible; use branded short domains.
  • Maintain consistent sending patterns (avoid sudden volume spikes).
  • Include clear opt-out instructions in every marketing message.

Best Practices for Sending SMS in Ireland

Messaging Strategy

  • Keep messages under 160 characters when possible to avoid segmentation charges.
  • Include clear call-to-action (CTA) with specific next steps.
  • Personalize using recipient's first name (e.g., "Hi Sarah," rather than "Dear Customer").
  • Use trackable links with UTM parameters for engagement monitoring.
  • A/B test message variations: test CTAs, timing, personalization, and message length on 10–20% of your list before full deployment.

Sending Frequency and Timing

  • Limit to 2–4 messages per month per recipient for marketing.
  • Retail: 2–3 messages/month work best for promotions.
  • Financial services: 1–2 messages/month for account updates.
  • Healthcare: As-needed for appointments; limit marketing to 1/month.
  • Respect Irish bank holidays and weekends (avoid sending promotional SMS on Sundays).
  • Maintain consistent sending patterns (e.g., same day/time each week).
  • Allow minimum 24 hours between marketing messages.

Localization

  • Default to English for general communications.
  • Offer Irish language option where appropriate (government services, public sector communications).
  • Irish language is mandatory for public bodies under the Official Languages Act 2003. Commercial entities should offer Irish as an option for inclusivity.
  • Consider cultural context and local references (e.g., GAA events, Irish holidays).
  • Use local date/time formats (DD/MM/YYYY, 24-hour time).

Opt-Out Management

  • Process opt-outs within 24 hours maximum (1 hour recommended).
  • Maintain centralized opt-out database accessible across all sending systems.
  • Confirm opt-out with one final message: "[Brand]: You're unsubscribed. No further messages will be sent."
  • Audit opt-out compliance regularly (monthly review of opt-out processing times).

Testing and Monitoring

  • Test across all major Irish carriers (Vodafone, Three, Eir).
  • Monitor delivery rates by carrier; benchmark targets: >95% delivery rate, <2% failure rate, <5% opt-out rate.
  • Track engagement metrics (click-through rate, conversion rate, response time).
  • Run regular A/B testing of message content (test one variable at a time).
  • Document and analyze failure patterns (track error codes, carrier-specific issues).

SMS API Integrations for Ireland

Twilio

Twilio provides a robust SMS API with comprehensive support for Irish numbers and messaging requirements.

Authentication & Setup:

  • Account SID and Auth Token required.
  • Support for alphanumeric sender IDs.
  • Automatic number formatting handling.

Common Error Codes:

  • 21211: Invalid 'To' phone number (incorrect format).
  • 21408: Permission to send SMS not enabled (account configuration issue).
  • 21610: Unsubscribed recipient (number on opt-out list).
  • 21614: 'To' number is not a valid mobile number (landline or invalid).
  • 30003: Unreachable destination (carrier network issue).
  • 30005: Unknown destination (invalid number).

Troubleshooting Guide:

  • Error 21211: Verify E.164 format (+353XXXXXXXXX).
  • Error 21610: Check and update opt-out lists.
  • Error 30003: Retry after 5 minutes; if persistent, contact carrier.
  • For detailed error info, check Twilio Error Codes.
typescript
import { Twilio } from 'twilio';

// Initialize Twilio client
const client = new Twilio(process.env.TWILIO_ACCOUNT_SID, process.env.TWILIO_AUTH_TOKEN);

// Function to send SMS to Irish numbers
async function sendIrishSMS(to: string, message: string) {
  try {
    // Ensure number is in E.164 format for Ireland
    const formattedNumber = to.startsWith('+353') ? to : `+353${to.substring(1)}`;

    const response = await client.messages.create({
      body: message,
      from: 'YourBrand', // Alphanumeric sender ID
      to: formattedNumber,
      // Optional parameters for delivery tracking
      statusCallback: 'https://your-webhook.com/status'
    });

    return response.sid;
  } catch (error) {
    console.error('SMS sending failed:', error);
    throw error;
  }
}

Sinch

Sinch offers dedicated Irish SMS capabilities with strong delivery rates.

typescript
import { SinchClient } from '@sinch/sdk';

const sinch = new SinchClient({
  servicePlanId: process.env.SINCH_SERVICE_PLAN_ID,
  apiToken: process.env.SINCH_API_TOKEN,
  region: 'eu' // Ireland uses EU region
});

async function sendSinchSMS(to: string, message: string) {
  try {
    const response = await sinch.messages.send({
      from: 'CompanyName',
      to: [to],
      body: message,
      // Optional delivery report flag
      deliveryReport: 'summary'
    });

    return response.messageId;
  } catch (error) {
    console.error('Sinch SMS failed:', error);
    throw error;
  }
}

MessageBird

MessageBird provides reliable SMS delivery with Irish-specific features.

typescript
import { MessageBird } from 'messagebird';

const messagebird = MessageBird(process.env.MESSAGEBIRD_API_KEY);

async function sendMessageBirdSMS(to: string, message: string) {
  const params = {
    originator: 'YourBrand',
    recipients: [to],
    body: message,
    // Ireland-specific parameters
    datacoding: 'auto', // Automatic character encoding
    gateway: 272 // Ireland MCC
  };

  return new Promise((resolve, reject) => {
    messagebird.messages.create(params, (err, response) => {
      if (err) {
        reject(err);
      } else {
        resolve(response);
      }
    });
  });
}

Plivo

Plivo offers competitive rates for Irish SMS with good delivery reliability.

typescript
import { Client } from 'plivo';

const client = new Client(
  process.env.PLIVO_AUTH_ID,
  process.env.PLIVO_AUTH_TOKEN
);

async function sendPlivoSMS(to: string, message: string) {
  try {
    const response = await client.messages.create({
      src: 'YourBrand', // Sender ID
      dst: to, // Destination number
      text: message,
      // Ireland-specific options
      type: 'sms',
      url: 'https://your-webhook.com/status'
    });

    return response.messageUuid;
  } catch (error) {
    console.error('Plivo SMS failed:', error);
    throw error;
  }
}

API Rate Limits and Throughput

Rate Limits (default tiers):

  • Twilio: 100 messages per second.
  • Sinch: 30 messages per second.
  • MessageBird: 60 messages per second.
  • Plivo: 50 messages per second.

Requesting Rate Limit Increases:

  • Twilio: Submit request via Twilio Console > Messaging > Settings > Request Increase. Provide use case, expected volume, and business justification. Approval typically takes 2–5 business days.
  • Sinch: Contact Sinch Support with account details and throughput requirements. Enterprise plans offer up to 1,000 msg/sec.
  • MessageBird: Email support@messagebird.com with volume projections. Rate limits can increase up to 300 msg/sec for verified accounts.
  • Plivo: Submit ticket via Plivo Console > Support. Include traffic patterns and peak volume estimates.

Throughput Management Strategies:

  • Implement exponential backoff for retries (initial delay: 1s, max: 32s).
  • Use message queuing systems (Redis, RabbitMQ) to buffer high-volume sends.
  • Batch messages in groups of 50–100 to optimize API calls.
  • Monitor delivery rates and adjust sending speed dynamically.
  • Distribute load across multiple API accounts if needed.

Error Handling and Reporting

Common Error Codes (cross-platform):

  • 400 / Invalid Parameters: Check phone number format, message encoding, sender ID.
  • 401 / Authentication Failed: Verify API credentials, check token expiration.
  • 403 / Forbidden: Account restrictions, insufficient permissions, unpaid balance.
  • 429 / Rate Limit Exceeded: Implement rate limiting, add delays between requests.
  • 500 / Server Error: Retry with exponential backoff, contact provider support.

Best Practices:

  • Implement comprehensive error logging with structured JSON format.
  • Monitor delivery receipts and track status transitions (sent → delivered / failed).
  • Set up automated alerts for failure thresholds (e.g., alert if failure rate >5%).
  • Store message status updates in database with timestamps for audit trails.
  • Audit failed messages regularly (weekly review of error patterns by carrier).

Recap and Additional Resources

Key Takeaways

  1. Compliance First: Always prioritize GDPR and ePrivacy regulations; maintain consent records for minimum 5 years.
  2. Timing Matters: Respect Irish business hours (09:00–18:00 IST); handle DST transitions automatically.
  3. Clear Consent: Maintain robust opt-in/opt-out processes; process opt-outs within 24 hours.
  4. Technical Setup: Use proper E.164 number formatting (+353XXXXXXXXX) and GSM-7 character encoding.

Cost Optimization Strategies:

  • Use GSM-7 encoding to avoid UCS-2 overhead (GSM-7 = 160 chars/segment, UCS-2 = 70 chars/segment).
  • Keep messages under 160 characters to avoid concatenation charges (each segment billed separately).
  • Avoid special characters that consume 2 GSM-7 characters: {, }, [, ], ~, |, , \.
  • Use alphanumeric sender IDs (free) instead of dedicated long codes (monthly rental fees apply).
  • Schedule bulk sends during off-peak hours for potential volume discounts.
  • Negotiate volume-based pricing with carriers for >100,000 messages/month.

Next Steps

  1. Review ComReg guidelines for SMS marketing.
  2. Implement proper consent management systems with double opt-in.
  3. Set up monitoring and reporting infrastructure (delivery rates, error tracking, engagement metrics).
  4. Test delivery across all major Irish carriers (Vodafone, Three, Eir).

Additional Information

Official Resources:

Industry Guidelines:

  • GSMA Ireland Guidelines
  • Mobile Marketing Association Best Practices
  • Irish Direct Marketing Association Standards

Frequently Asked Questions

What are SMS best practices in Ireland?

Key best practices include respecting Irish business hours (9:00-18:00 IST), obtaining clear consent, using proper number formatting and character encoding, and complying with GDPR and ePrivacy regulations. It's also crucial to maintain robust opt-in/opt-out processes and test SMS delivery across major Irish carriers like Vodafone, Three, and Eir.

How to send SMS messages in Ireland?

Ireland supports two-way SMS, concatenated messages, and number portability. MMS is handled via SMS conversion with URL links. Sending to landlines is not supported. Ensure compliance with GDPR and ePrivacy regulations for marketing messages, particularly concerning consent and opt-out handling.

What is the character limit for SMS in Ireland?

Standard GSM-7 encoding allows 160 characters per SMS. However, using UCS-2 encoding for special characters limits messages to 70 characters before they are split. It's generally recommended to keep messages concise and under 160 characters for optimal readability.

Why does Ireland convert MMS to SMS?

Ireland automatically converts MMS messages to SMS with a URL link to ensure compatibility across all devices. This allows users to access rich media content even if their device doesn't directly support MMS. Ensure the URLs used are short and clear for the best user experience.

When should I send marketing SMS in Ireland?

The primary sending window for marketing SMS is between 09:00 and 18:00 IST. Avoid sending between 21:00 and 07:00 IST. Emergency messages are exempt. Always document any justified out-of-hours messages.

Can I use an alphanumeric sender ID in Ireland?

Yes, alphanumeric sender IDs are fully supported in Ireland without pre-registration. They are displayed as-is across major networks. However, avoid generic terms like "SMS" or "INFO" to maintain brand clarity and avoid potential filtering.

How to comply with SMS regulations in Ireland?

Comply with GDPR and ePrivacy (S.I. No. 336/2011). Obtain explicit consent before sending marketing messages, support STOP/HELP keywords in English and Irish, and check the National Directory Database (NDD) for opt-out preferences. Process opt-outs within 24 hours.

What is the National Directory Database (NDD) in Ireland?

The NDD is Ireland's database for opt-out preferences. Businesses must check numbers against it before sending marketing messages. It's essential to maintain internal suppression lists and update them regularly based on NDD checks and user opt-out requests.

How to manage SMS opt-outs in Ireland?

Process opt-out requests (STOP, UNSUBSCRIBE, OPTOUT) within 24 hours. Maintain a centralized opt-out database and confirm the opt-out with a final message. Regularly audit opt-out compliance to avoid legal issues.

What SMS APIs are available for Ireland?

Several SMS APIs offer services in Ireland, including Twilio, Sinch, MessageBird, and Plivo. These APIs provide varying features and rate limits, so choose one that suits your specific needs and budget.

What are SMS API rate limits for Ireland?

Rate limits vary by provider. Twilio allows 100 messages per second, Sinch 30, MessageBird 60, and Plivo 50. Implement strategies like exponential backoff, message queuing, and batching to manage throughput and avoid exceeding limits.

How to handle SMS API errors in Ireland?

Implement comprehensive error logging, monitor delivery receipts, set up alerts for failure thresholds, and store message statuses in a database. Regularly auditing failed messages can help identify and resolve issues quickly.

What are the required SMS keywords in Ireland?

Required keywords include STOP, UNSUBSCRIBE, or OPTOUT for opt-out requests, HELP for assistance, and INFO for additional service details. These should be supported in both English and Irish, with opt-out requests processed regardless of capitalization.