- Every action is written to the timeline the moment it happens, not summarised afterwards.
- The things that did not happen are counted too, each with its reason.
- An agent should never have to ask support what the AI did last night.
There is a particular kind of AI product that goes quiet for four minutes and comes back with done. It is a lovely demo and an awful thing to hand somebody whose license is attached to the outcome.
01Narrate while it happens
The lead arriving, the gate clearing, the dial, the disclosure, the booking, the note, the follow-up task — each is a row with a timestamp, written as it occurs. If you open the screen mid-call you see the call mid-flight, not a spinner.
- 18:42:07 lead.created · zillow · M. Alvarez
- 18:42:08 gate.check · consent ✓ window ✓ caps ✓ dnc ✓
- 18:42:15 call.dial · +1 512 ··· ··81 · disclosed AI
- 18:45:55 showing.booked · Sat 11:00 · J. Park
- 18:46:02 gate.hold · R. Chen · no consent · counted
02Count the negative space
The last line in that log is the one we care most about. A dial that did not happen is an event. It has a contact, a rule that stopped it, and a lane that is still open — and if the software does not say so, the only record of it is an absence, which nobody audits.
"9 dials Ava did not place" is a screen in the product, not a support ticket.
03Why this is a feature and not a log file
Receipts change what you are willing to delegate. A broker who can see, at any moment, exactly what the AI did and declined to do overnight will let it do considerably more than a broker who has to take it on faith. The transparency is not there to reassure the nervous — it is there so the capable can hand over more.