How to get there: Top bar β Phones β a phone β π₯ Contacts β click a contact. The list below the live panel is every past call, newest first.
Each row shows scenario, status, start time, duration, message counts, mismatches, and whether it was scheduled β° or triggered β‘.
| Status | Meaning |
|---|---|
| Completed | ran to the end |
| Failed / Error | a step failed |
| Aborted | someone stopped it |
| Expired / Timeout | ran out of time waiting for a reply |
| Running / Pending | still going |
Filter with the chips along the top. Both the filter and the paging happen on the server, so the counts you see are for the whole history, not just the page in front of you.
Click any row.
The diagram shows the scenario as it existed when that call ran β not as it looks today β with each step coloured:
| Colour | Meaning |
|---|---|
| green | done |
| red | failed |
| faded | never reached, because something earlier failed |
This is why editing a scenario never changes your old reports: each call stores its own snapshot.
π‘ Events, beside the diagram, is the raw timeline: every message sent, every reply received, every timeout and every mismatch, each with a timestamp.
This pairing is the point of the product.
The most common finding: the reply is right there in the events, but the step still failed β which means the EXPECT stepβs match mode was too strict. See Chapter 06.
Next: The chat view