🇪🇸 Español 🇬🇧 English 🇧🇷 Português

IVR node: Go to another IVR

Jump from one IVR flow into a completely different IVR in your library with the Go to another IVR node — a one-way handoff.

Jul 11, 2026

What it's for

Hands the whole call off to a different IVR in your library (Workspace > IVRs). It's a one-way jump — the call continues from the destination IVR's entry node and never returns to the original flow. This differs from the Submenu node (which can act as a reusable sub-flow within the same design): Go to another IVR fully switches the "program" the call is running.

Requirements

  • The destination IVR must exist in the library and belong to the same workspace as the channel, with at least one saved design. It doesn't need to be published: if there's no published version, the node automatically falls back to the draft version, as long as it has nodes.
  • It has no configurable outputs in the editor — it's a terminal node in the source flow: everything after it happens inside the destination IVR, not here.

Configuration

  • Target IVR: pick one from the list, or type its ID directly, or a variable (e.g. {{detected_lang_ivr}}) that resolves at call time.

Example

You have a "General reception" IVR and want Portuguese-speaking callers to hit a completely different menu, with its own hours and agents. After the Detect language node, the pt edge connects to a Go to another IVR node pointing at "Brazil reception". From there the call follows the entire "Brazil reception" design and never returns to "General reception".

Tips

  • Use it to split whole audiences or campaigns (language, brand, special hours) into independent IVRs instead of cramming all the logic into one giant diagram.
  • If you need to return to the original flow after a sub-routine, use Submenu instead of this node.

Troubleshooting

  • If the target IVR isn't configured or the ID doesn't exist, the call hangs up at that point — check that the IVR exists, belongs to the same workspace as the channel, and has at least one saved design (draft or published) with nodes; it doesn't need to be published.
  • If you point to a variable and it's empty at call time, the node has nowhere to jump — make sure an earlier node always sets it.
Was this helpful?

Related articles