Skip to main content
The Redirect element transfers control of a call to a different URL, which then returns a fresh <Response> to drive the rest of the flow. The redirect URL is the element’s text content. Any elements placed after <Redirect> are never processed - Redirect must be the last element you intend to run.

​
Attributes

​
Nesting rules

Redirect takes no child elements. Its text content is a single fully qualified HTTPS URL. Redirect cannot be nested inside another verb - it is a top-level child of <Response>.

​
Parameters sent in the redirect request

​
Examples

​
Redirect to a new flow

When the Speak element finishes, Vobiz requests the redirect URL and runs whatever XML it returns.

​
Loop back to a menu

Use Redirect to re-present an IVR menu after invalid input, instead of duplicating the menu XML.

​
Example redirect webhook

POST to the redirect URL

​
Edge cases and tips

  • Elements after Redirect are dead code. Vobiz stops processing the current document the moment it reaches Redirect. Put fallback logic in the redirect target, not after the Redirect element.
  • The target must return valid XML. The redirect URL must respond with a <Response> document served as application/xml. A non-XML or error response drops the call.
  • Redirect vs transferring with Dial. Use Redirect to change which of your endpoints controls the call flow (branching, looping, handing off to another service). Use Dial to bridge the caller to another party (a phone number or SIP user). To transfer a live call to an agent, return XML from the redirect target that contains a Dial - see Transfer a call.
  • State is not carried automatically. Redirect posts the standard call parameters but not your application’s own state. Pass context via query parameters on the URL or look it up by CallUUID.