It verifies you, reads your accounts, acts where the bank's policy lets it, and hands anything else to a person
with the context attached. No menu, no hold music.
Why are you calling?
Pick a reason. Each one ends differently, and the agent is not scripted: it reads the
same ledger and the same policy whichever way you put it.
The customer you are calling as, the ledger, and the bank's policy
The bank, the customer and every transaction are fictional. These are the numbers the
agent reads from.
When
Activity
Amount
Status
What the agent may do, and what always goes to a person
How you talk to it
SpeakTypeWatch
When it asks you to verify
Any four digits and any date of birth will do. For example 4417 and March 14, 1986.
More options
Language model
Rules, nothing to downloadQwen2.5-1.5B in your browser · about 1 GB, once
Voice
Agent speaks aloud
This demo uses your browser's own speech engine, and
optionally an open model running on your GPU, so it works without a key. Nothing you say leaves the page except to
your browser's speech service.
What is real here
The conversation state machine, the adaptive turn detection, the tool-call pattern and the shape of the call record are the
product's, taken from its source. The policy boundary is the point of the demo: the agent reads and acts only where the bank
has said it may, and everything else is handed over with the transcript, the intent and the checks already done. In the
product a model understands the caller and phrases the agent; here that is Qwen2.5-1.5B-Instruct on your own GPU, or rules
when it is not loaded. What the agent is allowed to do never depends on the model.
Set up the call→The call→What came back
not connected00:00
What the agent knows
Under the hood: turn detection
Transcription confidence over a rolling window sets how long
the agent waits in silence before it treats a pause as the end of a turn.
Samples
0
Average confidence
·
Trend
unknown
Silence before turn ends
600 ms
Prefix padding
350 ms
Threshold
0.5
Baseline profile until three samples are in.
Set up the call→The call→What came back
What came back.
The call is over; this is the record. Where it led, what the agent did and on what basis, and, if a person is
taking over, the packet they receive so the customer does not start again.
Where this leads
Outcome
·
Handover packet
Actions, with the audit trail
Call summary
How was that call?
Optional, one to five.
The record as stored: the product's call record, filled from this call