See who rang and what they wanted
Who rang, and what did they want?
Ask who has called the line lately and what each caller needed, then list the same calls from your terminal.
What you get: every recent call in one table, with who called, what they asked for, and what they were promised, so nothing a caller was told gets lost.
Ask Quox
Section titled “Ask Quox”Ask in your own words:
Who has rung the shop line recently, and what did each of them want? How many of those calls came in to us?
▤ AOCL │ L1 identity complete · allowed · 2ms
▤ AOCL │ L3 policy gate complete · proceed · 12ms
◐ VOICE │ calls ✔ VOICE │ calls │ 5 count, 5 total, 5 calls · 5.4s
⛓ AEE │ envelope opened · ops.tool · voice_calls ok
⛓ AEE │ envelope opened · stream_success
Four of the five recorded calls came in to us. The fifth was an outbound call from the shop. Numbers are masked in the record, so I've used the last digits. When (UTC) Sat 14 Nov, 18:27 Caller Sam (***0111) What they wanted Asked if the winter tyre order had arrived. They were told it lands Friday and the shop will ring when it's in. When (UTC) Sat 14 Nov, 13:12 Caller Unnamed (***0222) What they wanted Asked for Saturday opening hours and was told 9am to 4pm. When (UTC) Fri 13 Nov, 19:02 Caller Unnamed (***0333) What they wanted Hung up after about 20 seconds without speaking to anyone. When (UTC) Tue 10 Nov, 19:22 Caller Jordan (***0444) What they wanted Asked for a quote on a cargo bike for deliveries. They were promised a written quote by Friday. The outbound call was on Thu 12 Nov at 19:42 UTC. We rang Sam (***0111) back to confirm a service booking for Thursday morning. • Unanswered call: The 13 Nov call has an unknown outcome. The record only has one side of the transcript and no answered, missed or voicemail field, so I can't say if anyone picked up. • Cargo bike quote: The quote promised to Jordan was due Friday, which was yesterday. I can't see in this record whether it was sent, so it's worth checking. • Tyre order: Sam was promised a ring when the order arrives, and it's due Friday.
15.9s · 1 tool · 0 approvals
quox.✔ Machine verified against the CLI on 14 Nov 2026 · test report mwgu3k
Quox read your org’s call record and listed each call with the caller and what they wanted. It counted four calls coming in and one going out, masked the phone numbers to their last digits, and picked out the promises worth following up: a quote that was due, and a call back when an order arrives. Where the record could not say whether a short call was answered, it said so instead of guessing.
This run used a test org seeded with five fictional calls to a bike shop. The names and numbers are made up.
Do it yourself
Section titled “Do it yourself”quox voice calls --limit 5TIME DIR PEER SUMMARY TURNS2026-11-14T18:27:45.451Z in ***0111 Sam asked whether the winter tyre order has arrived; told... 32026-11-14T13:12:45.451Z in ***0222 A caller asked for Saturday opening hours; told 9am to 4pm. 22026-11-13T19:02:45.451Z in ***0333 Short call, the caller hung up before speaking to anyone. 12026-11-12T19:42:45.451Z out ***0111 Called Sam back to confirm the service booking for Thursd... 22026-11-10T19:22:45.451Z in ***0444 Jordan asked about a quote for a cargo bike for deliverie... 3 Calls are listed newest first. in is a caller ringing you, out is a call your line placed. --limit takes up to 200; without it you get the latest 50.
What just happened
Section titled “What just happened”Quox read the call record for your active org only. Reading changes nothing, so no approval was needed and no call was placed.
Check it yourself
Section titled “Check it yourself”quox voice insights gives the totals for the same record, so you can check the in and out count against the list.
Nothing to undo: listing calls only reads.
- Count your calls
- Back to Calls you can count