Sequential dialing

Use one destination per <Dial> and return the next <Dial> from its action URL when the attempt does not connect. This keeps the sequence explicit in your application.

Sibling <Number> elements inside one <Dial> run concurrently. Use separate Dial instructions when destinations must run in order.

Attempt the first destination

Set redirect="true" so Vobiz executes the XML returned by the action endpoint:

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Dial
      callerId="+14155550100"
      timeout="20"
      action="https://example.com/dial-next"
      method="POST"
      redirect="true">
    <Number>+14155550101</Number>
  </Dial>
</Response>

Your /dial-next handler receives the final DialStatus. Return a fallback Dial only for outcomes your application considers unsuccessful, such as no-answer, busy, or failed. If the call completed successfully, return your normal completion XML instead.

Return the fallback destination

For an unsuccessful first attempt, /dial-next can return:

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Dial
      callerId="+14155550100"
      timeout="20"
      action="https://example.com/dial-result"
      method="POST"
      redirect="false">
    <Number>+14155550102</Number>
  </Dial>
  <Hangup/>
</Response>

Because the second Dial uses redirect="false", Vobiz sends its final result to /dial-result, ignores XML returned by that endpoint, and continues to <Hangup/>.

Replace callerId with a Vobiz number owned or authorized by your account. Set each Dial timeout explicitly so an unavailable destination does not delay the sequence.

XML Overview

Sequential dialing

Attempt the first destination

Return the fallback destination

Next steps

​Attempt the first destination

​Return the fallback destination

​Next steps

Attempt the first destination

Return the fallback destination

Next steps