Inboxes
A place where messages arrive.
Products
Make voicemail handling a defined part of your calling workflow, with clear ownership, appropriate policies and visibility into outcomes.
Call path
Voicemail appears in three different places. Keeping them apart avoids confusion about what a feature does. Which of them are available to your account is confirmed in a demonstration.
The call goes out as part of a campaign.
The system helps identify a person or a likely machine.
The campaign handles likely voicemail the way you decide.
The result is saved for reporting.
Inbox
Where inbox features are supported, they help teams see what needs attention. Availability depends on your configuration.
A place where messages arrive.
A clear list of what is waiting.
Messages linked to the person they relate to.
Only the right people can listen.
Message to callback
A message is only useful if someone acts on it. Assignment follows the rules you set, similar to call routing and management, where supported.
It is captured and recorded.
It goes to the right team or person.
The owner is told, where supported.
The follow-up call is placed.
The result is saved.
Be clear about what outbound voicemail features do and do not exist. Answering machine detection helps identify likely voicemail. Any message-drop feature is available only where confirmed, and consent rules apply.
| Option | What it means | Caveat |
|---|---|---|
| Answering machine detection | Helps identify likely voicemail and machine states. | No detection is perfect. Validate on your own routes. |
| Campaign handling | You decide how each campaign treats voicemail. | Set per campaign in the dashboard. |
| Message drop | Leaving a recorded message. | Confirm availability in a demonstration, and check consent rules first. |
Review voicemail practices with your own advisers.
Policy summary
Voicemail and recordings are sensitive voice data. Decisions about whether to keep them, for how long and who can listen belong to your organisation. See compliance controls for how the platform supports your policies.
Treat messages with appropriate care.
Follow the rules where you and the caller are located.
Available only where the product supports it.
Limit who can listen and download.
Reporting
Voicemail results appear in your reporting and call records, so you can see how campaigns treat them. Review them in reporting and analytics and campaign management. Response time and follow-up views are described only where reported.
Go-live checklist
Treat voicemail like any other part of the workflow. Send outcomes to other systems with the API and webhooks if you need them elsewhere.
Set how each campaign handles voicemail.
Check any message wording before use.
Validate behaviour on your own routes and traffic.
Decide who acts when something fails.
Name the people who own each step.
Product demonstration
A demonstration shows how voicemail is detected and handled in a campaign, and which options apply to your account. The wider flow is explained in how it works.
Voicemail management software helps teams handle voicemail as part of their calling process, whether that means detecting likely voicemail on outbound calls, capturing messages or making sure someone follows up. The scope varies between products, so check which of those functions you need and ask for them to be shown in a demonstration.
Dialog is positioned for outbound teams, and its voicemail features focus on outbound campaigns, including answering machine detection. Whether inbound voicemail capture is available to your account is confirmed in a demonstration, and we would rather tell you plainly than let you assume. Tell us what you need before you evaluate.
Assignment depends on the voicemail features available to your account. Where message capture and routing are supported, messages can follow rules that send them to the right team, with notifications and callback workflows around them. Confirm exactly what is available in a demonstration, and describe the ownership you want so we can check it.
Whether a message-drop feature is available to your account is confirmed in a demonstration rather than assumed. What is available today is answering machine detection, which helps identify likely voicemail so you can decide how each campaign treats it. Consent and calling rules also apply to recorded messages, so review them with your own advisers.
Yes. Voicemail results appear in your reporting and call detail records, so you can see how campaigns treat them. You can review them by campaign and send them to your own systems with the voice API and webhooks. Response-time and follow-up views are confirmed in a demonstration, so ask to see the ones your supervisors need.
Retention and access decisions belong to your organisation, because rules differ by region and by use. Configurable retention and recording policies are described only where the product supports them, so confirm what is available to your account in a demonstration. Agree who may listen to messages and how long they are kept before launch.
Discuss your use case, existing systems, calling volumes and integration requirements with the Dialog team.
Tailored demo · Unlimited users