Lists
Load and maintain contact lists.
Solutions · By Role
Set up and maintain campaigns, lists and users without waiting on developers. See the admin console in a live demo.
Task map
The hands-on work behind every campaign, all in the browser. The strategic view is on the operations page.
Load and maintain contact lists.
Create and adjust campaigns.
Add people and set permissions.
Assign and watch outbound numbers.
Investigate failed calls.
Setup walkthrough
Set up a campaign from import to schedule in campaign management.
Load the approved list.
Match fields to the campaign, where supported.
Set calling windows.
Set attempts and spacing.
Granular permissions decide who can see and change what. The roles below are typical; configure them to your structure.
| Role | Typical access | Typical restriction |
|---|---|---|
| Admin | Campaigns, users, numbers and settings. | Limited to the admin team. |
| Supervisor | Monitoring and campaign adjustments. | No user or number changes. |
| Agent | Their own calls and dispositions. | No settings. |
Unlimited users: add people without adding seats.
Number table
Assign, rotate and watch outbound numbers; see caller ID reputation.
Numbers per campaign.
Only where supported and appropriate.
Number health at a glance.
Dialog voice routes.
Troubleshooting flow
Diagnose failed calls and routing problems with call detail records, which include SIP codes, MOS scores and carrier costs. Routing is covered in call routing and management.
Look up the call detail record.
SIP codes show why a call failed.
MOS scores show call quality.
Route, rule, list or carrier.
Change checklist
Change safely: test first, keep a record and know how to roll back. Repetitive tasks can be automated with the voice API; general dialer workflows are on the call center dialer page.
What changes, why and when.
Try the change on a small list.
Note the change and the owner.
Know how to undo it.
Product demonstration
A live demonstration walks through campaign, list, user and number setup. Documentation and help are on the support and help center page.
A dialing admin sets up and maintains the dialer: contact lists, campaigns, users and permissions, outbound numbers and caller ID, and the routing and retry rules behind them. Admins also troubleshoot failed calls and keep changes documented. In Dialog this work happens in the browser, without a dialer server to maintain.
Yes. Campaigns, lists, users and numbers are managed in the browser, so day-to-day setup does not need developers. Developers help when you connect other systems through the API and webhooks or want to automate repetitive admin tasks. Which settings are configurable for your account is confirmed in a demo. Most admins start without any code.
Admins add users in the dashboard and use granular permissions to decide who can see and change what, typically separating admins, supervisors and agents. You can give access to everyone who needs it. Review permissions regularly and remove access when people change roles. Keep a short record of who has which role.
Lists are imported into campaigns, with field mapping and formats confirmed for your account in a demonstration. Clean them before import: remove duplicates, apply do-not-call and opt-out suppression and check that every contact may be called. Clean lists waste fewer attempts and protect your numbers. Keep a record of each import and who approved it, so problems can be traced.
Numbers are assigned per campaign, and their health can be monitored. Rotation is used only where it is supported and appropriate. Keep a simple record of which number belongs to which campaign, so troubleshooting stays easy. Review the assignments whenever campaigns change.
Start with the support and help pages, and use the voice API documentation for integrations and automation. The support team can help with configuration questions, and the scope of support is set out in your agreement. Keep your own notes on how your campaigns are configured, so knowledge stays with the team.
Discuss your use case, existing systems, calling volumes and integration requirements with the Dialog team.
Tailored demo · Unlimited users