Review the request before it runs.
The transcript is editable. Gemma produces a structured plan with an explicit ticket scope and requested activities, validated before any workflow step can execute.
Voice → transcript → reviewed plan
04 / Durable voice workflowsDesigned & built by Himanshu Jha
VOX
A spoken request. A reviewable result.
Turn a voice request into a reviewed support plan, researched reply drafts and a spoken briefing. Approvals and workflow history survive interruptions.
See the build01 / 03 · Product screenshot
What to look for
One instruction. A saved record of the work.
The recorded run preserves the instruction beside its results: 24 fictional tickets triaged, seven labels saved and two drafts prepared. Its provider availability banner describes the capture, not a live entitlement.
Repository capture · historical run · fictional tickets01 / The problemWhy this
Why this
needed building.
Voice makes a task easy to request, but it does not resolve approval, retries or interrupted work. A support assistant needs to preserve what was requested, what ran, and what a person actually approved.
I built a voice-to-plan workflow that triages a demonstration ticket queue, researches guidance, drafts replies and produces a spoken briefing of saved results.
02 / Architecture
Follow the system.
The engineering behind the screens, in three stages.
Keep progress through interruptions.
Mastra runs named activities. Temporal handles durable scheduling and approval signals in the integrated deployment. Saved cursors, cached responses and a ledger support recovery.
Approved plan → activities → saved progress
One plan is not blanket consent.
Each reply has its own approval decision. A spoken briefing reports saved results, with generated audio cached for replay. Customer sends remain simulated in the public demo.
Drafts → individual decisions → briefing
03 / DecisionsThe choices
The choices
that matter.
Separate the two approvals
Approving a plan allows the requested work to run. It does not automatically approve every drafted reply.
Persist before reporting
Saved results and workflow history make a briefing traceable. Recovery uses persisted state rather than asking the model to reconstruct the run.
Name the provider mode
Live provider access is bounded. The rules-only path uses fixed templates and is labeled; configured provider failures do not silently become local generation.
04 / Evidence
Inspect it for yourself.
Hosted demonstration with fictional tickets; customer sends are simulated.
Scope & limits
Explore the repository The judge demo contains fictional tickets and simulated customer sends. It is not connected to a real customer inbox. Live passes are limited; the site shows current availability. This case study does not consume a live pass.
The voice interface is the entry point. Durable state and explicit approval make the workflow dependable.
Next build / Local intelligenceOmniDev