Telephony that fits the stack you already run.
Connect CallMangal to cloud telephony, SIP infrastructure, or India/local telephony providers — keep your existing telephony investment instead of rebuilding your calling stack.
The same agent, however the call starts.
A workflow you build and browser-test in CallMangal runs the same way whether a customer calls in, or an agent calls out — telephony is the connection point, not a second workflow to maintain.
Inbound calling
A caller dials a connected number and reaches the configured agent workflow.
Outbound calling
An agent calls out — one number, or a campaign run against a contact list.
Browser test first
Test the workflow over WebRTC before any number is connected.
Human handoff
Both directions can hand a conversation to a person, with context preserved.
Built for global and India-focused telephony environments.
Use different providers across regions or businesses. Provider availability is confirmed by the CallMangal team — these are supported integrations, not certified partnerships.
Global providers
Indian / local providers
SIP / custom infrastructure
Bring your own SIP trunk or carrier relationship.
If you already have telephony infrastructure — a SIP trunk, a PBX, or an existing carrier relationship — connect it directly instead of, or alongside, a supported cloud telephony provider. This is a common fit for existing infrastructure and specific regional or carrier needs that a standard provider does not cover.
From a real phone number to a finished, reviewable call.
Connecting telephony means pointing a phone number — provisioned through a supported provider, or brought in over your own SIP trunk — at a CallMangal agent workflow.
Number connected
A phone number is provisioned or connected via a supported provider or SIP trunk.
Routed to a workflow
The number is pointed at the agent workflow built and browser-tested for that job.
Call handled
The agent runs the conversation — inbound or outbound — the same way it did in testing.
Outcome captured
Recording, transcript and structured fields are stored, per your configuration.
Follow-up triggered
A webhook, CRM update or human handoff carries the result forward.
Who owns what, whichever way you connect.
Your telephony provider or SIP infrastructure
Carrier connectivity, phone number provisioning, and call routing between the public phone network and CallMangal.
CallMangal
The conversation itself — understanding the caller, running the workflow, capturing the outcome, and triggering what happens next.
Most connection issues trace back to one of three places.
Authentication / registration
The connection between CallMangal and your provider or SIP trunk is not established.
Number routing
The number is not pointed at the intended agent or workflow.
Network / firewall
SIP or media traffic blocked between your own infrastructure and CallMangal, if using a custom trunk.
Confirm a browser test still runs cleanly first — that isolates whether an issue is in the workflow itself or in the telephony connection.
Tell us what you're already running.
Cloud telephony, SIP trunk, or a local provider — we'll walk through how it connects to a CallMangal agent.