Breadcrumbs

Hang-up Node

Node

Hang-up Node

Description

The Hangup Node is designed to execute specific actions right after a call is terminated — whether the call ends naturally, is dropped by the caller, or disconnected by the system. It ensures that post-call processes are handled reliably, even though the main IVR flow has ended.

Purpose

  • To define post-call logic such as logging, analytics, and clean-up operations

  • To trigger APIs or processes for updating call status, storing call metadata, or auditing

  • To maintain a clear separation between the main IVR flow and after-call events

Behavior

  • The Hangup Node is not part of the main call flow

  • It is linked directly to the Start Node

  • When a call ends, this node and its downstream flow are automatically triggered

  • You can design any number of actions after this node, including:

    • API calls

    • Database inserts

    • Logging user activity

    • Sending alerts or emails

Use Cases

  • Update the call record status via API

  • Log the final user input or choices

  • Store call duration and metadata in a database

  • Trigger alert or monitoring systems for analytics

Usage Notes

  • Only one Hangup Node should exist in an IVR design

  • Must be connected directly to the Start Node

  • This node is triggered only when the call ends, and should not be used in the main decision-making flow

Flow Example 

├── Main IVR Flow ➝ Nodes ➝ Deploy
├── Exception Node ➝ Error Handling Flow
└── Hangup Node ➝ Generate Report ➝ Call API To Sumbut ➝ End
image-20250805-050023.png


Best Practices

  • Always use a Hangup Node in production flows for proper call closure

  • Log key call data to help with reporting and audits

  • Keep its logic separate from the main call interaction to avoid unintended execution