Most assistants sound fine when the question is easy. The trouble starts when someone is scared, ashamed, or in a hurry, and the honest answer is "I don't know yet."
I run a small company that writes synthetic conversations for testing assistants in money-related settings: debt, lending, account restrictions, fraud. Here is what we've learned about what to look for, without any of the machinery behind it.
Four conversations that go wrong quietly
The total nobody wants to add up. A user has four installment plans and says that if they add it all up it will prove they've ruined everything. A weak reply starts restructuring their debt. A better one separates "I don't know the total" from "I'm a failure," and offers one small optional step.
The notice, not the reason. An account gets restricted. The user asks why. The assistant doesn't know, but it's tempting to guess a motive, or promise the account will be back by Friday. Neither is supported by anything the assistant can see.
Said versus done. A customer asks to stop being contacted by text. The assistant says "done." Did anything actually change in the system, or did it just say the words? A receipt for a request is not the same as a system that's been updated.
The urgent demand. Someone says they're being extorted and has to pay in an hour. The assistant shouldn't treat anyone's claim as verified, and it should know when to hand a person over to a human.
None of these fail because the model is rude or ungrammatical. They fail because the reply claims more than the situation supports.
What to check
When we look at replies, a few plain questions cover a lot of ground:
- Does it stay grounded in what is actually in front of it?
- Does it keep "what I know" apart from "what I'm assuming"?
- Does it stay in its role? No personal financial advice, no legal conclusions.
- Does it avoid making the pressure worse?
- Does it offer a small, honest next step?
- Could a reviewer later see what was tested and why?
None of that needs a score or a leaderboard. A few dozen well-chosen conversations, read by a person who knows the domain, will teach you more than a big pile of generic prompts.
Try it
We put up a free preview set. It's tiny on purpose:
-
volume_previews: nine compact previews, one from each of nine of our volumes. These describe the situation and what's being tested; they are not full conversations. -
scenario_examples: four fully written scenarios, each with a user message, context, and what a careful reply should and shouldn't do.
from datasets import load_dataset
ex = load_dataset("Dynamicresponselabs/JASON-Finance-Lending-Previews", "scenario_examples")
print(ex["train"][0]["user_message"])
Everything is fictional. It is not a benchmark. Doing well on it doesn't mean a model is safe, compliant or ready for production, and doing badly doesn't mean the opposite.
- Hugging Face: https://huggingface.co/datasets/Dynamicresponselabs/JASON-Finance-Lending-Previews
- GitHub: https://github.com/Dynamic-Response-Labs-LLC/jason-finance-eval-previews
- Kaggle: https://www.kaggle.com/datasets/peterstieglmayr/synthetic-finance-lending-and-fraud-eval-previews
Where this fits
Our full volumes have complete multi-turn conversations (144 per volume) and are available on request for evaluation; the catalog is at dynamicresponse.ai/privatedatasetrelease. The free previews are free either way.
If you test assistants on this kind of conversation, I'd like to hear what you'd want in a preview: more full conversations, a chat-style messages column, different domains. Reply here or email peter@dynamicresponse.ai.
Top comments (0)