Cekura - The self-improvement loop for voice agents

Cekura is the testing, observability, and self-improvement platform for production voice and chat AI agents. It simulates thousands of scenarios, catches failures, diagnoses the root cause, rewrites prompts and config, then re-validates with a full regression sweep. Unlike tools that hand failures back to your team, Cekura closes the loop by fixing the agent itself and proving the fix holds without overfitting.

Add a comment

Replies

Best

How does Cekura evaluate more nuanced qualities like tone, empathy, or conversational flow, beyond just accuracy or task completion?

 Yes , beyond accuracy/task-completion, we have built-in metrics for exactly that: CSAT and Sentiment score the caller's tone and satisfaction, Verbosity and Unnecessary Repetition flag conversational flow issues like over-explaining or re-confirming the same thing, and Voice Tone + Clarity looks at delivery quality from the audio itself. For anything more specific to your agent's context, you can also define a custom LLM-judge metric

Thanks — the GitHub Actions path is the answer to that question. The follow-up I'd have is whether the infra regression suite runs against a live agent clone or replays recorded sessions, because customer-support agents with integration state tend to behave differently on replay versus a live environment.

 Hi Hazy, every Infrastructure Suite case is a real simulated call against a real running agent.

That is the answer to the question - replay-based evals have a way of missing failures that only show up with live state, so real simulated calls against a running agent is the right approach. Good to know the suite is doing actual call simulation rather than matching against recorded outputs.

Voice agents fail in ways text evals never catch — interruptions, latency, someone talking over the bot. The "loop" framing is the right one: testing voice once at build time is basically useless. Would love to know how many simulated calls it takes before the improvements show up.

 Fair question , it's less about a fixed number of calls and more about iterations: the loop diagnoses, fixes, and re-validates until the full evaluator set passes. We've seen quite a lot of improvement starting from just 1-2 rounds itself

Congrats on the launch! Really like that you’re focusing on proving fixes instead of just identifying failures. One thing I’m curious about: how do you decide when a suggested fix is reliable enough to recommend versus flagging it for manual review?

 Hi Ujjval the loop run a suggested fix multiple times to see if the fix consistently resolves the failure mode. If the loop isn't sure about anything then it hands to the user for manual review.

Love seeing more attention on production reliability for voice AI. The regression validation especially stood out. Curious whether Cekura can prioritize issues by business impact (for example, failed payments vs. minor conversation hiccups) or if everything is treated equally.

 Great question. You can easily prioritize issues on which to self-improve your agent on Cekura. You can create custom metrics depending on your use case and can attach them to scenarios on which you are improving your agent and the self-improvement loop will consider the failure points on the attached metrics to improve your agent upon.

Love that this closes the loop instead of dumping another list of flagged calls on a human. The rule that it has to reproduce a bug before it is allowed to fix it feels very sane. For a team running a voice agent in something sensitive like healthcare intake, can you control which kinds of fixes it applies on its own and which ones need sign-off first?

 Hi Dogan, for every issue the loop suggests a fix and verifies the fix across multiple runs to see if it is consistent but every change today requires your approval before it is applied. We are already working on adding a control which can enable the loop to automatically apply fixes for issues that are not critical and don't require manual review.

Let's go team !! So excited for what's ahead.

Let's go!!

Voice AI quality is surprisingly difficult to measure consistently. I like that this goes beyond transcript evaluation and looks at things like interruptions, latency, and delivery quality. That's usually where real production issues show up

Congratulations. And happy product launch.

 Thanks brother!