# Flowstates

> Managed messaging infrastructure for SMS, RCS, WhatsApp and OTP. 99.99% gateway SLA across the UK, Ireland, US, Canada, Singapore, Australia and New Zealand.

Language policy: English (en) is canonical. Spanish (/es/) and Brazilian Portuguese (/pt/) translations are listed as "also at" alternates where they exist. Other translations (fr, de, nl, pl, it, zh, yue) are available on the site but are non-indexable and intentionally not listed here — cite the English, Spanish or Portuguese URL.

## Products

- [Managed Messaging — SMS, RCS, WhatsApp & OTP](/managed-messaging): Outsourced SMS, RCS, WhatsApp and OTP operations run by Flowstates: vendor management, routing, monitoring, escalations and 99.99% gateway SLA reporting. (also at /es/managed-messaging, /pt/managed-messaging)
- [Your Gateway, Operated by Us (BYOG)](/managed-gateway-as-a-service): Bring your own gateway and vendors — Flowstates runs day-to-day operations. SLA-backed monitoring, incident response and vendor escalations.
- [Messaging Gateway as a Service — SMPP & API](/messaging-gateway-as-a-service): Gateway layer delivered as a service. Multi-vendor SMPP and API binds, routing tables and real-time failover for messaging and telecom teams. (also at /es/messaging-gateway-as-a-service, /pt/messaging-gateway-as-a-service)
- [Messaging as a Service — One API](/messaging-as-a-service): Send SMS, WhatsApp, RCS, email and voice via one API. Flowstates owns the vendor SDKs, routing, failover and observability — your team doesn't. (also at /es/messaging-as-a-service, /pt/messaging-as-a-service)
- [Messaging & OTP API for Developers — SMS API](/api): Programmable messaging API: one endpoint for SMS, RCS, WhatsApp and OTP, with API-key auth, delivery webhooks, channel cascade and full reference docs. (also at /es/api, /pt/api)
- [OTP API & SMS Verification Service](/otp-api): One OTP API for SMS, email and voice verification. Global reach, multi-vendor failover and per-route delivery data in a single REST integration. (also at /es/otp-api, /pt/otp-api)
- [CPaaS Platform for Campaigns & Journeys](/cpaas): Run SMS, voice, email and WhatsApp campaigns and customer journeys in TruContact, with personalisation, validation, reporting and cost control. (also at /es/cpaas, /pt/cpaas)
- [Bridge — AI Workspace for Customer Teams](/bridge): Bridge by Sainapsis: the AI-powered workspace that unifies WhatsApp, email, calls and CRM context. Resold and operated by Flowstates.
- [URL Short Links — Branded Domains & QR Codes](/short-links): Branded URL short links on your own domain, with automatic QR codes and real-time click tracking for SMS, RCS, WhatsApp and email. (also at /es/short-links, /pt/short-links)
- [Managed SMS, RCS & WhatsApp Gateway UK](/uk/managed-sms-rcs-whatsapp-gateway): Managed SMS, RCS and WhatsApp gateway for UK SaaS and CPaaS teams. Keep your vendors while we run routing, failover, monitoring and cost optimisation.

## Solutions

- [Aggregator-in-a-Box — Operating Model](/solutions/aggregator-in-a-box): The operating model for building or reselling an aggregator capability: multi-tenant customers, vendor connectivity, rating and billing, operated with you. (also at /es/solutions/aggregator-in-a-box, /pt/solutions/aggregator-in-a-box)
- [SMS for Adobe Marketo — Flowstates Integration](/solutions/adobe-marketo): Add SMS, RCS and WhatsApp to Adobe Marketo journeys with a no-code webhook. Multi-vendor routing, per-campaign reporting and managed deliverability. (also at /es/solutions/adobe-marketo, /pt/solutions/adobe-marketo)
- [TruContact — SMS, Voice, Email & WhatsApp](/solutions/trucontact): TruContact runs SMS, voice, email and WhatsApp campaigns from one platform: personalisation, PDF on the fly, delivery reporting and regional data centres. (also at /es/solutions/trucontact, /pt/solutions/trucontact)
- [Bridge by Sainapsis — Customer Workspace](/solutions/bridge): Bridge, supplied and operated by Flowstates: a workspace for relationship-led teams, with WhatsApp, CRM and reporting in one contract.

## Use cases

- [OTP Delivery Resilience & Multi-Vendor Failover](/use-cases/otp-resilience): Keep OTP verification available when an SMS route or provider degrades. One API, multi-vendor failover, attempt tracking and managed escalation. (also at /es/use-cases/otp-resilience, /pt/use-cases/otp-resilience)
- [OTP for Transaction & Action Verification](/use-cases/otp-verification): Verify payments, account changes, staff approvals and confirmations with single-use OTPs. Recorded consent, lower fraud and a regulator-friendly audit trail. (also at /es/use-cases/otp-verification, /pt/use-cases/otp-verification)
- [SMS Routing Across Multi-Vendor Setups](/use-cases/multi-vendor-routing): Multi-vendor SMS routing with per-route deliverability scoring across SMS, RCS and WhatsApp vendors and managed escalation. (also at /es/use-cases/multi-vendor-routing, /pt/use-cases/multi-vendor-routing)
- [Messaging Cost Optimisation](/use-cases/cost-optimisation): Reduce per-message cost with category-aware routing, BYOV and ongoing vendor commercials review. (also at /es/use-cases/cost-optimisation, /pt/use-cases/cost-optimisation)
- [SMS Gateway Operations & Vendor Escalation](/use-cases/vendor-escalation): One SMS gateway operations layer that owns escalation across your messaging vendors, carriers and routes. (also at /es/use-cases/vendor-escalation, /pt/use-cases/vendor-escalation)
- [WhatsApp Business Operations](/use-cases/whatsapp-operations): Template management, category-aware routing and BSP escalation for WhatsApp Business at scale. (also at /es/use-cases/whatsapp-operations, /pt/use-cases/whatsapp-operations)
- [Customer Outreach for BPO Services](/use-cases/bpo-customer-outreach): Messaging layer for BPOs running customer campaigns for B2C clients. SMS, WhatsApp and RCS with managed routing and per-client reporting. (also at /es/use-cases/bpo-customer-outreach, /pt/use-cases/bpo-customer-outreach)
- [Healthcare Shift Fill via SMS & WhatsApp](/use-cases/healthcare-shift-fill): Fill clinical shifts faster with two-way SMS and WhatsApp. Bank, agency and locum messaging operated under a 99.99% gateway SLA. (also at /es/use-cases/healthcare-shift-fill, /pt/use-cases/healthcare-shift-fill)

## Conversion content

- [Fix OTP Delivery Issues](/otp-delivery-issues): Diagnose and resolve one-time-password delivery problems: filtering, latency, vendor failover and observability. (also at /es/otp-delivery-issues, /pt/otp-delivery-issues)
- [CPaaS vs BYOV — Which Should You Choose?](/cpaas-vs-byov): Compare classic CPaaS with bring-your-own-vendor messaging. Cost, control, vendor risk and operational fit. (also at /es/cpaas-vs-byov, /pt/cpaas-vs-byov)

## SMS country guides

- [SMS Country Guides — Sender IDs & Compliance](/sms-guides): Country-by-country SMS guidance on sender IDs, registration, consent, opt-out and route policy — with law, carrier policy and our recommendations kept separate. (also at /es/sms-guides, /pt/sms-guides)
- [Brazil SMS Guide: Sender IDs & Compliance](/sms-guides/brazil): Practical guidance for sending OTP, transactional and marketing SMS to Brazil, including sender IDs, registration, consent, opt-out and route policy. (also at /pt/sms-guides/brazil)
- [Chile SMS Guide: Senders & Opt-Out Rules](/sms-guides/chile): Sending OTP, transactional and marketing A2P SMS to Chile: sender rewriting, domestic longcode limits, consent, opt-out, No Molestar and route policy. (also at /es/sms-guides/chile)
- [Colombia SMS Guide: Sender IDs & RNE](/sms-guides/colombia): Sending OTP, transactional and marketing A2P SMS to Colombia: senderID rewriting to shortcodes, RNE suppression, Law 2300 contact hours and route policy. (also at /es/sms-guides/colombia)
- [Costa Rica SMS Guide: Senders, Consent & Routes](/sms-guides/costa-rica): Sending OTP, transactional and marketing A2P SMS to Costa Rica: sender rewriting, Law 8642 prior-request consent, Law 8968 disclosures, SUTEL and route policy. (also at /es/sms-guides/costa-rica)
- [Mexico SMS Guide: Sender IDs & REPEP](/sms-guides/mexico): Sending OTP, transactional and marketing A2P SMS to Mexico: senderID preservation and rewriting, shortcodes, REPEP suppression, consent and route policy. (also at /es/sms-guides/mexico)
- [Jamaica SMS Guide: Senders & Consent](/sms-guides/jamaica): Sending OTP, transactional and marketing A2P SMS to Jamaica: NANP 876/658 numbering, sender handling, data-protection consent, portability and route policy.
- [Peru SMS Guide: Sender IDs & Consent](/sms-guides/peru): Sending OTP, transactional and marketing A2P SMS to Peru: +51 mobile numbering, senderID rewriting, Law 32323 consent, opt-out and route policy. (also at /es/sms-guides/peru)
- [Ecuador SMS Guide: Sender IDs & Consent](/sms-guides/ecuador): Sending OTP, transactional and marketing A2P SMS to Ecuador: +593 mobile numbering, senderID rewriting, prior authorisation, opt-out and route policy. (also at /es/sms-guides/ecuador)
- [Guatemala SMS Guide: Senders & Consent](/sms-guides/guatemala): Sending OTP, transactional and marketing A2P SMS to Guatemala: +502 mobile numbering, sender rewriting, consent, opt-out and route policy. (also at /es/sms-guides/guatemala)
- [Dominican Republic SMS Guide: Senders](/sms-guides/dominican-republic): Sending OTP, transactional and marketing A2P SMS to the Dominican Republic: +1 809/829/849 numbering, sender rewriting, consent, opt-out and route policy. (also at /es/sms-guides/dominican-republic)
- [Argentina SMS Guide: Senders & No Llame](/sms-guides/argentina): Sending OTP, transactional and marketing A2P SMS to Argentina: +54 mobile formatting, sender rewriting, No Llame, opt-out, data protection and route policy. (also at /es/sms-guides/argentina)
- [Germany SMS Guide: Senders & Consent](/sms-guides/germany): Sending OTP, transactional and marketing SMS to Germany: sender IDs, two-way routes, UWG consent, GDPR objections and route policy.
- [US SMS Guide: 10DLC, Toll-Free & TCPA](/sms-guides/united-states): Sending OTP, transactional and marketing A2P SMS in the United States: 10DLC, toll-free verification, short codes, TCPA consent, opt-out and route policy.
- [Spain SMS Guide: Alias Registration](/sms-guides/spain): Sending OTP, transactional and marketing A2P SMS to Spain: +34 numbering, CNMC alias registration, sender options, LSSI consent, opt-out and route policy. (also at /es/sms-guides/spain)
- [Paraguay SMS Guide: A2P Senders & Consent](/sms-guides/paraguay): Sending A2P SMS to Paraguay: +595 numbering, seven-digit A2P senders, sender replacement, No Molestar consent and route policy. (also at /es/sms-guides/paraguay)
- [Philippines SMS Guide: Senders & Opt-In](/sms-guides/philippines): Sending OTP, transactional and marketing A2P SMS to the Philippines: +63 numbering, registered sender IDs, mobile portability, opt-in, opt-out and route policy.
- [Sweden SMS Guide: Sender IDs & Consent](/sms-guides/sweden): Sending A2P SMS to Sweden: +46 numbering, dynamic sender IDs, long codes, portability, consent, opt-out and route policy.
- [UK SMS Guide: PECR, Sender IDs & Route Policy](/sms-guides/united-kingdom): Sending OTP, transactional and marketing SMS to the UK: +44 validation, alphanumeric sender IDs, protected-brand registration, PECR consent and opt-out.
- [Honduras SMS Guide: Sender IDs, Privacy & Route Policy](/sms-guides/honduras): Sending OTP, transactional and marketing A2P SMS to Honduras: +504 numbering, sender rewriting, privacy, opt-out and route policy. (also at /es/sms-guides/honduras)
- [El Salvador SMS Guide: Sender IDs, Consent & Route Policy](/sms-guides/el-salvador): Sending OTP, transactional and marketing A2P SMS to El Salvador: +503 mobile numbering, Claro sender registration, rewriting, consent, opt-out and route policy. (also at /es/sms-guides/el-salvador)
- [Venezuela SMS Guide: Senders & Privacy](/sms-guides/venezuela): Sending OTP, transactional and marketing A2P SMS to Venezuela: +58 mobile numbering, sender registration and rewriting, privacy, opt-out and route policy. (also at /es/sms-guides/venezuela)

## Regions

- [Regions — UK, US, Canada, Singapore, ANZ](/regions): Managed messaging operations across the UK & Ireland, United States, Canada, Singapore and Australia & New Zealand.
- [Messaging Gateway Operations — UK & Ireland](/regions/uk-ireland): Managed SMS, RCS and WhatsApp operations for the UK and Ireland. UK GDPR compliant, ICO-aligned, 99.99% gateway SLA.
- [Managed Messaging Gateway — United States](/regions/united-states): 10DLC, toll-free and short-code messaging operations across US carriers. TCPA-aware, multi-vendor failover, 99.99% SLA.
- [Managed Messaging Gateway — Canada](/regions/canada): SMS, RCS and WhatsApp operations across Canadian carriers. CASL and PIPEDA-aware messaging with managed escalation.
- [Managed Messaging Gateway — Singapore](/regions/singapore): SSIR-registered SMS, WhatsApp and RCS operations for Singapore. PDPA-compliant routing with regional failover.
- [Messaging Gateway — Australia & New Zealand](/regions/australia-new-zealand): Sender-ID-aware SMS, RCS and WhatsApp operations across AU and NZ. Privacy Act-compliant with managed vendor escalation.

## Company

- [About Flowstates — Messaging Operations Specialists](/about): We run messaging infrastructure for SaaS platforms and enterprises across the UK, Europe, North America, APAC and LATAM. (also at /es/about, /pt/about)
- [Trust, Security & Compliance](/trust): GDPR, UK GDPR, PIPEDA, PDPA and Privacy Act compliant messaging operations with a 99.99% gateway SLA. (also at /es/trust, /pt/trust)
- [Contact Sales](/contact): Talk to our messaging operations team about SMS, RCS, WhatsApp and OTP delivery. (also at /es/contact, /pt/contact)
- [Book a Messaging Review](/book): 30-minute review of your messaging routing, deliverability and vendor mix with our operations team. (also at /es/book, /pt/book)
- [Support](/support): Operational support for managed messaging customers — escalations, incidents and routing changes.
- [Resources & Use Cases](/resources): Guides, comparisons and use cases for OTP resilience, multi-vendor routing and WhatsApp operations. (also at /es/resources, /pt/resources)
- [Developer Docs — URL short links & OTP APIs](/docs): Authenticate, create branded URL short links and generate or validate OTPs. Endpoints, request bodies and example responses for the Flowstates platform. (also at /es/docs, /pt/docs)
- [Messaging infrastructure blog — field notes](/blog): Practitioner notes on customer messaging infrastructure: managed gateways, OTP resilience, multi-vendor routing, and the operational reality of A2P at scale. (also at /es/blog, /pt/blog)

## Blog posts

- [Portable A2P Messaging Architectures](/blog/portable-messaging-architectures-2026): How to design A2P messaging so it isn't welded to one vendor — application abstraction, routing policy, sender identity, and BYOV/hybrid commercial models. (also at /es/blog/portable-messaging-architectures-2026, /pt/blog/portable-messaging-architectures-2026)
- [Multi-Channel Messaging Orchestration](/blog/multi-channel-messaging-orchestration-2026): Orchestration is deciding whether, when and through which channel to contact someone. Delivery operations is making that attempt work. Separating the two (also at /es/blog/multi-channel-messaging-orchestration-2026, /pt/blog/multi-channel-messaging-orchestration-2026)
- [Messaging Feedback Loops](/blog/customer-feedback-loops-improve-messaging): How to instrument a messaging programme so delivery statuses, clicks, conversions, complaints and opt-outs become named actions with owners and thresholds (also at /es/blog/customer-feedback-loops-improve-messaging, /pt/blog/customer-feedback-loops-improve-messaging)
- [How to Compare Transactional SMS Providers](/blog/transactional-sms-providers-comparison): A defensible way to evaluate transactional SMS providers: coverage, sender registration, route transparency, DLR quality, escalation, failover and pricing
- [Messaging Frequency Capping: An Operator's Guide](/blog/messaging-frequency-capping): How frequency capping controls per-recipient volume across SMS, push, email and WhatsApp, why it differs from rate limiting, and how to enforce it across (also at /es/blog/messaging-frequency-capping, /pt/blog/messaging-frequency-capping)
- [SMS OTP Services: Security, Delivery & UX Guide](/blog/sms-otp-services-white-paper): Learn where SMS OTP fits, its security limits, why codes fail to arrive, and how routing, fallback and observability improve verification success.
- [Is WhatsApp Secure? Personal Chats, Business Messaging](/blog/is-whatsapp-secure): What WhatsApp's encryption does and does not cover, why business chats follow a different data path, and the governance a business messaging programme still (also at /es/blog/is-whatsapp-secure, /pt/blog/is-whatsapp-secure)
- [How Global SMS Delivery Works: A Technical Guide](/blog/how-global-sms-delivery-works): A layered breakdown of how international SMS actually reaches handsets — SMSCs, routes, DLRs, compliance, and the operational habits that keep delivery healthy. (also at /es/blog/how-global-sms-delivery-works, /pt/blog/how-global-sms-delivery-works)
- [Enterprise Messaging Consolidation](/blog/enterprise-message-service-managed-gateway): How to consolidate a fragmented enterprise messaging estate: inventory, a stable application contract, route supply models, traffic-class separation, canonical
- [Programmable SMS APIs: Integration Details That Matter](/blog/sms-for-developers-programmable-messaging-apis): The integration decisions that decide whether an SMS API is maintainable: request contracts, idempotency, encoding, status mapping, webhook handling, retries (also at /es/blog/sms-for-developers-programmable-messaging-apis, /pt/blog/sms-for-developers-programmable-messaging-apis)
- [7 Operational Practices for Omnichannel Retail Messaging](/blog/omnichannel-retail-strategy-best-practices): Practical messaging operations for retail: anchor every message to current order state, separate traffic classes, centralise consent and suppression, and (also at /es/blog/omnichannel-retail-strategy-best-practices, /pt/blog/omnichannel-retail-strategy-best-practices)
- [Running a U.S. SMS Programme](/blog/sms-compliance-updates-2026): An operational checklist for U.S. SMS programmes: consent evidence, registration alignment, opt-out handling, quiet hours, suppression, template governance (also at /es/blog/sms-compliance-updates-2026, /pt/blog/sms-compliance-updates-2026)
- [Mass Texting for Business](/blog/mass-texting-service-business-impact): When bulk SMS is the right channel, how to separate promotional from service traffic, and the consent, segmentation, sender and delivery controls that decide (also at /es/blog/mass-texting-service-business-impact, /pt/blog/mass-texting-service-business-impact)
- [A Practitioner's Guide to A2P SMS Delivery](/blog/a2p-sms-delivery-practitioners-guide): How A2P SMS actually behaves in production: sender registration, traffic-class isolation, DLR and error mapping, route-level monitoring, retries and outcome (also at /es/blog/a2p-sms-delivery-practitioners-guide)
- [Build, Buy or Operate a Messaging Gateway? A SaaS Decision](/blog/why-saas-platforms-outsource-messaging-gateway): The work that remains after integrating a CPaaS API — adapters, registrations, status mapping, routing, on-call, vendor management — and how to choose between (also at /es/blog/why-saas-platforms-outsource-messaging-gateway, /pt/blog/why-saas-platforms-outsource-messaging-gateway)
- [The Quiet Re-platforming of Customer Messaging](/blog/quiet-replatforming-of-customer-messaging): Application, route supply and messaging operations are separating into three decisions. What that changes for buyers who outgrew single-vendor CPaaS. (also at /es/blog/quiet-replatforming-of-customer-messaging, /pt/blog/quiet-replatforming-of-customer-messaging)
- [Transactional vs Marketing Traffic on the Same Gateway](/blog/transactional-vs-marketing-traffic): Why authentication, service, promotional, support and urgent traffic need separate senders, routes, queues and monitoring — with an isolation matrix and (also at /es/blog/transactional-vs-marketing-traffic, /pt/blog/transactional-vs-marketing-traffic)
- [Designing a Multi-channel Fallback Chain](/blog/multi-channel-fallback-chain): Fallback policy driven by objective, deadline, consent and signal reliability — with a decision table, state machine and the deduplication rules that stop (also at /es/blog/multi-channel-fallback-chain, /pt/blog/multi-channel-fallback-chain)
- [OTP Metrics That Reveal Delivery and Verification Failures](/blog/metrics-that-predict-otp-success): A measurement model for OTP: verification completion, resend behaviour, latency distributions, route breakdowns, canonical failure reasons and alerting from (also at /es/blog/metrics-that-predict-otp-success, /pt/blog/metrics-that-predict-otp-success)
- [Messaging Infrastructure Decisions That Need Operational](/blog/messaging-infrastructure-2025-26): The messaging infrastructure decisions a multi-market team has to own — contracts and adapters, route supply, registrations, status models, routing (also at /es/blog/messaging-infrastructure-2025-26, /pt/blog/messaging-infrastructure-2025-26)
- [Reducing Debtor Days with Verified Messaging Channels](/blog/reducing-debtor-days-with-verified-channels): A practical message sequence for invoice collections — verified senders, payment-state suppression, consent, and what to measure without promising faster (also at /es/blog/reducing-debtor-days-with-verified-channels, /pt/blog/reducing-debtor-days-with-verified-channels)
- [What 99.99% Gateway Availability Actually Means](/blog/what-99-99-gateway-actually-means): What a gateway availability figure covers and excludes, how the measurement boundary works, and the questions to ask before you accept a messaging SLA. (also at /es/blog/what-99-99-gateway-actually-means, /pt/blog/what-99-99-gateway-actually-means)

## Policies

- [Privacy Policy](/privacy): How Flowstates collects, uses and protects personal data. GDPR, UK GDPR, CCPA, PIPEDA, PDPA and Privacy Act-aware.
- [Website Terms of Use](/terms): The rules that apply when you access or use the Flowstates website, content, tools, documentation, demos and other online resources.
- [Cookie Policy](/cookies): How Flowstates uses cookies, pixels, tags, local storage and similar technologies. Manage your cookie preferences.
- [Modern Slavery & Anti-Bribery Policy](/ethics): Flowstates' Modern Slavery, Human Trafficking, Anti-Bribery and Anti-Corruption Policy. Standards, supplier expectations and reporting channels.

## Machine-readable

- [/llms-full.txt](/llms-full.txt): Expanded Flowstates company context for LLMs.
- [/docs/llms.txt](/docs/llms.txt): Developer/API LLM manifest.
- [/docs/llms-full.txt](/docs/llms-full.txt): Expanded developer/API LLM context.
- [/docs/openapi.yaml](/docs/openapi.yaml): OpenAPI 3.1 specification for documented public endpoints.
- [/sitemap.xml](/sitemap.xml): Sitemap of every indexable page.