The Recents tab reads the call fact table, not the message thread. Each row shows who, when, how long, and — when it was missed — why in plain English ('went to a personal voicemail', 'no one was set to ring', 'no answer', 'busy'). A recorded conversation plays inline on its own row. Tapping the name opens the bond chips to jump to their estimate or pipeline card.
Also called: call history · recent calls · who called · missed call list
- 1GET /api/comms/calls reads the `calls` table with filter=all|missed|voicemail
- 2Direction filter chips and a name/number search narrow the list
- 3The search only applies its number leg when the query actually contains digits
- 4Miss causes are mapped to human labels; the arrow itself carries the direction colour
The conversation thread carries the human sentence; the call list has to carry the facts — how long it lasted, who picked up, why it was missed, whether there is a recording. Searching it by name was broken in a way that looked like the feature simply did not work: a letters-only search matched every row in the list, so typing a name returned everything. Recents now filters by direction, searches by name or number, and puts a plain-English miss reason on every missed call.
- A call list with no explanation of misses
- Search that silently matched everything
- Recordings only reachable from a separate tab
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →