Status-update Event

The status-update event informs your server about the current state of every AI call. These updates are crucial for tracking live call progress, monitoring terminations, and debugging integration issues. If you’ve configured a server URL for your agent, all status updates are pushed to your server in real time.

Example Payloads

Call In Progress

{
  "eventTimestamp": 1756368117035,
  "eventType": "status-update",
  "callSession": "d0132d99-a7a4-4826-ad7b-72fee9f6f61f",
  "fromCaller": "+31612345678",
  "toAssistant": "+31850123456",
  "status": "in-progress"
}

Call Ended

{
  "eventTimestamp": 1756368117035,
  "eventType": "status-update",
  "callSession": "d0132d99-a7a4-4826-ad7b-72fee9f6f61f",
  "fromCaller": "+31612345678",
  "toAssistant": "+31850123456",
  "status": "ended"
}

Call Ended with Debugging Info

{
  "eventTimestamp": 1756368117035,
  "eventType": "status-update",
  "callSession": "d0132d99-a7a4-4826-ad7b-72fee9f6f61f",
  "fromCaller": "+31612345678",
  "toAssistant": "+31850123456",
  "status": "ended-with-debugging",
  "debugging-artifact": "Couldn't Get Assistant. Assistant Request Did Not Return One."
}

Status Types Explained

in-progress:
The call has started and is currently ongoing.

ended:
The call has completed normally, either by the customer or the agent.

ended-with-debugging:
The call ended due to an error or unexpected situation. The debugging-artifact field contains technical details to help you diagnose the issue (e.g., invalid assistant config, server response errors).

Viewing Logs in the Dashboard

All status updates are indexed and displayed on the /logs page of your Flireo dashboard. This overview helps you monitor call history and quickly identify issues.

Status: Shows if a call is active, terminated, or had an error

Reason: Why the call was ended (e.g., customer-ended-call)

Debug Info: Displays the debugging-artifact for quick troubleshooting

Use Cases

Live Call Monitoring:
Build dashboards or notifications for active and completed calls.

Integration Health:
Quickly spot issues in your assistant webhook logic using debugging info.

Compliance & Auditing:
Maintain a full history of all call attempts and terminations.

Developer Debugging:
Use ended-with-debugging events to fix configuration or workflow errors.

Implementation Notes

Status updates are sent automatically for every call session if a server URL is set.

You do not need to respond to these events.

Use the callSession/eventTimestamp for cross-referencing with other events (e.g., end-of-call-report).

All status events are stored and searchable in your dashboard logs.

For more on troubleshooting and analytics, see Conversation Logs.

Next:
Learn about end-of-call-report or discover how to customize assistant workflows.

Status-update Event

Example Payloads#

Call In Progress#

Call Ended#

Call Ended with Debugging Info#

Status Types Explained#

Viewing Logs in the Dashboard#

Use Cases#

Implementation Notes#