Every call event is written into the customer's thread as its own row: incoming answered with duration, missed with the reason it was missed, outbound with the outcome, voicemail with a player, and recordings as their own row. Each carries a coloured badge — inbound green, outbound accent, missed red — plus a direction arrow.
Also called: call history in the thread · who called who · missed call in the message list
- 1The voice webhook writes a plain-English sentence into conversation_messages for every call outcome
- 2The thread derives direction from the WORDING, not the stored inbound/outbound flag, because every call row is recorded as an inbound record regardless of who dialled
- 3A voicemail's quoted transcript tail is split back out of the body and handed to the player
- 4On an outbound (accent-coloured) bubble the badge switches to a translucent white treatment so it stays visible
Calls, voicemails and recordings all landed in the thread as grey sentences, so telling "they rang us" from "we rang them" meant stopping to read each one. Worse, only incoming calls were written to the thread at all — a builder could ring a customer, talk for a minute, and that customer's history would show nothing, while the phone's own list had it. Calls now read as calls: colour-coded, with a direction arrow, and both directions recorded.
- Call direction unreadable at a glance
- Half the call history missing from the customer record
- Badges invisible against their own bubble colour
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 →