Skip to content
Messaging & A2P SMS

Two-Way SMS & Conversational Messaging

Receive and reply to SMS on virtual mobile numbers, long codes and short codes in 60+ countries - routed by keyword to your webhook, agent inbox or chatbot in real time.

Two-Way SMS & Conversational Messaging - Dollu
  • 60+

    Countries with inbound numbers

  • < 2 s

    Inbound to webhook

  • 800+

    Operator connections

Overview

What is Two-Way SMS & Conversational Messaging?

Most business SMS is one-way: a notification goes out and any reply disappears into an unmonitored number. Dollu's two-way SMS service turns that outbound channel into a conversation. We provide inbound-capable numbers - virtual mobile numbers, long codes, 10DLC and toll-free numbers in the US, and dedicated or shared short codes - in more than 60 countries, and deliver every reply to your systems within seconds. Customers can confirm, reschedule, ask a question or opt out simply by replying to the message they received.

Inbound routing is where the service earns its keep. A rules engine matches each incoming message on keyword, regular expression, sender number, time of day or the outbound message it replies to, and forwards it to the right destination: an HTTPS webhook, an SMPP bind, a shared agent inbox, or your chatbot. Session tracking links a reply to the campaign or notification that prompted it, so a bare YES arrives in your system with the appointment, order or ticket reference already attached.

For teams that want to talk to customers directly, the shared inbox presents conversations as threads with assignment, tags, canned responses, internal notes and SLA timers, and it can sit alongside your existing contact-centre platform. For automation, any bot framework or NLU engine can be connected over REST; when the bot reaches its limits, a handover API passes the thread and its history to a human agent without the customer noticing. Surveys, polls and NPS or CSAT capture run on the same engine with branching logic and structured data export.

Coverage, compliance and reporting are managed for you. We advise on which number types support inbound in each market, handle registration and know-your-customer requirements where regulators require them, enforce opt-in and opt-out keywords, and retain full conversation history with configurable retention periods that respect GDPR and sector rules. Dashboards show inbound volume, response times, resolution rates and keyword performance per number and per country.

How it fits together

A2P SMS path: from your application to the handset.

A2P SMS path: from your application to the handset.Application · HTTPS or SMPP · gateway · operator SMSC · handset, with delivery receipts returning on the same pathYour applicationCRM · bank · platformHTTPS APISMPP 3.4DOLLU SMS GATEWAYSender-ID registryDLT · 10DLC · alphanumeric IDsSMS firewallcontent · velocity · AIT patternsRouting enginedirect binds first · DLR-verifiedOperator SMSC800+ direct connectionsSMPPHandsetsubscriberSS7 / MAPdelivery receipts (DLR): delivered · undelivered · expired, returned to your webhook or SMPP sessionRegistered sender IDs and templates are checked before routing; the firewall drops spoofed traffic and AIT-pattern bursts before they cost you.Direct operator binds mean fewer hops, faster OTP delivery and receipts that reflect the handset rather than an intermediate hub.
Reading the diagramYour application submits messages over the HTTPS API or an SMPP 3.4 bind. The Dollu SMS gateway checks the sender ID against the registry (DLT, 10DLC and country-specific registrations), passes traffic through the SMS firewall for content, velocity and artificially inflated traffic patterns, and routes over direct operator binds - more than 800 of them - to the subscriber's handset. Delivery receipts travel back along the same path to your webhook or SMPP session.
Why Dollu

Why choose Dollu for two-way sms.

The advantages of buying from a carrier that owns its network, interconnects and operations - rather than a reseller.

  • Turn notifications into outcomes

    Reply-to-confirm, reply-to-reschedule and reply-to-pay flows resolve the customer’s next step in the same thread, cutting no-shows and call-backs.

  • Meet customers where they already are

    SMS is on every handset with no app to install or number to save; two-way makes it a genuine support and sales channel, not just an alert feed.

  • Automate the routine, escalate the rest

    Keyword rules and chatbots handle balance checks, order status and FAQs; the handover API brings in an agent only when the conversation needs one.

  • One integration, many countries

    The same webhook payload, inbox and routing rules work for a US 10DLC number, a UK VMN and an Indian long code, so you build the flow once.

  • Live in days, not quarters

    Numbers in most markets provision instantly, the inbox needs no development, and a webhook integration is typically a day of engineering time.

Capabilities

Capabilities in detail.

Everything included with Two-Way SMS & Conversational Messaging - the platform features, options and controls you get from day one.

  1. 01

    Inbound number inventory

    Virtual mobile numbers, national long codes, US 10DLC and toll-free SMS numbers, and dedicated or shared short codes; SMS-enable existing DIDs where the operator supports it.

  2. 02

    Keyword and routing engine

    Match on keyword, prefix, regex, sender, time window or number; chain rules; auto-reply with static or templated text; route to multiple destinations in parallel.

  3. 03

    Webhook and SMPP delivery

    Signed HTTPS webhooks with retries and exponential back-off, or SMPP 3.4 deliver_sm on your existing bind; message, sender, number, timestamp and session metadata in every payload.

  4. 04

    Shared agent inbox

    Threaded conversations, assignment and queues, tags, canned responses, internal notes, SLA timers and role-based access; works in the browser with no install.

  5. 05

    Chatbot and NLU integration

    Connect any bot platform over REST; pass conversation context in and receive replies out; handover API transfers the thread and history to an agent when confidence drops.

  6. 06

    Session and conversation threading

    Replies are linked to the outbound message that triggered them, so a YES or a 2 arrives with the appointment, order or ticket reference attached.

  7. 07

    Surveys and structured capture

    Multi-question SMS surveys with branching, validation and time-outs; NPS, CSAT and yes/no polls; results exported as structured records or pushed by webhook.

  8. 08

    Compliance and consent

    Opt-in and opt-out keywords enforced per market, 10DLC campaign registration, sender registration where required, and configurable retention for conversation logs.

  9. 09

    Analytics

    Inbound volume, first-response and resolution times, keyword hit rates, bot containment and agent workload per number, team and country; export via CSV or API.

How it works

How it works.

From first conversation to live traffic - a tracked, engineer-led onboarding with a named owner at every step.

  1. Step 01

    Choose your numbers

    Select the countries and number types you need. Most VMNs and long codes are provisioned instantly; short codes and 10DLC campaigns go through registration with our team’s help.

  2. Step 02

    Configure routing

    Define keywords, auto-replies and routing rules in the portal. Point each rule at a webhook, SMPP bind, inbox queue or bot endpoint and test with real handsets.

  3. Step 03

    Connect inbox, bot or systems

    Invite agents to the inbox, connect your chatbot over REST or wire the webhook into your CRM or ticketing tool. Sample payloads and SDKs are provided.

  4. Step 04

    Go live and measure

    Start sending messages that invite replies. Track response rates, resolution times and bot containment in the dashboard and refine keywords and flows as you learn.

Compare

Direct, premium or grey.

Where an SMS route class shows up: in delivery, in the sender ID your customer sees, in the truthfulness of the delivery receipt and in the compliance risk you carry.

A2P SMS route classes compared on delivery, sender ID, delivery-receipt quality, compliance risk and price.
DimensionDirect operatorPremium aggregatedGrey routesNot offered by Dollu
DeliveryDirect SMPP bind to the mobile operator; the highest and most consistent deliveryVia a vetted hub or Tier-1 aggregator holding operator agreements; high delivery with occasional re-routingVia SIM farms or unauthorised international paths; unpredictable, filtered and blocked without notice
Sender IDRegistered alphanumeric ID, short code or long number preserved exactlyRegistered sender ID normally preserved; may be substituted on a few destinationsOverwritten with a random numeric sender; your brand is invisible
DLR qualityHandset delivery receipts from the operatorOperator or hub receipts; reliable, occasionally delayedFake or aggregator-generated receipts; no proof of delivery
Compliance riskLowest - operator-approved, with DLT, 10DLC or sender-ID registration completed up frontLow - operator agreements in place; Dollu vets every hub it usesHigh - breaches operator terms and local law; carries fines, blacklisting and lost sender IDs
Price positionHighest per message; the lowest cost per delivered, verified messageMidLowest headline price; the hidden cost is failed OTPs, blocked traffic and brand damage

Dollu does not sell grey routes. Every destination on our deck is direct operator or premium aggregated, and the route class is shown against each price so you know exactly what you are buying.

Use cases

Who uses this and why.

Typical deployments across carriers, enterprises, platforms and contact centres.

  • Appointment confirmation and rescheduling

    Clinics, salons and service providers send reminders that customers confirm or move with a single reply, with changes written back to the booking system.

  • Delivery and logistics exceptions

    Couriers offer delivery windows and safe-place options by SMS and act on replies automatically, reducing failed deliveries and support calls.

  • Customer support and sales

    Agents handle enquiries, quotes and follow-ups in threaded conversations, with bots deflecting routine questions and handing over when needed.

  • Surveys, feedback and research

    Post-interaction NPS and CSAT, multi-question research surveys and quick polls with branching logic and structured results.

  • Banking and payment confirmations

    Reply-to-approve transaction checks, card activation and balance queries on registered numbers with full audit history.

  • Contests, voting and keyword campaigns

    Text-to-win, keyword opt-ins and audience voting on short codes with real-time tallies and automatic acknowledgement messages.

Specifications

Technical & commercial specifications.

Key parameters at a glance. Ask us for the full service description and SLA document.

Inbound coverage60+ countries; outbound to 200+
Number typesVMNs, long codes, US 10DLC and toll-free, short codes
MO deliverySigned HTTPS webhook (JSON), SMPP 3.4 deliver_sm, portal inbox
LatencyTypically under 2 seconds from handset to webhook
RoutingKeyword, regex, sender, time window, session; auto-replies
InboxThreads, queues, assignment, canned replies, notes, SLA timers
Bot integrationREST in/out, context passing, handover API to agents
EncodingGSM-7 and UCS-2; concatenated messages; MMS on US/CA numbers
ComplianceOpt-in/opt-out keywords, 10DLC registration, GDPR retention
Support24×7 NOC; P1 response ≤ 15 min; named account manager
Pricing model

How Messaging is priced.

A2P, OTP and promotional SMS are priced per message by destination and route class - direct operator or premium aggregated. Wholesale SMPP decks for aggregators; RCS and WhatsApp per conversation or session.

We publish the model, not a public rate card - actual rates depend on destination, route class, volume and regulatory cost. See how every Dollu service is priced.

Per message · by country & route
  • Direct-operator and premium route tiers per destination
  • Sender ID and DLT registration assistance included
  • Volume-based discounts by monthly message count
  • Two-way inbound priced per number
  • RCS and WhatsApp Business per conversation or session
Billing
Per submitted message, itemised by destination and route; prepaid or postpaid
Commitment
None - month-to-month; volume commitments unlock better tiers
Request a rate deckActual rates within one business day.
Where it is available

220+ destinations, 800+ operator connections.

Direct operator binds and premium aggregated routes into every major mobile network. Country guides explain the sender-ID rules, KYC and route options in the markets we are asked about most.

Sender-ID registration markets

In these destinations A2P traffic is scrubbed unless the sender is pre-registered. Dollu’s compliance desk prepares and submits the registrations before your first message.

  • IndiaDLT entity, header and template registration
  • UAESender IDs registered with e& and du under TDRA rules
  • Saudi ArabiaSender IDs registered with stc, Mobily and Zain under CST rules
  • SingaporeSMS Sender ID Registry (SSIR); UEN required
  • PhilippinesSender-ID whitelisting with Globe, Smart and DITO
  • United States10DLC brand and campaign registration
FAQ

Two-Way SMS - your questions answered.

The questions customers and carriers ask us most often before they interconnect. If yours is not here, our team answers within one business day.

Still have a question?

Ask our solutions team

We offer inbound-capable numbers in more than 60 countries across Europe, North America, Asia-Pacific, the Middle East, Africa and Latin America. Number types differ by market - VMNs in most of Europe, 10DLC and toll-free in the US, long codes in India - and some markets require local registration. Our team confirms availability and requirements for your list within one business day.

Let’s talk

Start the conversation.

Tell us the countries you need and how you want replies delivered; we will provision test numbers and share webhook samples the same day.

Abstract globe with connected network lines