r/vapiai

Vapi raised $50M Series B and immediately rebuilt the dashboard, here's what actually changed
▲ 9 r/vapiai+1 crossposts

Vapi raised $50M Series B and immediately rebuilt the dashboard, here's what actually changed

So Vapi closed a $50M Series B from Peak XV, they've now done 1 billion calls, and they're powering Ring, Intuit, ServiceTitan. Cool. But the second you log in this week you can see where part of that money went, because the agent builder looks completely different.

Spent the last few days rebuilding agents on it. Here's what's worth knowing if you haven't logged in yet:

The wins:

  • Logs are now ON the agent page. FINALLY. No more bouncing to Observe > Logs > filter by assistant just to check what your agent did on the last call. This alone saves me probably 50 clicks a day.
  • Transcriber, model and voice are now top-level on the assistant page. Click into any of them and a sidebar opens with everything (provider, language, fallback, denoising, smart endpointing). Way less scrolling.
  • Fallbacks are first-class citizens now. You can set fallback transcriber, model AND voice from the same panel. Pro tip if you're new: never set the fallback to the same provider as the primary. If OpenAI goes down, your fallback to OpenAI also goes down. Pick a different vendor.
  • Structured outputs and scorecards have replaced the old summary, success eval, and structured data fields (those are deprecated now). Structured outputs are now created globally and assigned to assistants, same model as tools. Build once, attach everywhere.
  • Monitors are (fairly) new. Set them up to catch things like transcriber request failures across all assistants, with thresholds and Slack/email notifications. Production hygiene baked in.

The small stuff that still annoys me:

  • End call is no longer a toggle, you have to create an End Call tool and assign it. Fine once you know, but I broke an agent the first time because I assumed it carried over.
  • The old layout toggle is hidden under the three dots top right. If you panic on first login, that's your escape hatch.

My humble opinion: the rebrand especially, but also the new UI feel less developer-first and more enterprise-pitchable. Make of that what you will. I think it's net positive, the old dashboard had real friction once you scaled past a couple of agents.

Made a full walkthrough on YouTube going through every tab if you want the visual version.

What's been your experience so far? Anyone hit weirdness on the migration?

u/ApprehensiveUnion288 — 3 days ago
▲ 6 r/vapiai

Vapi just raised a $50M Series B. Here’s what we’re investing in for voice AI builders

Today we announced Vapi’s $50M Series B.

Over 1 million developers have built on Vapi so far and together they’ve created nearly 3 million voice agents and powered more than 1 billion calls.

This is only possible thanks to everyone building with us from side projects to production deployments handling real customer conversations every day.

This next chapter means we can invest even harder into the things builders care about most:

tighter latency under load
deeper reliability + stronger guardrails
better tooling for shipping agents at scale

Voice AI still feels very early, and it’s exciting seeing how quickly the space is evolving.

We’re planning to spend more time sharing updates, experiments, launches, and community projects here again.

If you want to read more about the raise and what we’re building toward, Jordan shared more here

u/Vapi-AI — 10 days ago
▲ 11 r/vapiai+4 crossposts

Most “HIPAA-compliant” voice agent stacks stop at:
- “Our cloud signs a BAA”
- “Our STT/TTS/LLM vendors sign BAAs”
- “We encrypt in transit + at rest”

That’s necessary, but not sufficient once real PHI hits production agents.

I wrote up a short post on the gaps we keep seeing when teams assume “BAA = compliant” for AI voice agents (blog link in comments)

Quick summary of the problem areas:

- Fragmented audit trail across telephony, STT/TTS, LLM, tools, dashboards.
- LLMs treated as an unbounded PHI sink via prompts, tools, and memory.
- BAA coverage that breaks somewhere in the vendor/subprocessor chain.
- Behavioral leaks (what the agent *says* on calls) even when infra looks secure.

With Masker.dev, I’m treating PHI minimization as a first-class design constraint: sit between your voice platform and LLM, detect and redact PHI, swap in surrogates so the agent stays coherent, and keep an audit log of every redaction.

Curious how folks here are handling PHI minimization and auditability across multi-vendor voice stacks. Happy to jam in comments or DMs.

reddit.com
u/Away_Pirate_1186 — 12 days ago