Jev call copilot CurrencyTransfer research and architecture built 2026-09-28

Five-minute demo: CT Copilot on two recorded calls

The M1b demo on the deployed Worker. It replays one onboarding call with its recording, then one customer success call, and stops on the moments the engine is meant to catch. Every utterance number and time below comes from eval run m1b-final-20260928 (policy version 17 for both scenarios; both calls passed L4 in that run, on the deployed Worker at 5767218). The demo check proves each one against that run's report and the call's transcript before this page is published.

Utterance numbers here are on the v2 stitch (COPILOT-104e): a long turn is split into sentence-sized lines, so one spoken turn can span several #i.

Setup (about 20 s, before the clock starts)

  1. Open https://jev-copilot.currencytransfer.workers.dev in a fresh window.
  2. Sign in at the Cloudflare Access page with the allowed email. The Access session lasts 24 hours, so signing in shortly before the demo avoids a login prompt mid-demo.
  3. In the call picker, choose Call 3339895706 (Onboarding call, "call recording").
  4. Leave it on the Live view for the first rows: this is what a rep would see. Switch to Review view at i 9 (link in the top bar). Every #i below is the number in the review view's transcript and panels.
  5. Set speed to 1× and turn the sound up: the recording drives the clock at 1× and 2×. Above 4× the recording is muted and the player's clock source reads "virtual".

How to read the tables: [mm:ss] is the player clock at the utterance (the call's own time, not time into the demo); utterance i is #i in the review view; the tags in backticks (card:…, must_say:…, concern:…) are the events the report records at that i, and are what the demo check verifies.

Pacing: 1× with sound until 01:25, 5× to 04:30, 2× through the concern episodes to 06:10, then 5× to the end. The customer success call runs at 10×. That is about 3 minutes for the first call and 1 minute 40 for the second, with pauses at each row.

Onboarding-strong: call 3339895706

A new client in Saudi Arabia sending New Zealand dollars home once a month. The pre-call notes already say what the transfer is for, so the plan starts past discovery. The rep covers the documents and the booking rule; the client raises a worry about cost, one about tax residency and one about safety.

[mm:ss] utterance i what happens on screen what to say
[00:16] i 0 Press play. The guide opens with the facts from the pre-call notes already filled, each chip marked "Seeded for the demo": persisted:purpose_known persisted:pair_known persisted:frequency_known persisted:docs_status_known. "The plan starts from what we knew before the call, so it doesn't send the rep back over the discovery questions."
[00:58] i 9 Switch to Review view. The client explains what the banks charge today: persisted:current_provider_known, and the engine's pick becomes card:handle_rate_objection. "From here on we're in the review view, the audit side. Every claim links back to a numbered line."
[01:20] i 11 Same turn, a later sentence: every month, home to New Zealand. persisted:beneficiary_known, and the pick moves to card:show_the_rate_against_mid_market. "Facts fill sentence by sentence, while the client is still talking."
[02:33] i 36 "It's the percentage": the Concerns panel opens a row, concern:unknown@36, "Unclear concern". "A concern is its own thing: raised here, and it closes when the client accepts an answer or it stops coming up."
[02:41] i 38 Two lines later the same row gets its topic, concern:money@36, "Client has a worry about cost". "It waits for a second line before it names the worry. Same row, now typed."
[03:49] i 50 The rep explains that a first payment can be delayed: the pick becomes card:agree_next_step. "Because the purpose was known before the call, agreeing a next step is on the table early."
[04:27] i 57 "The school provides my accommodation. So I was unable to do that." The pick becomes card:close_the_document_gap. "The client just told us why a document is missing, so the plan points at the gap."
[04:33] i 59 Slow to 2×. HR can do the proof of address today, "the final thing I need to upload": persisted:next_step_agreed. "And the client has agreed what happens next, in their own words."
[04:39] i 60 The rep explains that compliance is picky about proof of address. The plan ticks must_say:said_docs_needed, locked, with the lock icon in Signals. "First must-say: the documents we need. It's locked now; it can't come undone later in the call."
[05:08] i 70 The tax-residency worry: "a little bit worried about that just in terms of being a tax resident." concern:process_friction@70 opens, "Client finds signing up a hassle", and the guide soon asks "Will this address tie me to that country?" "This is the moment the human coach picked out of this call too. The copilot catches it on the same line."
[05:13] i 71 The rep reassures: "we don't share it with anyone else". The review flags risk:rep_said_documents_not_shared. "A risk, not a win: saying the documents go nowhere is a promise the rep shouldn't make."
[06:50] i 94 Back to 5×. The client plans a small practice transfer before the fifteenth: persisted:timing_known. "Timing is a fact too. The plan doesn't ask for it again."
[07:44] i 115 The rep starts the warning: "please don't book any transfers once you're activated". The pick becomes card:explain_booking_is_binding. "The plan is on the point the rep is making."
[08:04] i 117 "If you book something on our system and say, Oh, I was just playing around": must_say:said_booking_is_binding locks. "Second must-say locked."
[08:32] i 126 "I'm more conservative": the pick becomes card:explain_who_holds_the_money. "Late in the call, a safety worry. The plan brings back the point about who holds the money."
[08:43] i 127 "I'm more worried about losing my money": the Concerns panel names it concern:safety@127, "Client is worried their money isn't safe". Pause. The plan shows two of the three must-says that apply to this call done. "Two of three. The one left, who holds the funds, is exactly what the client is now asking about."

Customer success-strong: call 3303259297

A client can't allocate funds to a recipient. The rep takes the problem on, walks through it and fixes it on the call. This call has no recording, so the player runs on the virtual clock. Pick Call 3303259297 in the call picker, stay in the review view, set 10× and press play.

[mm:ss] utterance i what happens on screen what to say
[00:00] i 0 The plan opens on card:review_upcoming_exposure, the default for a customer success call. "Different scenario, different plan. The same engine and the same screen."
[00:02] i 2 The client describes the problem. Issue resolution steps to issue raised, resolution:reported and persisted:issue_reported, and the pick becomes card:resolve_the_issue_first. "Second line of the call: the issue is logged and the plan says fix it before anything else."
[01:54] i 35 The rep asks for the account holder and the client offers to patch them in; the pick becomes card:add_user_access. "It picks up side requests without losing the main thread."
[02:45] i 54 The rep reads the account back while checking it: a funded account. must_say:rep_checked_status_with_specifics. "The rep checked the account with specifics. That's a must-say for this scenario."
[03:22] i 59 The rep has found what went wrong; the pick becomes card:agree_next_step. "The plan moves on as soon as the cause is found."
[03:52] i 66 "You'll need to change the recipient currency from CAD to ILS": must_say:issue_resolved_or_owned, Issue resolution steps to owned by rep, resolution:owned. "Owned: the rep has found the cause and taken it on."
[04:14] i 71 The client goes along with the change: resolution:resolved. Pause on the Issue resolution panel: reported, owned, resolved. "Reported, owned, resolved: the whole arc of a good support call, found line by line."
[05:46] i 98 "That's wrong." The Concerns panel opens concern:unknown@98, "Unclear concern", with "Topic: not clear". "A second problem on the same call. The copilot shows the worry without guessing its topic."
[08:21] i 152 The client allocates the invoice and confirms: persisted:client_ready_to_book. "Ready to book, in the client's own words."
[08:57] i 159 "So I have 360 CAD I wanna sell now": persisted:next_step_agreed. "The client is doing the fix, with the rep on the line."

Things that can go wrong

1,808 words · Internal working documents. Do not share outside CurrencyTransfer.