API
Manage calls, campaigns and agents programmatically.
How it works
See how your operation can connect voice routes, configure campaigns, run agent workflows and feed call data into the systems you already use.
The workflow
The operating journey, including the setup work that comes before the first call. The sequence is a proposed process and is confirmed with you during scoping.
Agree volume, geography, compliance and integration needs.
Set up Dialog voice routes and test them.
Set up campaigns, roles, permissions and routing rules.
Run representative calls and check agents, recording and reporting.
Supervise live activity and send call data to your systems.
Step 1
Start with the volume, geography, compliance and integration needs that will shape the rollout. Capacity and timelines are agreed during scoping, not assumed.
Step 2
Calls run over Dialog-supplied voice routes, which are tested during setup before production traffic.
Use routes supplied by Dialog for campaigns where that fits.
List the numbers you need and how inbound and outbound traffic should be routed.
Test routes on representative traffic before go-live.
Step 3
Create a controlled workflow that suits the way agents and supervisors work.
Step 4
The practical experience of agents and managers, from starting calls to reviewing outcomes.
Agents work from the browser with the campaign and contact in front of them.
Supervisors see agents, queues and campaign results as they happen.
Watch calls, statuses and outcomes without waiting for a report.
Helps identify likely voicemail. Validate it against your own routes and traffic before relying on it.
Step 5
Use events, call records and connected systems to support reporting and automation.
Manage calls, campaigns and agents programmatically.
Receive an event for every call to update a CRM or notify a team.
Granular records of each call event for reporting and audit.
Send call data to your warehouse and BI tools, subject to implementation.
Example event
{
"event": "call.completed",
"campaign_id": 42,
"reference_id": "YOUR_REFERENCE_ID",
"duration": 124,
"disposition": "sale"
}
Go live
Explain the operational checks that sit between configuration and full production. Compliance with legal and regulatory requirements remains the responsibility of your organisation.
Use cases
Four common ways the same steps play out.
Controlled outreach with recordings and audit trails. Your team keeps legal decisions.
Financial services solution → SalesFast follow-up on leads, with call outcomes pushed to the CRM.
Sales solution → InternationalRoute testing per destination before production traffic.
Call routing →Proof
See the actual interface before you book a technical discussion. Walkthroughs are run on a scenario that matches your campaigns.
Start with a demo or a pricing request. A specialist scopes your volume, routes, users and integrations, then agrees a staged plan with you. Book a demo to begin.
Team structure, expected concurrency, call destinations, working hours, numbers, reporting needs, integrations, and security or service requirements. Share what you have and we fill in the rest during scoping.
It depends on your provider and the numbers involved. Number inventory and any porting needs are reviewed during scoping, and provider timelines apply.
In the browser: lists, calling rules, roles, permissions and routing. Approved calling modes are agreed for each campaign during setup.
Yes, through the API and webhooks, which send call events to the systems you use. Details depend on your CRM and implementation. See the API documentation.
Representative traffic is run on each route before go-live, and results are reviewed with you. Call detail records show what happened on each call.
It depends on volume, integrations and approvals, so we do not commit to a timeline before scoping. Your written plan sets out stages and responsibilities.
Share your calling regions, approximate volume and required integrations.