Outbound FAQs and Tips
Last updated
Last updated
Plum Voice recommends scheduling batch calls to begin at a fifteen minute interval past the hour (e.g. 15, 30 or 45 minutes). We do NOT recommend scheduling batches at or near the top of the hour (e.g., 00) because doing so can cause unnecessary call spikes that can negatively impact call completions.
The short answer: When it reaches the top of the queue.
The longer answer: The time of day, the number of calls a client wants to make, and the number of other campaigns in the Plum Outbound Queue can affect how quickly a client's calls get placed. Any phone numbers that get put back into the Plum Outbound Queue so it may take longer for some calls to complete than others.
Plum's Outbound Queue is optimized for placing calls. As a result, getting to the next call in the queue takes priority over updating the status of the previous call. Each phase of the outbound process contains several potential status changes. In order to ensure that calls go out as quickly as possible, call status updates may be delayed.
Dialing via the outbound queue and the processing of call status data are two separate, yet inter-related processes within the Plum Platform. It is possible, therefore, that a call or a call campaign can be completed before all the status updates for those calls are processed in their entirety.
Once the platform has call status data, it sends that information to the customer using the provided result_url.
First, let's explain how we determine if a call has failed or completed.
A call is considered "failed" when it has been queued, dialed, and does not get answered. Calls may not be picked up for a like the number is busy, caller didn't answer, etc. The call status of "failed" does not mean the call has failed to be queued or dialed.
A call is considered "completed" when the call is ultimately answered. The only caveat with this is answered calls can include voicemail. To provide the best user experience, we recommend building your application with to better handle those situations.
If an issue with queuing outbound occurs, it would be made available at the time of the API request or visible in the pending queue. Stuck calls in the pending queue may have gone out but did not update properly in our system, finding correlating call logs with the stuck call may help in debugging further.
Stopping a running campaign is possible if the campaign's calls have not entered the outbound queue. However, the outbound queue is designed to process high volumes of calls quickly.
Once an outbound campaign has been submitted, calls often enter the queue immediately. You may only have a limited window to stop a campaign before any calls go out.
You can see the status of your calls by navigating to the outbound calling page and clicking on "view" in your campaign. You can adjust the number of completed entries and refresh the screen. In the table you can see the number dialed, ani (if applicable), status, attempt, callee type, and call info. The will point you in the right direction why we consider that call has failed. You can also see this information when clicking the info icon to see the call info modal.
Please view our for more information on outbound campaigns.