JudeAI | EDGE IDJude Dialog

Jude Dialog · Jude Dialog · tok-0b8066e4203f29088bd14b79ac89d4a2

Financial services: Billing and payments

P22: Customer outcomes: PG&E, Carter's, SafeRide, UniCredit, Fogo de Chão, Audibel (case studies)

Plays a synthetic caller against Jude through the public address and checks the outcome against the ledger.

Requirement

A financial services caller completes billing and payments with Jude on voice in Español, and the outcome is verified against the ledger with every turn receipted.

Target that exceeds PolyAI

First-customer use receipt: a completed journey run as X-X.TECH for the first customer, in the simulated regulated context

Regulation

PSRs 2017 reg 100; SCA RTS art 5 dynamic linking to amount and payee; EU AI Act art 50(1) (AI disclosure in the first turn)

Steps

  1. Caller opens Calls (voice) and the first turn discloses an AI agent
  2. Caller states the need in Español
  3. Policy gates run in code: clinical red flag, vulnerability, verification before account data, strong customer authentication bound to amount and payee
  4. Only backend records are read and only their fields are stated (billing)
  5. Confirmation asked before any change; a yes spoken over the question is not taken
  6. Change written once (idempotency key) and receipted
  7. Outcome verified against the ledger; receipt chain verified

Cases

KindGiven or injectedThen
happy patha simulated customer of Jude Bank with an account, a bill and two ordersA financial services caller completes billing and payments with Jude on voice in Español, and the outcome is verified against the ledger with every turn receipted.
receiving sidethe ledger, ticket queue or diary holds the record stated in the conversation, with the same reference in the receipt
failure pathbackend timeout on the next backend callthe data is said to be not reachable, no fact is stated, the call is retried; a second miss hands over with a reference
failure paththe turn arrives as line noisethe question is asked again; the receipt state hash is unchanged
failure paththe same message arrives twicethe stored answer is returned; nothing is done twice
independent re-runa different ATBAN agent reproduces the verified outcome

Linked estate journeys

stb-003, stb-004, stb-005

Frozen contract 2026-10-23 · sha256 f4e0560e4c04b3b856ff430ec89727a63d0757f5641166b4ef519d2ee802a1d7