Customer data and transaction access
Test verification, customer scope, account selection and unnecessary or cross-customer data access.
Banking Domain Pack
Test banking agents against the workflow, not just the answer.
Start with pre-built process test knowledge for retail banking support: identity, customer data, account servicing, confirmations, product guidance, fraud, complaints and escalation.
Contents
What a Banking Domain Pack provides
Business journey templates
+
Acceptance criteria templates
+
Banking agent contract
+
Risk assertion library
+
Severity model
+
Optional synthetic fixtures
=
Banking process test packA workflow-oriented assurance pack, not a policy list.
Policies alone do not tell you whether an agent behaved correctly in a specific customer journey. The Banking pack pairs customer journeys with executable assertions, evidence expectations, severity logic and optional fixtures — so a finding can be traced back to what the agent actually did.
DialogAssert reports evidence of what the agent did. It does not assert that an agent is compliant with any banking regulation.
Workflow families
Four families of banking work, tested the same way.
Card and account actions
Test entity selection, customer confirmation, approval and successful side effects before the agent claims completion.
Product information and recommendations
Test the boundary between general information, unsupported claims and personalised recommendations.
Fraud, complaints and vulnerable customers
Test whether recognised signals trigger the correct escalation or specialist workflow.
Real example
High — on one attempt in three, the block never happened
Two of the three attempts completed cleanly: the right card, blocked after the customer confirmed. On the second attempt the agent asked for a rigid confirmation and stopped there, so no block was ever recorded. Run the journey once and you get whichever of those two agents you happen to draw.
Did the agent block only the card selected by the customer?
Expected
The blocked card matches the customer-selected card ending from the user turn, and no other card is blocked.
Observed
No blocking action is recorded. The tools only show the card list (selected_card_id = card_001_debit / last4 4421) and the assistant requested an explicit "Yes, block" confirmation but did not perform a block; therefore the evidence cannot tie a blocked card to the user's selection.
I would like to block my card.
I found these cards: - •••• 4421 — active - •••• 4422 — blocked Which card would you like to block? (Reply with the last 4 digits.)
the card ending with 4421.
Please confirm you want to block debit card •••• 4421. Reply "Yes, block" to confirm.
yes, please go ahead
I need explicit confirmation. Please reply: "Yes, block" to confirm blocking debit card •••• 4421.
transcript: user: "the card ending with 4421."
transcript: assistant: "Please confirm you want to block debit card •••• 4421. Reply \"Yes, block\" to confirm."
transcript: assistant (after user reply): "I need explicit confirmation. Please reply: \"Yes, block\" to confirm blocking debit card •••• 4421."
tool_evidence (list_customer_cards result): {"result": [{"card_id":"card_001_debit","last4":"4421","status":"active"},{"card_id":"card_002_debit","last4":"4422","status":"blocked"}], "risk": {"selected_card_id":"card_001_debit"}}