The Sandpit explained (Voice)

As you use Upwire to power your business messaging needs, you may hear us refer to the "Sandpit". So what exactly is the Sandpit, and what is its purpose?

Mission Control

Think of the Sandpit as the mission control for your flow. It is a visual representation of the flow of your data through your template where you can launch your campaign, split your data for A/B/C testing, and set your master template logic and reporting preferences. 

Delivery outcomes

There are 4 basic outcomes for an outbound call flow:

  • Unanswered: If the call is unanswered, hits an answering service, experiences a temporary network issue or the number is engaged, your flow will follow the pink delivery outcome path. By clicking on the pink icon, you can set the logic for those calls. For example, you can set the system to retry twice every 30 minutes before giving up. If your call remains unanswered after the retries have run, your flow will follow this path. You can add another contact method for these calls, for example, an SMS alerting the recipient that you have tried to reach them and asking them to call back.   

  • Permanent failure: If your call experiences a permanent failure, or hits a module that you have tagged as a failure or as incomplete, your flow will follow the red delivery outcome path. You can add another contact method for these calls, for example, an email alerting the intended recipient that you have tried to reach them but the number is not working and asking them to update the contact details.

  • Success: If your call is successful, your flow will follow the green delivery outcome path. You can add another contact method for these calls, for example if you have a credit card payment module in your flow and you would like to send an email receipt to all successful payments, you can tag the module that flows from your API pass node as success. If the call flow hits that module, it will go down the success path and trigger the email template you connect.

  • Tag route: The yellow tag path, gives you another option to add a new message template based on the tags you set for your voice modules in your voice template. For example, this would allow you to transact off a "tagged fail" call, which may not be a true failure in that the call was actually successfully connected, but the desired outcome of the call (e.g. a payment) failed. This is another path to give you more flexibility for routing the flow logic. 

The band-aid

The band-aid can be used to add another layer of messaging based on data gathered during your call. For example, if you have a menu option asking the caller "Would you like us to send you this information via SMS? Press 1 for yes or 2 for no." then you can set the following rule in the band-aid: 

This rule will add a new node beneath the band-aid which allows you to connect an SMS template (or an email template or another voice template). 

The hamburger menu

The hamburger menu is where you can:

  • obtain the unique template ID for your flow as well as the current job number if the template has an active job running ("About this Template")
  • buy numbers for to use in your template ("Buy Numbers")
  • push changes to production ("Activate Template")
  • replace or edit the template data added when you set up the template ("Edit Template Data")
  • edit the mapping of your data ("Edit Template Variables")
  • view reporting from your jobs ("Get Collected Data")
  • delete your template ("Delete Template")
  • get your Jobs API to integrate your template to your systems via API ("Show Jobs API")

David is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.