Argentina SMS Guide 2025: Send SMS with Compliance & APIs

What You Need to Know About Argentina's SMS Market

When you send SMS to Argentina, you're reaching one of South America's most developed mobile markets. Whether you need A2P (application-to-person) messaging for marketing campaigns, transactional SMS for authentication, or bulk SMS services for customer engagement, understanding Argentina's regulatory landscape is essential. This guide covers everything from technical requirements and phone number formatting (+54 country code) to compliance with Law 25.326 (Personal Data Protection) and Law 26.951 (Do Not Call Registry), plus API integration examples for major providers including Twilio, Sinch, MessageBird, and Plivo.

Market Conditions: Argentina has a mature mobile market with high SMS adoption rates. The country's major mobile operators include Claro, Personal, and Movistar. WhatsApp is extremely popular for messaging, though SMS remains crucial for business communications and authentication. Android devices dominate the market with approximately 87.94% market share, while iOS devices account for 11.91% (as of Q4 2024, per StatCounter). Claro leads with approximately 40% of wireless subscriptions (Q4 2023), while Personal and Movistar maintain competitive positions.

SMS Features and Technical Capabilities in Argentina

Argentina supports a comprehensive range of SMS features including two-way messaging, concatenation, and number portability, though MMS is handled through SMS conversion.

Two-way SMS Support

Two-way SMS is fully supported in Argentina with no major restrictions. This enables interactive messaging campaigns and customer engagement through SMS conversations.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenation is fully supported across all major carriers.

Message length rules: Standard 160 characters for GSM-7 encoding, 70 characters for Unicode (UCS-2) before splitting occurs.

Encoding considerations: Both GSM-7 and UCS-2 (Unicode) are supported, with GSM-7 recommended for optimal message length and cost efficiency.

Concatenated message limits: When messages exceed single-segment limits, they split into 153-character segments for GSM-7 or 67-character segments for UCS-2. A 6-byte User Data Header in each segment enables reassembly on the recipient's device.

MMS Support

MMS messages are automatically converted to SMS with an embedded URL link to the media content. This ensures compatibility across all devices while maintaining the ability to share rich media content.

Recipient Phone Number Compatibility

Number Portability

Number portability is available in Argentina, allowing users to keep their phone numbers when switching carriers. This feature does not significantly impact message delivery or routing as the system automatically handles carrier identification.

Sending SMS to Landlines

Sending SMS to landline numbers is not supported in Argentina. Attempts to send messages to landline numbers will result in a failed delivery and an error response (400 error code 21614) from the API, with no charges applied to the sender's account.

What Are Argentina's SMS Compliance Requirements? (Law 25.326 & Law 26.951)

Argentina's SMS communications are regulated under Law 25.326 (Personal Data Protection Law, enacted 2000) and Law 26.951 (National Do Not Call Registry Law, enacted July 30, 2014). ENACOM (Ente Nacional de Comunicaciones) oversees telecommunications infrastructure, while AAIP (Agencia de Acceso a la Información Pública) enforces data privacy regulations. As of June 1, 2024, AAIP Resolution 126/2024 unified the sanctions regime for both laws, establishing three tiers of violations: minor infractions (fines up to ARS 40,000,000, approximately USD 44,490 at June 2024 official exchange rates), serious infractions (up to ARS 45,000,000, approximately USD 50,000), and very serious infractions (up to ARS 50,000,000, approximately USD 55,600). Fines may be reduced by half for voluntary payment. You must obtain explicit consent before sending marketing messages and comply with Do Not Call registry requirements.

Consent and Opt-In

Explicit Consent Requirements:

• Written or digital confirmation from recipients before sending marketing messages
• Clear disclosure of message purpose, frequency, and company information
• Documented proof of consent maintained for compliance purposes
• Separate consent required for different types of communications (marketing, transactional, etc.)
• Proof retention: Operators accept any form of opt-in (web, call center, mobile-originated messages, paper form), but you must retain proof of opt-in to present during operator audits or in response to user complaints

HELP/STOP and Other Commands

• Required Keywords:
  • STOP, BAJA, NO ("stop" in Spanish)
  • AYUDA, HELP (must support both Spanish and English)
• Messages must include opt-out instructions in Spanish
• Opt-out confirmation messages should be sent in the recipient's preferred language

Do Not Call / Do Not Disturb Registries

Argentina maintains the "Registro Nacional No Llame" (National Do Not Call Registry) managed by AAIP under Law 26.951. Key requirements:

• Check numbers against the registry before sending marketing messages
• Registered numbers have a 30-day waiting period before they can file denunciations
• Update contact lists monthly to remove registered numbers
• Maintain internal suppression lists for opt-outs
• Honor opt-out requests within 24 hours
• Registry of Offenders: AAIP Resolution 126/2024 established a Registry of Offenders tracking companies that violate Laws 25.326 and 26.951

Time Zone Sensitivity

• Recommended Sending Hours: 9:00 AM to 10:00 PM local time (Argentina Time, ART) for promotional and marketing messages
• Reasonable calling hours: AAIP Resolution 126/2024 establishes specific hours considered reasonable for making calls on weekdays and Saturdays (9:00 AM to 10:00 PM)
• Avoid sending during national holidays
• Emergency or critical notifications exempt from time restrictions
• Consider different time zones within Argentina for nationwide campaigns

What Phone Number Formats Work for Argentina SMS? (E.164 & Sender IDs)

E.164 Number Format for SMS

Critical formatting difference: Argentina mobile numbers require different formatting for SMS versus voice calls:

• SMS format: +54 [area code] [subscriber number] (omit the '9' prefix)
• Voice call format: +54 9 [area code] [subscriber number] (includes '9' prefix)

Example: For Buenos Aires mobile (11) 15 1234-5678:

• SMS: +541112345678
• Voice: +5491112345678

Structure: Argentina uses a 10-digit numbering plan (excluding country code):

• Area codes: 2-4 digits (Buenos Aires = 11, larger cities = 2-3 digits, rural areas = 4 digits)
• Subscriber numbers: 6-8 digits (total always equals 10 digits)
• The "15" prefix visible in domestic mobile numbers should be removed for international formatting

Important: Always store numbers in E.164 format without spaces, dashes, or parentheses for consistency and portability. The total length is limited to 15 digits maximum per ITU-T E.164 standard.

Alphanumeric Sender ID

Operator network capability: Not supported by local networks

Registration requirements: N/A

Sender ID preservation: No - messages will be delivered with random shortcode

Long Codes

Domestic vs. International:

• Domestic: Supported but not available through most providers
• International: Fully supported

Sender ID preservation: No - original sender ID is not preserved

Provisioning time: 1-2 business days for international numbers

Use cases:

• Two-way communication
• Customer support
• Transactional messages

Short Codes

Support: Yes, fully supported

Provisioning time: 6-15 weeks

Use cases:

• High-volume marketing campaigns
• Two-factor authentication
• Emergency alerts
• Customer engagement programs

Restricted SMS Content, Industries, and Use Cases

Understanding Argentina's content restrictions and carrier filtering is crucial for maintaining high delivery rates and avoiding regulatory penalties.

Restricted Industries:

• Gambling and betting services
• Adult content
• Cryptocurrency promotions
• Unauthorized financial services

Regulated Industries:

• Banking and financial services require additional compliance
• Healthcare messages must comply with patient privacy laws (similar to HIPAA standards)
• Political messaging has specific disclosure requirements
• Insurance and pharmaceutical promotions need pre-approval

Additional Content Restrictions:

• No political, religious, or gambling content in promotional messages
• Operator policies prohibit traffic promoting competing networks (messages promoting networks other than the terminating network will not be delivered)

Content Filtering and Spam Prevention

Known Carrier Filters:

• URLs from unknown domains
• Excessive punctuation
• All-caps messages
• Multiple consecutive spaces

Best Practices to Avoid Filtering:

• Use registered URL shorteners
• Maintain consistent sender IDs
• Avoid spam trigger words
• Keep message formatting simple

Best Practices for Sending SMS in Argentina

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear call-to-actions
• Use personalization tokens (customer name, account info)
• Maintain consistent brand voice

Sending Frequency and Timing

• Limit to 4 marketing messages per month per recipient
• Space messages at least 24 hours apart
• Avoid sending during siesta hours (1:00 PM - 4:00 PM)
• Consider cultural events and holidays

Localization

• Primary language should be Spanish
• Use local date format (DD/MM/YYYY)
• Consider regional dialects and expressions (Rioplatense Spanish in Buenos Aires)
• Provide customer support in Spanish
• Adapt messaging for cultural context (see international SMS best practices)

Opt-Out Management

• Process opt-outs within 24 hours
• Maintain centralized opt-out database
• Send confirmation of opt-out
• Regular audit of opt-out lists

Testing and Monitoring

• Test across major carriers (Claro, Personal, Movistar)
• Monitor delivery rates by carrier
• Track engagement metrics
• Regular A/B testing of message content

How to Send SMS to Argentina Using APIs (Twilio, Sinch, MessageBird, Plivo)

Choosing the right SMS API provider for Argentina depends on your specific needs for pricing, throughput, features, and reliability. Here's a quick comparison:

All providers support Argentina's E.164 format (+54), two-way messaging, and delivery tracking.

Twilio SMS API for Argentina

Twilio provides a robust REST API for sending SMS messages to Argentina. Authentication uses account SID and auth token.

import twilio from 'twilio';

// Initialize client with your credentials
const client = twilio(
  process.env.TWILIO_ACCOUNT_SID,
  process.env.TWILIO_AUTH_TOKEN
);

// Function to send SMS to Argentina
async function sendSMSToArgentina(
  to: string,
  message: string
): Promise<void&gt; {
  try {
    // Ensure number is in E.164 format for Argentina (+54)
    const formattedNumber = to.startsWith('+54') ? to : `+54${to}`;
    
    const response = await client.messages.create({
      body: message,
      to: formattedNumber,
      from: process.env.TWILIO_PHONE_NUMBER,
      // Optional: statusCallback URL for delivery updates
      statusCallback: 'https://your-callback-url.com/status'
    });
    
    console.log(`Message sent successfully! SID: ${response.sid}`);
  } catch (error) {
    console.error('Error sending message:', error);
  }
}

Sinch SMS API for Argentina

Sinch offers a straightforward REST API with JWT authentication for sending SMS messages.

import axios from 'axios';

class SinchSMSService {
  private readonly apiToken: string;
  private readonly serviceId: string;
  private readonly baseUrl: string = 'https://sms.api.sinch.com/xms/v1';

  constructor(apiToken: string, serviceId: string) {
    this.apiToken = apiToken;
    this.serviceId = serviceId;
  }

  async sendSMS(to: string, message: string): Promise<void&gt; {
    try {
      const response = await axios.post(
        `${this.baseUrl}/${this.serviceId}/batches`,
        {
          from: 'YourSenderID',
          to: [to],
          body: message
        },
        {
          headers: {
            'Authorization': `Bearer ${this.apiToken}`,
            'Content-Type': 'application/json'
          }
        }
      );
      
      console.log('Message sent:', response.data.id);
    } catch (error) {
      console.error('Sinch SMS error:', error);
    }
  }
}

MessageBird (Bird) SMS API for Argentina

MessageBird provides a feature-rich API with support for multiple message types.

import messagebird from 'messagebird';

class MessageBirdService {
  private client: any;

  constructor(apiKey: string) {
    this.client = messagebird(apiKey);
  }

  sendSMS(to: string, message: string): Promise<void&gt; {
    return new Promise((resolve, reject) =&gt; {
      this.client.messages.create({
        originator: 'YourCompany',
        recipients: [to],
        body: message,
        // Optional parameters for Argentina
        type: 'sms',
        datacoding: 'plain', // or 'unicode' for special characters
      }, (err: any, response: any) =&gt; {
        if (err) {
          reject(err);
        } else {
          resolve(response);
        }
      });
    });
  }
}

Plivo SMS API for Argentina

Plivo offers a powerful API with support for high-volume messaging.

import plivo from 'plivo';

class PlivoSMSService {
  private client: any;

  constructor(authId: string, authToken: string) {
    this.client = new plivo.Client(authId, authToken);
  }

  async sendSMS(to: string, message: string): Promise<void&gt; {
    try {
      const response = await this.client.messages.create({
        src: 'YourSourceNumber', // Your Plivo number
        dst: to,
        text: message,
        // Optional parameters
        url: 'https://your-callback-url.com/status',
        method: 'POST'
      });
      
      console.log('Message sent:', response.messageUuid);
    } catch (error) {
      console.error('Plivo error:', error);
    }
  }
}

API Rate Limits and Throughput

• Rate Limits (per LVN - Long Virtual Number):
  • Maximum 500 messages per day per long code
  • 40 messages per 10 minutes per number
  • 5 messages per minute from same number

Throughput Management Strategies:

• Implement message queuing using Redis or RabbitMQ
• Use multiple sender IDs for load balancing
• Batch messages for optimal delivery
• Implement exponential backoff for retries

Error Handling and Reporting

• Implement comprehensive logging with Winston or Bunyan
• Monitor delivery receipts (DLRs)
• Track common error codes:
  • 21614: Invalid number format
  • 21408: Rate limit exceeded
  • 21611: Message blocked

Frequently Asked Questions About Sending SMS to Argentina

How much does it cost to send SMS to Argentina?

SMS costs to Argentina vary by provider but typically range from $0.03 to $0.10 per message for standard SMS. Short code messaging may have different pricing structures. Contact your SMS provider (Twilio, Sinch, MessageBird, or Plivo) for current international SMS rates to Argentina.

Do I need to register to send SMS to Argentina?

Yes, for high-volume or commercial SMS campaigns, you should register with Argentina's telecommunications carriers. Short codes require 6-15 weeks for provisioning and operator approval. Transactional messages sent via international long codes may not require pre-registration but must still comply with Law 25.326 and Law 26.951.

What is the best time to send SMS in Argentina?

The optimal sending window for promotional SMS in Argentina is 9:00 AM to 10:00 PM local time (Argentina Time, ART), Monday through Sunday. Avoid sending during siesta hours (1:00 PM - 4:00 PM) and national holidays. Transactional and emergency messages are exempt from these time restrictions.

Can I use alphanumeric sender IDs in Argentina?

No, alphanumeric sender IDs are not supported in Argentina. Messages sent with alphanumeric IDs will be automatically replaced with a random short code or long code number. For brand recognition, consider using short codes instead.

How do I format phone numbers for Argentina SMS?

Argentina phone numbers use E.164 format: +54 followed by 10 digits (area code + subscriber number). For SMS, omit the '9' prefix that's used in voice calls. Example: +541112345678 for a Buenos Aires mobile number.

What is Argentina's Do Not Call Registry?

Argentina's "Registro Nacional No Llame" is managed by AAIP under Law 26.951. Businesses must check this registry before sending marketing SMS. Registered numbers have a 30-day waiting period before filing complaints. Update your contact lists monthly and honor opt-out requests within 24 hours.

Which SMS API providers work best for Argentina?

Major SMS API providers supporting Argentina include Twilio, Sinch, MessageBird, and Plivo. All support E.164 formatting, delivery receipts, and two-way messaging. Choose based on your needs for pricing, throughput (500 messages/day per long code), and features like status callbacks and error handling.

What content is restricted in Argentina SMS?

Restricted content includes gambling, adult content, cryptocurrency promotions, and unauthorized financial services. Healthcare and banking SMS require additional compliance with patient privacy and financial regulations. Political messaging has specific disclosure requirements under Argentine law.

Recap and Additional Resources

Key Takeaways:

1. Always format numbers in E.164 format (+54 followed by 10 digits)
2. For SMS: use +54 + area code + subscriber number (omit the '9' prefix used in voice calls)
3. Implement proper opt-out handling
4. Respect local time zones and sending hours (9:00 AM–10:00 PM for marketing)
5. Maintain proper consent documentation

Next Steps:

1. Review ENACOM regulations (https://www.enacom.gob.ar)
2. Implement proper error handling and monitoring
3. Set up delivery receipt handling
4. Test thoroughly across all major carriers

Additional Resources:

• ENACOM (National Communications Entity): https://www.enacom.gob.ar
• AAIP (Agency for Access to Public Information): https://www.argentina.gob.ar/aaip
• Law 25.326 (Personal Data Protection): https://www.argentina.gob.ar/aaip
• National Do Not Call Registry: https://nollame.aaip.gob.ar
• Mobile Operators Association: https://www.gsma.com/latinamerica

Technical Documentation:

• Twilio Argentina Guidelines: https://www.twilio.com/docs/sms/guidelines/ar
• MessageBird API Docs: https://developers.messagebird.com
• Sinch API Reference: https://developers.sinch.com
• Plivo API Documentation: https://www.plivo.com/docs