Where is NS-518206? It's been a week.
It shipped Monday with UPS and arrives Thursday.
Fine.
Automated testing for AI customer service and sales agents
Voxli plays your customers in full conversations with your agent. You see what a model switch or a prompt edit changed, and whether a new client's agent is ready to go live.
Works with any model your agent runs on
“We had our development team spend three months building internal tools to handle what Voxli does out-of-the-box.”
Voxli's founders built ftrack and grew it from zero to millions in yearly revenue before selling it. ftrack won an Academy Award in 2021. Meet the founders
Before Voxli
After a model switch, a prompt edit, or a new client's setup, your agent still answers every question, and nothing looks wrong. A list of one-off test questions never gets far enough to see the difference.
It promises a delivery date that your order system never returned.
Five messages in, it has forgotten what the customer asked for.
The customer only asks about a refund. It starts one anyway.
Your brand's warm voice turns stiff and formal.
It writes the tests, runs the conversations, and shows you where one went wrong.
We set up the connection with you. No Voxli code goes inside your agent.
Describe a test in plain English, or let Voxli talk to your agent and write the tests itself. You can also turn a real customer conversation into one.
Each test is a whole conversation. The customer can be impatient, confused, or combative, and writes in their own language.
Voxli explains each failure and points to the messages that caused it. You find the problem without reading the full transcript.
You tuned your prompts and tools to the model you use today. Another model, even a stronger one, can respond to them differently and offer a customer a discount nobody approved. Run the same tests several times on the old model and the new one, and see what got better and what got worse in each scenario.
Use cases
Start from the change you are about to make.
Run the old model and the new one on the same suite and see exactly what changed.
Know when a change makes your agent invent facts, before a customer acts on one.
Turn the use cases, brand rules, and safety limits you agreed on into a pre-launch suite.
Run the whole suite on every change, on a schedule or in CI, and get alerted when a flow breaks.
Check that the agent calls the right tool with the right arguments and reports what it actually did.
Import the conversation that went wrong, replay it until the failure shows itself, and keep it as a test.
We ran every model at its vendor's default settings and tuned nothing. Use the results to pick a few models to try, then run your own tests on those.
For developers
Connect Claude Code, Cursor, or any MCP client to your Voxli workspace. Your assistant reads the failing run, applies a fix, and runs the tests again.
More on MCPConnect your workspace
claude mcp add voxli --transport http https://api.voxli.io/mcp Then ask your assistant
Look up the latest run in Voxli and analyze why it failed.
Book 15 minutes with Mattias or Björn. We'll show you how Voxli would test that change for your agent.
After the call we set up a workspace connected to your agent, generate a first set of scenarios from it, and hand it over. You run them, read the results, and add your own. Everything in the workspace carries over if you continue.
How pricing works