Country Summary

Country nameArgentina
ISO codeAR
RegionSouth America
Dialing code+54


Use Cases

Short codes are ideal for high-throughput programmatic messaging.

Short codes are approved for specific use cases, so if you are experiencing carrier filtering on long codes you may be a good candidate for short codes.

Some of the most common use-cases for short codes in Argentina are: 

  • Two-factor authentication (2FA) or one-time passwords (OTP)
  • Promotional or marketing alerts
  • Account alert notifications
  • Reminders (appointments, upcoming payments, etc.)

Short codes can only message users on carriers within the countries in which they are provisioned.

Although Twilio can provision short codes in multiple countries, if your customers are not located in Argentina, you should not obtain an Argentina Short Code.

Short codes require express consent from end users before any SMS can be sent; if you cannot obtain consent you should not use a short code.

Twilio and/or the carriers will not support certain types of campaigns, including: 

  • Those in which express end-user consent cannot be obtained. This includes friend-to-friend invite-based campaigns, as well as opt-ins obtained through lead generation.
  • Campaigns containing sexual/adult content (which are prohibited by Twilio’s AUP).

Please note that if you order FTEU (Free to End User) Short Code the owner pays extra to send messages for which end users do not pay.

Minimum term commit for Argentina Short Code is 6 months.

The notice period before returning the Short Code is 1 month (provided minimum term commit has been fulfilled).

Minimum monthly messaging volume is 75000 messages. Failure to meet minimum volume per month may incur additional fees.

If Short Code does not have any traffic in Argentina for 30 days or more, there is a high chance of it to be withdrawn due to absence of usage.

All operators in Argentina observe a freeze during the month of December till mid January, which can affect provisioning.

Refer to this article for detailed explanation on Argentina Short Code Best Practices.

Other Options

To apply for Argentinian Short Code the following details are needed:

  • Short Code Type
    • Random or several preferred options to choose from (in case of preferred please provider 5 options)
    • Please outline here if you need FTEU (Free To End User) Short Code or not. Please note in case of FTEU Short Code the owner pays extra to send messages for which end users do not pay.
  • Brand/Company
  • Type of Traffic (Marketing or Notifications) and Use case
  • Monthly Volume (Amount of messages sent monthly)
  • Examples of SMS Text (Please include URL (if applicable) as it must be pre-approved by the vendor)
  • Preferred Billing Method:
    • Quarterly or Yearly (prices can be reviewed from here)

6-15 weeks, once you submit all required information and documentation.

Please expect delays on any applications submitted from December through mid January, as the wireless carriers have an annual provisioning freeze during this time.

Regulatory Bodies

Ente Nacional de Comunicaciones (ENACOM)


Click to see SMS pricing, including for short codes.

Next Steps

To apply for Argentina Short Code please follow these steps:

  • Check all the requirements above and collect all the needed details.
  • Send the application including all the requirements to

For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.