# Hang Up Call

Use the **Hang Up Call** component to end a caller's connection within a call flow. It is one of the end (terminating) components: as soon as a caller is routed to it, the call is disconnected.

## What this component does

Hang Up Call closes out the current call flow by dropping the caller's connection. Place it wherever the interaction should finish, for example after a message has played, once a self-service task is complete, or on a branch where no further routing is intended.

:::caution
This component ends the call immediately. Any step you place after it in the caller's path will never run, because the caller is already disconnected. Put Hang Up Call only at the true end of a branch, not in the middle of a route you still expect the caller to travel through.
:::

## Configuration

There is nothing to configure. Drop the component into your flow and connect it where you need the call to end.

:::tip
Because it needs no settings, Hang Up Call is a clean way to close off any branch that should simply stop, for example an after-hours branch or a menu option that only plays a message. Use it instead of leaving a branch unconnected.
:::

## Connections

Hang Up Call includes one built-in branch, **Call End**. Although the call itself is disconnected, you can attach this branch to a single follow-up component so that an action runs after the call has ended. The branch can connect to any one of the components below.

:::note
The Call End branch fires *after* the caller has been disconnected, so it is meant for background (back-office) work such as logging, notifications, or data updates. The caller cannot hear anything from a component on this branch, so do not attach steps that expect to talk to the caller. You can attach only one component to the branch.
:::

| Component | What it does |
|-----------|--------------|
| Internal Data Ops | Queries and updates records in the built-in PBX (Private Branch Exchange, your phone system's call-routing engine) database. |
| Email Sender | Sends an email, so you can push notifications, alerts, or caller-specific details. |
| Database Access | Connects to a database during the flow, running SQL (Structured Query Language, the standard language for reading and writing database records) to read or write data. |
| HTTP Request | Sends an HTTP (Hypertext Transfer Protocol, the protocol web services use to exchange data) request to an external web server to share data with third-party services. |

### Internal Data Ops components

Internal Data Ops covers several purpose-built components. For details, see:

- [Get Extension Presence Status](/pbx/call-flow-designer-guide/get-extension-presence-status/)
- [Set Extension Presence Status](/pbx/call-flow-designer-guide/set-extension-presence-status/)
- [Get Queue Agent](/pbx/call-flow-designer-guide/get-queue-agent/)
- [Get Queue Info](/pbx/call-flow-designer-guide/get-queue-info/)
- [Get Agent Status](/pbx/call-flow-designer-guide/get-agent-status/)
- [Set Agent Status](/pbx/call-flow-designer-guide/set-agent-status/)
- [Get System Info](/pbx/call-flow-designer-guide/get-system-info/)
- [Get System Capacity](/pbx/call-flow-designer-guide/get-system-capacity/)
- [Get Extension Info](/pbx/call-flow-designer-guide/get-extension-info/)
- [Get Company Contact Info](/pbx/call-flow-designer-guide/get-company-contact-info/)

### Other follow-up components

- [Email Sender](/pbx/call-flow-designer-guide/email-sender/)
- [Database Access](/pbx/call-flow-designer-guide/database-access/)
- [HTTP Request](/pbx/call-flow-designer-guide/http-request/)