New here?
The Quickstart connects an agent and gets a scored call in about five minutes.
Want the vocabulary first?
The glossary defines every term used across the product.
1. Connecting your agent
The only job of an integration is to get the finished call to Tuner. Once Tuner has it, everything on this page happens on Tuner’s side: transcript, per-turn timing, classification, evals, red flags, and alerts. Which route you take depends only on what you build on, and every route produces the same result once the call lands.
Worth knowing: for monitoring, traffic goes one way, from your stack to Tuner over HTTPS. Tuner needs no route into your network, so a fully self-hosted agent connects the same way a managed one does.
2. Seeing what happened on a call
Worth knowing: the depth of the latency breakdown depends on how you connected. Platforms that hand over a finished transcript can only tell you a call was slow. The SDKs record each stage as it happens, which is what turns “slow” into “the LLM stage added 900ms on turn four”.
3. Judging every call
This is where you tell Tuner what a good call looks like. Everything defined here runs on production calls and simulated calls alike.
Worth knowing: an eval judge is not limited to the words in the transcript. Because it can read the tool calls and results, and the agent’s own instructions, an eval can fact-check the agent instead of only rating its tone. “The agent quoted a delivery time the tool never returned” is a checkable failure, not an opinion. See What an eval actually judges.
Evals also run in whatever language the call happened in, so a multilingual agent needs one set of evals rather than one per language.
4. Testing before your customers do
Call Simulation places real voice calls against your agent and scores them with the evals you already configured. It is included from the Builder plan upward. Simulation is temporarily unavailable for Dograh agents, which can still capture and analyze real calls.5. Configuring, diagnosing, and automating
6. Data and compliance controls
Where your agent runs and where Tuner runs are separate questions. Your agent can be entirely self-hosted on any plan. Tuner itself runs as a hosted cloud service, with on-premise deployment available on Enterprise, alongside SOC 2 and HIPAA compliance, custom integrations, and a DPA on request. See the FAQ for both.
What makes Tuner different
Useful when you are comparing tools, or deciding whether you need more than one.One configuration for testing and production
One configuration for testing and production
A testing tool and a monitoring tool that know nothing about each other means writing the same criteria twice and watching the two definitions drift apart. In Tuner the evals, outcomes, and intents you define are used in both places. A behaviour you catch in simulation is scored the same way when it reaches production, and a failure you discover in production becomes a pressure test on the next run without any extra setup.
Latency you can attribute, not just measure
Latency you can attribute, not just measure
A call duration tells you a call was slow. Tuner’s SDK integrations record end of utterance, STT, LLM, TTS, and time to first byte per turn, so you can point at the stage that cost you the second. That level of detail is not available from a platform that only hands over a finished transcript, which is why the SDK path captures more than the webhook path.
Evals that check facts, not just tone
Evals that check facts, not just tone
An eval judge can be given the agent’s system prompt, its tools, its workflow, and the actual tool calls and results from the call. That turns evaluation into something checkable: did the required tool really run, were its arguments right, did the agent report back what the tool actually returned, did it follow the prompt it was given. Tone scoring is still there, it is just not the only thing an eval can do.
Real voice calls in both directions
Real voice calls in both directions
Simulation places actual voice calls over SIP, inbound or outbound, rather than exchanging text with your agent’s logic. Your telephony, your endpointing, your TTS, and your latency are all in the loop, so what you are testing is the thing your customers will hear.
No lock-in to one voice platform
No lock-in to one voice platform
Managed platforms, self-hosted frameworks, and fully custom stacks all connect. If you switch from a managed platform to your own infrastructure, your evals, history, and dashboards come with you rather than being left behind in a vendor’s console.
Configuration and diagnosis in natural language
Configuration and diagnosis in natural language
The MCP server both reads and writes. It is not a chat interface over your metrics. You can ask what is failing across every call, get the root cause, and have the fix applied to the agent’s configuration in the same conversation.
You pay per analysis
You pay per analysis
Credits are spent on the analyses you switch on, not on a seat count. An agent with three evals costs less per call than one with fifteen, and alerts and red flags cost nothing at all. Plans set your monthly credit allowance and feature access, starting free on Pay as You Go with 300 credits and no commitment. Current rates and plan contents are on the pricing page.
Where to go next
Quickstart
Connect an agent and get a scored call.
Call Simulation
Test before launch and after every change.
Evals and guardrails
How calls are judged, and what the judge can see.
Monitoring routine
What to check, and how often, once calls are flowing.