Azmarq — One Platform · Every Conversation

Developers · Voice

Programmable voice on Voice 360

Build outbound calls, IVR handoffs, and voice notifications on Azmarq Voice 360 capabilities available to your plan.

Built for: Contact center and product teams automating calls

  • Outbound & notifications
  • IVR handoffs
  • Digital + voice

What you can build

01

Outbound & alerts

Trigger voice notifications and campaign-style outbound where entitlements allow.

02

IVR handoffs

Connect programmable steps to IVR Studio flows for menus and routing.

03

Omnichannel pairing

Start in WhatsApp or inbox, escalate to voice — or callback from a journey.

Quick start

  1. 01

    Confirm Voice entitlements

    Voice modules are plan-based (often Growth+). Validate numbers and minutes with sales if needed.

  2. 02

    Provision numbers / DIDs

    Set up calling identities in Voice 360 before API traffic.

  3. 03

    Place a test call

    Use API credentials to trigger a low-risk test destination.

  4. 04

    Hook status events

    Subscribe to call status webhooks for answered, failed, and completed states.

Auth

Credentials from your console

Voice API access follows account entitlements. Confirm live endpoints, codecs/number rules, and minute wallets in console docs.

Illustrative outbound (shape only)

http
POST /v1/voice/calls
Authorization: Bearer <AZMARQ_API_KEY>
Content-Type: application/json

{
  "to": "+9198XXXXXXXX",
  "from": "+91XXXXXXXXXX",
  "action": "play_tts",
  "text": "Your appointment is confirmed for tomorrow at 10 AM"
}

# Confirm IVR connect, AMD, and recording options with your account team.

Illustrative only — not a live contract. Confirm paths and fields in developers.azmarq.com.

Common use cases

Appointment reminders

Voice nudges when SMS/WhatsApp alone isn’t enough.

Collections & confirmations

Outbound flows with IVR options to confirm or escalate to an agent.

Voice OTP

Speak codes for users who can’t receive SMS — see OTP API.

FAQs

Voice API — FAQs

Integration basics, credentials, and how this API relates to the product console.

Talk to sales

Voice entitlements are plan-based (often Growth+). Confirm numbers, minutes, and API access with sales.

Yes — many teams pair digital channels with Voice 360 callbacks. Orchestrate from Journeys or your backend.

Build on Voice

Grab credentials in the console, or talk to sales if you need channel enablement, WhatsApp WABA setup, or SMPP packaging.

Customer feedback

Conversations that teams can actually operate

Honest notes from growth, CX, ops, and compliance teams running CTWA, WhatsApp, journeys, inbox, voice, AI, and enterprise SMS on Azmarq CPaaS.

Meta Business Partners

Google Partner · Carrier-connected India · ISO 27001 · SOC 2 Type II

Featured feedback · CTWA Ads

CTWA leads finally land in one place. Our team qualifies on WhatsApp instead of chasing form dumps across tools — then My CDP keeps the thread for journeys.
AR

Ananya R.

Performance Marketing Lead · D2C · Bengaluru

Why teams stay

  • WhatsApp-first ops with SMS, RCS, email & voice
  • India-ready journeys, DND timing & sender discipline
  • Inbox, CDP, and AI handoff in one CPaaS stage
  • Enterprise SMS (SMPP) when volume is the product
Customer Journeys
Journeys with DND-aware waits and WhatsApp + SMS fallbacks feel built for India — not a US playbook pasted on.

Vikram S.

Growth Manager · Edtech · Pune

Unified Inbox
Unified Inbox cut the tab chaos. Tickets, queues, and SLAs finally match how our contact center actually works.

Neha K.

Head of CX · BFSI · Mumbai

Enterprise SMS
We needed SMPP-grade volume without bolting on another vendor. Azmarq kept wholesale SMS next to our WhatsApp stack.

Rahul M.

Operations Director · Logistics · Delhi NCR

Trust & Security
Security reviews went smoother with ISO 27001, SOC 2 Type II, and clear localization answers. That mattered for sign-off.

Priya T.

IT Compliance · Healthcare · Hyderabad

AI Agent Studio
AI Agent Studio handles FAQs on CTWA traffic, then hands off cleanly. Humans only see conversations that need them.

Arjun P.

Product Owner · Marketplace · Chennai

My CDP
My CDP stopped our spreadsheet segment nightmare. Opt-ins and attributes stay with the contact when we broadcast or drip.

Sana M.

CRM Lead · Retail · Ahmedabad

Voice 360
Voice callbacks after WhatsApp go quiet closed more high-intent leads than another SMS blast. Same profile, same journey.

Karan D.

Sales Ops · Real Estate · Noida

Messaging (SMS)
Messaging SMS for OTPs and alerts sits in the same console as WhatsApp. Finance finally sees one wallet story.

Meera L.

Engineering Manager · Fintech · Gurugram