Azmarq · Messaging (SMS)
The SMS control plane for India — OTPs, alerts, campaigns & two-way
Connections, API keys, sender IDs, inbound traffic, reports, and billing — the day-to-day Messaging portal for brands and product teams, inside the same CPaaS as WhatsApp journeys, RCS, and enterprise SMPP.
India-ready SMS · OTPs, alerts, campaigns, two-way
Messaging portal
Connections · sender IDs · API · reports · billing
OTP & auth
API-driven
Alerts
Transactional
Campaigns
CDP segments
Two-way
Inbound replies
DLT / SID
India-ready
Journeys
Omnichannel
What you run day to day
- 01Register & manage sender IDs
- 02Issue API keys to product teams
- 03Send OTPs, alerts, and campaigns
- 04Handle inbound / two-way replies
- 05Read delivery & billing reports
- 06Trigger SMS inside Journeys
Carrier-connected India
Messaging runs with connectivity across Airtel, Jio, Tata, and Vodafone — for reach that matches how India actually texts.
Carrier reach
Airtel · Jio · Tata · Vodafone
India operations
Sender ID & DLT-aware
Product traffic
OTP · alerts · API
Omnichannel
Journeys · CDP · RCS fallback
Clarify first
Messaging vs SMPP vs RCS
Most “SMS pages” blur portal, wholesale, and rich messaging. Azmarq keeps them honest — so you pick the right track for brand traffic, aggregator volume, or richer inbox UX.
Messaging (SMS)
Brand portal
Day-to-day OTPs, alerts, campaigns, two-way, sender IDs, API keys, and reports for product and marketing teams.
Enterprise SMS (SMPP)
Wholesale track
Binds, routing policies, rate cards, wallets, and CDR — for aggregators and SMS-heavy enterprises. Separate commercials.
Explore SMPP →Google RCS
Richer SMS inbox
Branding, media, carousels, and suggested replies where devices support RCS — with SMS as the thoughtful fallback.
Explore RCS →Authentication
OTP & login traffic that product teams trust
Ship verification, password resets, and step-up auth over SMS with API keys, sender control, and delivery visibility — not a black-box gateway bolted onto your stack.
- API-driven OTP and transactional auth sends
- Sender ID–aware routing for India traffic
- Delivery & failure signals your app can act on
- Quota and wallet visibility tied to Azmarq billing
OTP · API send
DeliveredSender · AZMARQ · Utility
Latency
Fast
Channel
SMS
Wallet
Debited
Transactional
Alerts customers actually open
Order updates, payment confirmations, dispatch ETAs, appointment reminders, and account notices — the high-open channel when WhatsApp isn’t the right fit yet or SMS is the mandated path.
- Utility-style transactional messaging
- Trigger from your product events via API
- Consistent sender branding customers recognize
- Reports that ops and finance can both read
Transactional queue
Event → SMS · last 15 min
Order #1842 shipped
Utility · DeliveredPayment received ₹2,499
Utility · DeliveredAppointment tomorrow 10:30
Utility · QueuedKYC incomplete — finish now
Utility · DeliveredOutreach
Campaign SMS with segment discipline
Promos, launches, and re-engagement that start from My CDP audiences — so SMS campaigns inherit consent, attributes, and journey logic instead of living in a disconnected blast tool.
- Segment-based sends from My CDP
- Schedule and throttle for deliverability hygiene
- Pair with WhatsApp / RCS when richer media wins
- Fallback SMS when richer channels aren’t available
Campaign · CDP segment
Weekend sale · opted-in
Conversation
Two-way & inbound — not only one-way notifies
When customers reply STOP, HELP, or a keyword, Messaging captures inbound so you can acknowledge, route, or hand off — instead of pretending SMS is fire-and-forget forever.
- Inbound / two-way patterns for reply-driven programs
- Keyword and opt-out handling patterns
- Handoff paths into service workflows where needed
- Visibility in reports so inbound isn’t a mystery
Two-way thread
Inbound captured · keyword YES · journey continued
India operations
Sender IDs & DLT-aware operations
India SMS isn’t “just hit send.” Brands need registered sender IDs, template discipline, and carrier-aware operations. Messaging is built for that day-to-day reality — not a generic global SMS form.
- Manage sender IDs for brand and product traffic
- Operate with India DLT / compliance awareness
- Carrier connectivity including Airtel, Jio, Tata, Vodafone
- Clear separation when you need wholesale SMPP instead
Sender ID control
India · DLT-awarePlatform
Connections, API keys, reports & billing
The Messaging portal is the control plane: connections for your apps, API keys for engineers, send tools for ops, and reports that tie delivery to wallet and plan quotas.
- Connections & authentication for your stack
- API keys for product and backend teams
- Delivery, usage, and billing visibility
- Same Azmarq account as WhatsApp, RCS, and voice
Messaging · SMS portal
Connections · keys · reportsConnections
3 active
API keys
Managed
Two-way
Enabled
Reports
Live
POST /v1/sms/send
sender: AZMARQ · status: queued
report_id: msg_9f2a… · wallet: debit
Orchestration
SMS as a journey step — not a silo
Trigger SMS inside Customer Journeys when a text beats a blast: OTP after signup, reminder if WhatsApp isn’t read, fallback after RCS, or a quiet nudge between richer channels.
- SMS steps alongside WhatsApp, RCS, email, and voice
- Branch on delivery / engagement outcomes
- Reuse CDP segments and journey logic
- Keep SMS inside the omnichannel story
Journey · Checkout recovery
- 01WhatsApp · cart reminder
- 02Wait 4h · no open
- 03SMS · short fallback
- 04RCS · lookbook if capable
Built for how India texts
Sender discipline, carrier reach,and reports finance can trust.
Azmarq Messaging is the brand-facing SMS layer of an India CPaaS — not a generic international SMS form pasted onto a landing page. Operate OTPs and alerts with sender ID awareness, then step into journeys when orchestration matters.
When volume and routing policy become the product, graduate to Enterprise SMS (SMPP) without abandoning the rest of Azmarq.
Where teams use it
SMS jobs across industries
Same portal patterns — different urgency. From fintech OTPs to logistics ETAs, Messaging keeps transactional and campaign traffic operable without a second vendor.
Fintech & BFSI
OTPs, transaction alerts, EMI reminders, and KYC nudges with sender discipline.
E-commerce & D2C
Order / dispatch updates, COD confirmations, and campaign SMS from CDP segments.
Edtech & SaaS
Login OTPs, class reminders, renewal notices, and product lifecycle alerts.
Healthcare & logistics
Appointment reminders, dispatch ETAs, and status texts customers expect on SMS.
Enterprises
Internal and customer transactional traffic with portal control and reporting.
Agencies & partners
Run brand SMS programs under Azmarq while escalating wholesale volume to SMPP.
How it maps on Azmarq
Capability → what you run → module
SMS rarely lives alone. Use this map to see when Messaging is enough — and when CDP, Journeys, RCS, or SMPP should join the story.
OTP & auth SMS
API keys · sender IDs · delivery signals
Messaging (SMS) →Transactional alerts
Event-triggered sends · reports
Messaging (SMS) →Campaign audiences
Segments · consent attributes
My CDP →Multi-step orchestration
SMS + WhatsApp + RCS + voice
Customer Journeys →Richer SMS inbox UX
Media · carousels · suggested replies
Google RCS →Wholesale / high volume
Binds · routing · rate cards · CDR
Enterprise SMS (SMPP) →
Operate SMS without a separate island
01
Connect
Set up connections and API keys for apps and backends.
02
Control
Manage sender IDs and send OTPs, alerts, or campaigns.
03
Converse
Enable two-way / inbound when replies matter.
04
Orchestrate
Trigger SMS inside Journeys with WhatsApp, RCS, and voice.
Next in the Azmarq story
FAQs
Questions about Messaging (SMS)
Straight answers for teams evaluating this module inside Azmarq CPaaS.
Talk to salesMessaging is the day-to-day SMS portal for brands — sender IDs, API keys, two-way traffic, reports, and billing. SMPP is the wholesale / high-volume enterprise track with binds, routing policies, rate cards, wallets, and CDR. Brands start on Messaging; aggregators and SMS-heavy operators often need SMPP.
Messaging (SMS) is classic SMS for OTPs, alerts, campaigns, and two-way. Google RCS upgrades the SMS inbox with branding, media, carousels, and suggested replies where devices support it. Many programs use RCS when available and fall back thoughtfully to SMS.
Azmarq works with leading Indian carriers including Airtel, Jio, Tata, and Vodafone for reach that matches how India texts.
Yes. Product OTP / auth traffic, transactional alerts, and campaign SMS from CDP segments are core Messaging use cases — with sender ID–aware operations for India.
Yes. India SMS requires registered sender discipline and compliance-aware operations. Messaging is built as the brand portal for that reality — not a generic international SMS form.
Yes. Trigger SMS inside Customer Journeys when a text beats a blast — as a primary channel, a reminder, or a fallback alongside WhatsApp, RCS, email, and voice.
Yes. Messaging supports inbound and two-way patterns so replies (keywords, confirmations, opt-outs) can be captured and acted on — not only one-way notifies.
In the Messaging portal: connections and API keys for your apps, delivery/usage reports for ops, and visibility tied to Azmarq wallets and plan quotas — same account as the rest of the CPaaS.
SMS that belongs in your omnichannel story
See the Messaging portal, journey steps, and India-ready operations — or ask sales about SMPP when wholesale volume is the product.
