Agentic IVR · voice first · early access
Zephoriam records every call as an append-only ledger of typed events — every prompt, every caller utterance, every routing decision, every piece of evidence the AI consulted — replayable end to end, so QA, compliance and coaching finally read the same record.
Pre-launch, built by a contact-center consultant who got tired of asking vendors questions they couldn't answer. No customers yet — you would be early, and we would rather say that than fake a logo wall.
Why it exists
Zephoriam began as a short list of things a contact-center consultant kept asking IVR vendors on discovery calls, and kept getting slides back instead of answers.
Every platform reports containment. Almost none can tell you that a caller heard the wrong branch of the menu, said “representative” twice, got no-matched, and hung up forty seconds in — let alone let you watch it happen again. Drop-out gets inferred from aggregates, weeks later, by whoever is best at spreadsheets.
Zephoriam's answer: the drop-out is an event, in sequence, sitting next to the prompt that preceded it and the recognition result that caused it. You replay the call instead of reconstructing it.
Most third-party voice agents bolt on by blind-transferring to an external phone number. From your side the call simply leaves the building: no events, no transcript, no evidence trail, no way to reconcile what the agent told the caller with what your systems know. It comes back as a line item on someone else's dashboard.
Zephoriam's answer: the agent is a node inside your flow, not a phone number. Its turns are events on the same ledger as every prompt and every transfer.
When a caller insists they were quoted a price, when a supervisor coaches on a call the bot handled first, when someone asks how a disclosure was delivered — “the model generated it” is not an answer, and a recording with no reasoning attached is barely better. QA, compliance and coaching each end up with their own partial export.
Zephoriam's answer: every agent turn carries the evidence it was permitted to use, by reference. What was said and why it was said live in one record that all three teams read.
How it works
Three architectural commitments. They are the reason the rest of the product behaves the way it does.
one append-only stream per call
Typed events — call.started, agent.said, caller.said, intent.classified, branch.taken, handoff.requested. Nothing is ever overwritten: a correction is a new event, so the record can gain detail but can never quietly change its story. Every screen is a replay of those events, which is why QA, compliance and coaching stop arguing about whose export is right.
the model selects; it never invents
At an agentic node the model chooses among the branches the flow declares, by index, against a schema — so it cannot route a caller to a destination that doesn't exist. When it states a policy, a price or an account fact, that fact came back from retrieval and is quoted by reference. No retrieved evidence, no claim. The interesting part is what it makes impossible.
the machine drafts; the person decides
Sensitive actions — a credit, a refund, an exception — stop for a human approval that is itself a recorded event. So do the platform's own improvement proposals: every request the flow couldn't handle is captured in the caller's own words, mined for patterns, and turned into a drafted new branch that a human approves or rejects. The system gets faster. The gate does not move.
A transfer to a person is a first-class result with a packet attached: the transcript, the classified intent, the evidence consulted, and what the automation already tried. Design for the handoff and it stops being the thing you hide from the report. A contained call that left the caller furious is a failure that the containment number scores as a win.
Every request the flow had no branch for is kept verbatim, as evidence. Those become drafted proposals — a new branch, with the calls that justify it cited by reference. A human approves every change before it reaches a live flow, and the approval is on the ledger like everything else.
Honest status
Most of this page describes architecture that exists and is under test. Here is the line between what is built, what is being built now, and what simply is not true yet.
Early access means small numbers of design partners, direct access to the build, and a real say in what the first flows look like.
Both go to the founder — a contact-center consultant, not a sales team.