December 3rd, 2024

Launch HN: Vocera (YC F24) – Testing and Observability for Voice AI

Vocera AI automates testing and monitoring of AI voice agents, addressing manual testing inefficiencies by simulating diverse personas and generating scenarios, providing real-time insights and detailed analytics for developers.

ExcitementConcernCuriosity
Launch HN: Vocera (YC F24) – Testing and Observability for Voice AI

Vocera AI, founded by Shashij, Sidhant, and Tarush, is a platform designed to automate the testing and monitoring of AI voice agents. The founders, who previously worked on voice agents in healthcare, encountered significant challenges with manual testing, which was time-consuming and prone to errors. They faced difficulties in demonstrating reliability to customers, covering edge cases, simulating diverse conversations, and monitoring production calls effectively. To address these issues, Vocera automates the simulation of real personas and generates a variety of testing scenarios based on prompts and call scripts. This allows for comprehensive monitoring of production calls and provides real-time insights into the performance of voice agents. The platform not only automates evaluation but also generates scenarios and metrics automatically, saving developers time. Users can still define scenarios and metrics manually if desired. Vocera offers detailed analytics on agent performance, reducing the need for developers to listen to all call recordings. The founders invite feedback and discussions from those interested in the challenges of Voice AI or who are building voice agents.

- Vocera AI automates testing and monitoring of AI voice agents.

- The platform addresses challenges like manual testing inefficiencies and reliability demonstration.

- It simulates diverse personas and generates testing scenarios automatically.

- Developers receive real-time performance insights and detailed analytics.

- The founders seek feedback and discussions on Voice AI challenges.

AI: What people are saying
The comments on the Vocera AI launch reflect a mix of excitement and concern regarding the product's implications and market positioning.
  • Many commenters express enthusiasm for the launch and recognize the value of automated testing for voice agents.
  • There are questions about the demand for testing tools in a niche market where many developers use existing SDKs with built-in observability.
  • Concerns arise about the potential confusion with the existing healthcare communication platform named Vocera, suggesting a need for a name change.
  • Users inquire about customization options for scenario generation and handling sensitive data in production calls.
  • Some commenters express interest in trying the product without going through traditional sales processes.
Link Icon 17 comments
By @Areibman - 5 months
Congrats on the launch!

Given the size of the niche (developers building voice agents), do you find there's a lot of demand for testing and observability? From my anecdata, many of the voice AI agent builders are using SDKs and builder tools (Voiceflow, Vapi, Bland, Vocode, etc). Observability is usually already baked-in pattern with these SDKs (testing I'm not so sure of).

One conversation I had with a voice agent builder: "Our product is complex enough where external testing tools don't make sense. And we know when things are not working because we have close relationships with power users and companies." Whose problem are you solving?

Your tool looks very powerful, but might the broader opportunity be just to use your evals to roll out the best voice agents yourself?

By @ghodoussikian - 5 months
Congratulations on the launch! This looks like a really powerful framework.

One trend I’ve noticed is there’s a really heavy focus on pre-deploy tests which makes a lot of sense. But one big gap is the lack of ability to surface the scenarios that you don’t know are even occurring after deployment. These are the scenarios that human agents are great at handling and ai agents often fall flat: in a sales context that can have a direct impact on a customers bottom line.

I think rather than attempting to deploy a perfect agent, having a mechanism to surface issues would lend much more peace of mind when launching ai voice agents. Would be happy to chat more if additional context/real world examples would be helpful. Congratulations again on the launch!

Background: have worked on contact center unstructured analytics for several years.

By @BrandiATMuhkuh - 5 months
Congrats on the launch! I can definitely see the value in that.

I've been working with auto-generated content for the past 8 years (both algorithmic and LLM-based). One of the biggest challenges is detecting and preventing regressions after "improving" the prompt, algorithm, or model.

Just yesterday, I deployed a voice agent (OpenAI + Twilio), and it's clear that there are countless scenarios where the agent might not perform as expected. For example, if you ask the agent to speak in German, but your tool uses call names or returns data in English, the agent might suddenly switch to speaking English.

Overall, I believe voice agents will primarily be used and developed by SMEs, but they often lack the time or expertise to account for all these edge cases.

Btw: here is the number agent. sorry it's in German: +43732 350011

By @tabarnacle - 5 months
I was able to easily flip the script on the return scenario to convince the rep that they were the one calling me to return - and then flipped it again. The quality of the voice was great, though.
By @shreyapathak - 5 months
Congrats on the launch!

Great to see the focus on robust and exhaustive evaluations. With large-scale usage of products, everything that can go wrong usually does so such evals will go a long way!

How do you intend to grow the product?

By @ishantarunesh - 5 months
I run an AI services company and we've built voice bots for multiple clients. Is there a way for us to evaluate the agents on Vocera (these are custom builds not VAPI or Synthflow etc)
By @AkashKaStudio - 5 months
Do you have a flow/customization where the customer asks to wait for X seconds? And is this just telephony over Websocket or is a WebRTC stream supported as well?
By @suyashb613 - 5 months
How do you handle sensitive data in production calls, especially for industries like healthcare and finance?
By @shyam_manchhani - 5 months
Can users customize scenario generation to focus on specific conversational intents or user behaviors?
By @savy91 - 5 months
Is there any way to sign up and try this without going through the sales call/demo?
By @filipeisho - 5 months
This is super dope! Are you looking to hire? Your product made me super excited.
By @nextworddev - 5 months
This market will be killed by Twilio soon
By @Aurornis - 5 months
> We were working on voice agents in healthcare

Having some experience with the healthcare industry, seeing the name Vocera here is incredibly confusing.

Vocera is a very common communication platform and set of devices used in hospitals: https://vocera.stryker.com/s/product-hub/vocera-smartbadge These things are everywhere in healthcare already. If someone came to me and suggested using “Vocera” for a healthcare related tech thing, my mind would assume it’s the Stryker product. It’s that common.

So unfortunately I’d recommend a name change as a high priority. Dealing with healthcare tech is difficult enough, but using the same name as a very popular and established healthcare tech product is going to be an unnecessary obstacle in getting traction. Not to mention that Stryker’s Vocera division will have some things to say about this.

By @rahulgoel - 5 months
Congrats on the launch. For a sec, I thought this was related to the healthcare comms firm owned by Stryker.

https://www.stryker.com/us/en/portfolios/medical-surgical-eq...

By @doubleg72 - 5 months
Vocera is a company that already exists in healthcare and you have some potential legal issues with keeping this name.