Field note 01 · Latency
The call that changed our latency budget
Written the way a person would say it out loud. Direct, grounded, human.
We used to think voice AI was a model problem. Then we watched a patient call a hospital, hear nothing for a full second, and hang up. Not because the model was wrong — because it was slow. The caller didn't judge the answer; they judged the silence before it.
That's when we stopped measuring inference time and started measuring the whole thing: from the moment a call connects to the first syllable the caller hears. That number — the gap that doesn't exist — became our product. 350 ms on Cloud, 355 ms on Resident, both measured end-to-end, method published.
Callers judge you in the first second of silence. We built Anuvo so that second never happens.
Field note 02 · Residency
Why the audio never leaves
The argument, in answer shape.
Cloud voice AI made agents possible, and it also made a quiet promise it can't keep: that sending every word of every patient call to somebody else's servers, forever, at a per-minute price, is fine.
For a hospital, a lab or a law firm it isn't fine. Their data is regulated, their callers are vulnerable, and their compliance team gets a vote. So the businesses that need a voice agent the most were locked out of the category — or worse, carrying a risk nobody had priced.
That is why Resident exists. The entire stack — recognition, orchestration, synthesis, the audit log — runs inside your building. No third-party model dependency. No per-minute fee. No audio leaving your network, ever. Residency and speed are not a trade-off; 355 ms measured, inside your four walls.
Field note 03 · Category
"Resident Voice AI" is not a category. Yet.
Why we're naming the shelf we want to own.
The "AI voice agent" category is crowded, well funded, and priced downward by companies with more capital than sense. Entering it means competing on price against people who can lose money longer than you can earn it.
So we defined a category we are already the only credible occupant of: Resident Voice AI. The word does double duty — the agent is resident on your infrastructure, and in a hospital, the resident is the one who is always there. The agent that is always there, on your floor, with your data.
We didn't invent the need. Hospitals miss calls all day because the front desk is one human deep, and their compliance rules won't let the fix live in someone else's cloud. We built the fix that fits the rule. The category follows the customer.
Next instalment? The naming story — why a Sanskrit prefix, an open vowel and a V travelled warm → daring → solid in three syllables. Subscribe by calling the demo line and asking for it.
