Flowstates messaging platform logo
    CR · +506 · MCC 712

    Costa Rica SMS guide

    What actually changes when you send OTP, transactional or marketing A2P SMS into Costa Rica — separated into Costa Rican law, supplier route policy and what we recommend operationally.

    Last reviewed: 1 August 2026 · Central America / LATAM

    On this page

    At a glance

    A quick operational read on Costa Rica. Anything marked route-dependent is set by the supplier and operator path your traffic uses, and is confirmed during route assessment.

    SMS to mobile
    Carrier or route policy
    Supported
    Sender presentation
    Carrier or route policy
    Common international A2P routes overwrite submitted alphanumeric and international numeric senders with a route-assigned local longcode or shortcode
    Alphanumeric senderID preservation
    Carrier or route policy
    Not dependable; not preserved on common current routes
    International numeric sender preservation
    Carrier or route policy
    Not preserved on common current routes
    Domestic local sender
    Carrier or route policy
    Selected provider-provisioned services only; not an arbitrary customer-supplied longcode
    Dedicated shortcode
    Carrier or route policy
    Route- and operator-dependent
    Two-way SMS
    Carrier or route policy
    Selected provider-provisioned local-number or shortcode services only; not universal
    Number portability
    Law / regulation
    Available — official SUTEL information takes precedence over conflicting provider summaries
    Marketing
    Law / regulation
    Prior request or consent, clear sender identity, immediate opt-out and suppression required
    Concatenation
    Carrier or route policy
    Not reliably supported; long messages may arrive as separate SMS and ordering cannot be assumed
    A2P security controls
    Law / regulation
    SUTEL's June 2026 anti-smishing requirements are being phased in
    Last reviewed
    Flowstates recommendation
    1 August 2026

    Route-dependent: “Route-dependent” means the behaviour is decided by the supplier and operator path your traffic takes, not by Costa Rican statute. Two providers can behave differently on the same day, and a route can change its policy. Confirm before launch.

    Law, route policy and recommendation

    Costa Rican data, consumer and telecom rules, supplier route behaviour and our own operating standard are three different things. Every statement on this page is labelled so the right team can act on it.

    • Law / regulation

      Law and regulation

      Binding obligations from Costa Rican legislation, executive decrees and SUTEL, including informed-consent disclosures, prior-request rules for direct-sale communications and the phased anti-smishing requirements. These apply whichever supplier you use.

    • Carrier or route policy

      Carrier or route policy

      Rules applied by operators, aggregators or your provider on the specific A2P path your traffic takes — sender rewriting, two-way availability, concatenation behaviour and content filtering. Route-dependent and subject to change.

    • Flowstates recommendation

      Flowstates operational recommendation

      What we ask customers to do because it protects deliverability and keeps you comfortably inside both the law and route policy. Deliberately stricter than the legal minimum.

    Numbering and networks

    The basics your validation layer and templates need to get right before the first send.

    • Law / regulationNumber format

      Costa Rican national telephone numbers use eight digits under the current SUTEL numbering plan, and are normally written in E.164 as +506 XXXX XXXX.

    • Law / regulationDialling code

      Country dialling code +506. Mobile country code 712.

    • Law / regulationNumber portability

      Mobile number portability is available in Costa Rica and is widely used, according to current official SUTEL material. Never infer the current operator from the original prefix.

    • Flowstates recommendationConflicting provider tables

      Some route-provider summary tables still describe Costa Rican portability as unavailable. Where a provider table conflicts with current official regulator information, we treat SUTEL as the source of truth and re-confirm the route behaviour separately.

    • Carrier or route policyNetworks

      The main national mobile operators to plan for are Claro, Kölbi and Liberty. Supplier and operator mapping still has to be confirmed against live route data rather than inferred from brand or prefix.

    • Flowstates recommendationValidation

      Validate to E.164 and run mobile validation or lookup before sending. Standard A2P SMS routes should target mobile services, so fixed-line destinations should be validated out rather than submitted and failed.

    • Flowstates recommendationPortability handling

      Because portability is widely used, resolve the current operator at send time instead of caching an operator against a contact record.

    E.164 example

    +506 XXXX XXXX

    Country code 506, then the eight national digits of a Costa Rican number.

    SenderID options

    In Costa Rica what the recipient sees is decided by the route, not by the value in your API call. On common international A2P paths the submitted sender is overwritten with a route-assigned local longcode or shortcode, so design the message body around that.

    Carrier or route policy

    Best for, what the recipient sees and replies describe carrier or route behaviour on current A2P paths in Costa Rica — not Costa Rican statute. They vary by supplier and operator, and are confirmed before launch rather than guaranteed universally.

    Rewritten international A2P sender

    Best for
    One-way OTP and transactional traffic on a validated route
    What the recipient sees
    A route-assigned local longcode or shortcode, not the submitted brand or international number
    Replies
    Not assumed

    Provider-provisioned local two-way number

    Best for
    Approved service, support or conversational use cases that genuinely need inbound replies
    What the recipient sees
    The local numeric sender assigned by the selected service
    Replies
    Yes, only when explicitly configured

    Dedicated shortcode

    Best for
    Consistent numeric identity, scale and possible two-way programmes where available
    What the recipient sees
    The route-supported shortcode where preserved
    Replies
    Potentially available, route-dependent

    Alphanumeric senderID

    Best for
    Not a dependable branding option on common Costa Rica routes
    What the recipient sees
    Generally a rewritten local numeric sender or shortcode
    Replies
    No

    Put the brand and purpose in the message body, because the sender is commonly rewritten. Sender presentation is route- and operator-dependent.

    What changes by traffic type

    Costa Rica is not one rulebook. The same destination behaves differently depending on the category you send and the route it takes.

    OTP / authentication

    Suitable on validated high-quality routes.

    • Flowstates recommendation

      Keep the copy purely transactional and short — no marketing, no offers, no upsell in a verification message.

    • Flowstates recommendation

      Identify the brand in the message body, because the sender is commonly rewritten to a route-assigned local number.

    • Flowstates recommendation

      Fit the OTP into a single segment; concatenation is not reliable on common Costa Rica routes.

    • Flowstates recommendation

      Use a branded domain for any link and avoid ambiguous link text.

    • Flowstates recommendation

      Monitor latency, delivery, verification conversion and per-operator performance rather than submitted-versus-delivered counts alone.

    • Flowstates recommendation

      Configure carrier-grade failover so a degraded route does not become a failed login queue.

    • Law / regulation

      Classify the traffic accurately as A2P. SUTEL's anti-smishing requirements oblige operators to distinguish P2P from A2P, so mislabelled traffic is more likely to be filtered as implementation progresses.

    Transactional / service

    Suitable for alerts, confirmations and account or service updates.

    • Flowstates recommendation

      Identify the brand and state the purpose of the message clearly.

    • Flowstates recommendation

      Use a branded domain for links rather than a public or shared shortener.

    • Flowstates recommendation

      Keep promotional content out of transactional templates — mixed content invites re-classification.

    • Flowstates recommendation

      Prefer a single segment. If a route splits a long message, do not assume the parts arrive in order.

    • Carrier or route policy

      Enable replies only where a two-way service has been explicitly configured. Inbound handling is not a default on Costa Rican A2P paths.

    Marketing / promotional

    Prior request or consent, clear identity and an immediate, free opt-out before launch.

    • Law / regulation

      Direct-sale electronic messaging requires prior consent under Costa Rican telecom and consumer rules, and the recipient must be able to stop it clearly and free of charge.

    • Law / regulation

      Where personal data is used, the purpose must also be covered by the informed-consent and data-processing framework of Law 8968.

    • Flowstates recommendation

      Clearly identify the sender and the purpose of the message.

    • Flowstates recommendation

      Provide a clear, free and straightforward opt-out, and honour it immediately.

    • Flowstates recommendation

      Support natural Spanish requests such as BAJA, SALIR or CANCELAR. We do not claim that any particular keyword is mandated by Costa Rican statute.

    • Flowstates recommendation

      Maintain a central internal suppression and do-not-disturb list across every sending system.

    • Flowstates recommendation

      Do not use purchased lists.

    • Flowstates recommendation

      Schedule in recipient daytime local time and avoid late-night non-urgent traffic. This is our operating standard, not a statutory sending-hours window.

    • Carrier or route policy

      Validate the selected promotional route before launch; sender behaviour and content filtering differ between suppliers on the same destination.

    Operational compliance checklist

    What we expect to see in place before a Costa Rica route goes live.

    • Law / regulation

      Record the data source, the legal basis and the permitted purpose for every recipient record.

    • Law / regulation

      For promotions, retain demonstrable prior request or consent: recipient, timestamp, source, wording or version and purpose.

    • Law / regulation

      Where you collect personal data, give the data subject the disclosures required by Law 8968, Article 5.

    • Flowstates recommendation

      Identify the sending brand and the purpose of the message in the body, because the sender is commonly rewritten.

    • Law / regulation

      Provide an easy, free opt-out and suppress immediately once a recipient asks to stop.

    • Flowstates recommendation

      Support BAJA, SALIR and CANCELAR without claiming that one statutory keyword exists.

    • Flowstates recommendation

      Maintain a central internal suppression and do-not-disturb list; do not rely on a presumed network-level block.

    • Flowstates recommendation

      Do not use purchased lists.

    • Law / regulation

      Classify OTP, transactional and marketing templates before launch — accurate A2P classification matters under the anti-smishing requirements.

    • Flowstates recommendation

      Keep promotional content out of OTP and transactional templates.

    • Flowstates recommendation

      Schedule by Costa Rica recipient daytime local time, without inventing statutory hours.

    • Flowstates recommendation

      Use a branded short domain rather than a public or shared URL shortener.

    • Carrier or route policy

      Validate mobile service and the selected route before launch, and exclude fixed-line destinations.

    • Flowstates recommendation

      Prefer one-segment templates, because concatenation is unreliable on common Costa Rica routes.

    • Carrier or route policy

      Confirm category acceptance for the selected route before launch. Restrictions are route-specific rather than a published national list.

    • Flowstates recommendation

      Keep template, consent, campaign, suppression and route-approval records.

    Encoding and delivery

    Spanish copy makes encoding a real cost and delivery question in Costa Rica, and concatenation cannot be assumed. Test it rather than trusting a generic table.

    GSM-7, single segment
    160 characters
    GSM-7, concatenated
    153 characters per segment
    Unicode / UCS-2, single segment
    70 characters
    Unicode / UCS-2, concatenated
    67 characters per segment
    • Flowstates recommendation

      Spanish accents, smart punctuation and formatting copied from a document can change the encoding, which shortens the segment and raises cost. Check the encoding your template actually produces.

    • Carrier or route policy

      Common Costa Rica routes do not reliably support concatenated SMS. A long message may be split into independent messages, and delivery order cannot be guaranteed.

    • Flowstates recommendation

      Keep OTP and transactional templates to a single segment wherever practical.

    • Flowstates recommendation

      Run an end-to-end test with the actual Spanish copy across the Claro, Kölbi and Liberty paths selected for launch.

    • Flowstates recommendation

      Normalise to +506 XXXX XXXX and validate mobile numbers with lookup before sending — portability is available, so the original prefix tells you nothing reliable about the current operator.

    A country guide is only useful when the route follows it

    Knowing Costa Rica's rules is the easy half. Keeping every send inside them, on supplier routes that change their policy, is the operational half — that is the part we run.

    • Per-country and per-category routing

      OTP, transactional and marketing traffic take different Costa Rica routes, with the right policy applied to each category.

    • SenderID management

      We manage sender presentation where a route supports it, and design templates for the common Costa Rican case where the sender is rewritten.

    • Carrier-grade failover

      When a Costa Rica route degrades, traffic moves before your verification funnel does.

    • Per-route visibility

      Delivery, latency and OTP conversion measured per route and per operator, so a route policy change shows up as data rather than complaints.

    • 24/7 vendor escalation

      We chase the supplier and the carrier. You get the update, not the ticket queue.

    • BYOV / BYOG

      Keep your existing supplier and contracts and let us operate the routing, or use ours.

    • Branded short links

      Links on your own domain instead of a shared shortener, which route filters treat very differently.

    What we need to validate your Costa Rica route

    Send us these and we will come back with the route options, the sender behaviour you should expect and the policy that applies to your category.

    • Company or legal entity and website
    • Traffic category and use case
    • Spanish and English sample templates
    • Expected monthly volume and peak sending rate
    • Consent or request journey and evidence for promotional traffic
    • Sender preference
    • Link domains you intend to use
    • Whether you need replies or two-way messaging
    • Target launch date

    Frequently asked questions about SMS in Costa Rica

    Can I send SMS to mobile numbers in Costa Rica?

    A quick operational read on Costa Rica. Anything marked route-dependent is set by the supplier and operator path your traffic uses, and is confirmed during route assessment. SMS to mobile: Supported. Sender presentation: Common international A2P routes overwrite submitted alphanumeric and international numeric senders with a route-assigned local longcode or shortcode. Alphanumeric senderID preservation: Not dependable; not preserved on common current routes. International numeric sender preservation: Not preserved on common current routes.

    Which sender ID options work for SMS in Costa Rica?

    In Costa Rica what the recipient sees is decided by the route, not by the value in your API call. Rewritten international A2P sender — Best for: One-way OTP and transactional traffic on a validated route. Provider-provisioned local two-way number — Best for: Approved service, support or conversational use cases that genuinely need inbound replies. Dedicated shortcode — Best for: Consistent numeric identity, scale and possible two-way programmes where available. Alphanumeric senderID — Best for: Not a dependable branding option on common Costa Rica routes.

    What are the consent and opt-out requirements for SMS in Costa Rica?

    Costa Rica is often summarised as “you need opt-in”. June 2026 anti-smishing change: on 24 June 2026 SUTEL announced new anti-smishing requirements for operators providing SMS. Operators must build the capability to distinguish P2P from A2P traffic, filter malicious messages and provide end-to-end traceability. Implementation is phased and culminates over an 18-month period. That is primarily an operator-level regulatory change, not a basis for inventing a public customer-registration requirement. Operationally it makes accurate traffic classification, a recognisable brand and purpose, branded link domains, consistent templates and end-to-end route testing more important, and link or content filtering may tighten as implementation progresses. Law 8968, Article 5: when personal data is collected, the holder must be informed expressly, precisely and unequivocally about the existence of the database, the purposes, the intended recipients, the mandatory or optional nature of the answers, the treatment of the data, the consequences of providing it, the rights available and the identity and address of the controller. Express consent is required unless a statutory exception applies.

    How many characters fit in an SMS to Costa Rica?

    Spanish copy makes encoding a real cost and delivery question in Costa Rica, and concatenation cannot be assumed. GSM-7, single segment: 160 characters. GSM-7, concatenated: 153 characters per segment. Unicode / UCS-2, single segment: 70 characters. Unicode / UCS-2, concatenated: 67 characters per segment.

    Sources and change control

    Regulator, statute and provider references behind this guide. Provider documentation reflects one supplier's current route policy, not Costa Rican law — and where it conflicts with official SUTEL material, the regulator takes precedence.

    Change log

    • 1 August 2026 — Initial draft; separated Costa Rican data, consumer and anti-smishing rules from live sender and route policy, and corrected portability using official SUTEL information.

    Last reviewed 1 August 2026

    Disclaimer

    This is operational guidance, not legal advice. Operator, route, sender type, traffic category and customer configuration can change the applicable path. Flowstates confirms it during onboarding.