Important: Be Notified of Failures
If your Ringless Voice Mail HTTP POST has something invalid in the configuration then the Ringless Voice Mail will not be sent.
It is also common to attempt sending a Ringless Voice Mail to a number that does not have a voice mailbox. Those attempts will also fail.
Check the HTTP POST
If you are aware that the Ringless Voice Mail failed for a specific contact you should view the “Campaigns Tab” on that Keap contact record and look for the HTTP POST in the Recent Campaign History section. The HTTP POST may show an error, and if it does then clicking to open that error may reveal more information about the cause.
Failure Notification
You should create the API Goal in a Keap campaign that will be triggered if your Ringless Voice Mail fails. You can use that goal to notify you about the failure, for example by applying a tag that causes the contact to appear in a Saved Search report you are monitoring on your Keap dashboard.
The API Goals for Ringless Voice Mail failures can be found in the Automation Triggered when Sending s Ringless Voicemails page. You can also find that information below.
Please Read: After you add or change an API Goal in your Keap Campaign Builder you must inform turboDial to look for it by clicking the Reset Disabled Goals button in your turboDial Management Account.
Ringless Voice Mail Send Failure from Sly Broadcast
- When Sly Broadcast reports back that a Ringless Voice Mail message failed. When this happens there will usually be more details about the failure in the Note Record attached to the Contact Record.
- Integration: turboDialCV
- Call Name: MailFail
Ringless Voice Mail Send Failure from turboDial
- When a Ringless Voice Mail message is failed by turboDial. Common cases are when the queue limit is exceeded by sending too many Ringless Voice Mail HTTP POSTs in short order, or when a Name/Value pair in your HTTP POST is invalid.
- Integration: turboDialCV
- Call Name: SendFailed