Skip to main content
The [END_CALL] tag tells the engine to end the call after the agent has finished speaking. The agent says its goodbye line first, then the call is terminated cleanly.

​
Syntax

No parameters. Place it anywhere in the agent’s reply.

​
Example

Caller: “Great, thanks for the help.” Agent: “You’re welcome. Have a lovely day. [END_CALL]”
The caller hears the goodbye. Then the engine ends the call cleanly.

​
When to use it

Tell the agent in the system prompt when it should end calls:

​
How call ending works

Nixflex uses three layers to make sure every call ends cleanly on the caller’s phone. Closing our own audio stream is not enough — we must explicitly tell the telephony provider to terminate the call.
  1. Trigger — something decides the call should end ([END_CALL] tag, silence timeout, max duration reached, etc.).
  2. Direct telephony hangup — we call the telephony API to terminate the call leg. The phone disconnects within ~1 second.
  3. Post-stream safety net — when our stream closes, the telephony provider asks our engine what to do next. We return a hangup instruction so even if step 2 fails, the call still ends.
All three layers run in parallel. The caller’s phone disconnects, the recording saves, post-call analysis runs, and the webhook fires.

​
Other ways calls end

[END_CALL] is the graceful option. Calls also end automatically when one of these conditions is met. The exact value is stored on the call record as ended_reason. Use ended_reason to filter analytics and identify problem calls.

​
Configuration

The two silence/duration thresholds are agent-level fields: Set them when creating an agent or update them later. See Create agent.
If you want the agent to confirm the booking back to the caller before ending, write that into the prompt. The agent will speak the confirmation, then emit [END_CALL].