Skip to main content
Call Events is a technical view of the events recorded before, during, and after calls. Use it when Call History shows the conversation but you need more detail about execution.

​
Find the relevant events

Select an agent, then filter the event table by fields such as:
  • date;
  • call ID;
  • event status or HTTP status code;
  • event type or name;
  • execution stage; and
  • execution time.
Use Refresh to load newer events. Select an event to open its details; the fields shown depend on the event type.

​
Investigate a call

  1. Copy the call ID from Call History or Call Details.
  2. Filter Call Events by that ID.
  3. Order the events by time and identify the first unexpected status or result.
  4. Open that event and inspect its available request, response, timing, or telephony details.
  5. Compare the event with the corresponding block in Call Details.
Focus on the earliest event that differs from the expected behavior. Later failures can be consequences of an earlier missing value, rejected request, or telephony event.

​
Handle event data carefully

Event details can contain phone numbers, request data, returned values, and other call context. Share only the fields needed for the investigation, and do not copy credentials or sensitive customer data into public channels.
Event names and fields are technical execution data and may vary by event type. Use the product-facing block name and behavior when writing customer documentation or support guidance.
Use Call History for the transcript and block trace, Call Paths for route patterns across calls, and Call Events for the underlying execution timeline.
Last modified on August 10, 2026