161–170 of 182 posts
I'm assuming you're targeting this mainly at enterprises and business use-cases such as callcenters, but are you planning to make this usable for personal use cases as well? For example, having a bot to bounce ideas off while coding. Pretty much "just" the TTS / STT layer to talk to my finetuned LLM in a natural manner while you handle interruptions and such. I think the main issue right now for personal use would be…
The demo is nice but it makes me wonder: why would a company have a fully automated voice line rather than a booking interface? As a customer I'm never happy to call a company to make a reservation. I'd be extra annoyed if an AI picked up and I had to go through the motions of a conversation instead of doing two clicks in a Web UI.
Yes, for booking appointments, a simple interface might do the trick. However, we've seen many excellent use cases of our API that prevent repetitive tasks and help companies save money, like AI logistics assistants, pre-surgery data collection, AI tutor and AI therapists. I believe the future will bring even more voice interface applications. Imagine not having to navigate complex UIs; you could easily book a flight…
However, I agree with others. What I don't want to do is talk to LLMs for customer support. For that, I always want to talk to a real person. It would be infuriating for an LLM to pick up when calling a business.
Awesome product. We would love to use this for our app, but it wouldn't make sense economically. At $0.10 per minute it would cost significantly more than our existing TTS and SST solution. We've manually added a VAD and will have to add a way of handling interruption. All-in-all it roughly costs us $0.01 per minute and we just can't afford a 10X increase in costs. Guessing you guys have found a use case with higher…
Thanks. We get it—the current pricing doesn't fit everyone's budget. We will try to look into ways to roll out a more affordable option later.
What's the difference between your product and Gridspace's? I get the sense that your offering is more developer-focused, but I'm curious if there are any technical differences.
I believe Gridspace is an IVR solution, not one based on LLM. It's challenging to ask questions that deviate from the initial settings. We're using LLM to generate responses, which makes the conversation smoother.