Self-guided product walkthrough
Follow one employee from the owner’s brief to sourced work, an exact held reply, a correction, and the next similar case. No scheduled call, no customer theatre, and no fake interactive controls.
Fictional sample, real product states
The names and enquiry words are illustrative. The Chat, source, evidence, Review, Training, and approval states are the real product journey—not a customer story or a live simulation.
What ends here
The walkthrough ends with held work. Nothing in the sample was sent, and it does not claim unattended dispatch or a result from a real customer.
One employee · one job · six visible states
Read straight down. Every step stays with the same employee, and every risky effect remains concrete enough for the owner to judge.
The owner describes one job, the facts to use, and the boundary for risky work in the same Chat where they will later correct it.
“Handle new service enquiries. Check our service area and opening rules, flag urgent work, and draft replies for me to approve.”
A forwarded email, webhook, or schedule can wake the employee. This walkthrough uses fictional enquiry text so no customer data is presented as proof.
“Could you help with an urgent repair near Bristol tomorrow? We need to know whether you cover our area.”
The employee applies the standing rules, keeps unknowns unknown, and records the evidence behind its decision instead of inventing an answer.
“Service area: matched · Urgency: high · Tomorrow's availability: not verified · Next step: ask for postcode and callback number.”
Review shows the proposed effect and why it stopped. The owner can inspect the concrete work before authorising anything.
“Thanks for getting in touch. We cover Bristol and I’ve marked this urgent. What postcode and callback number should we use? I haven’t promised a time yet.”
A correction in Chat becomes a visible rule or preference in Training. The owner can inspect it, edit it, or remove it.
“For urgent enquiries, ask for the postcode and best callback number before discussing availability.”
Improvement is not a badge or a promise. The next comparable job is where the owner can see whether the correction changed the work.
“Rule applied: postcode and callback number requested; no availability promised; reply held with the new evidence visible.”
Proof beside its boundary
The walkthrough explains the shape. This company-owned production test is the harder evidence underneath it.
On Vavio's company-owned, already-connected production Gmail account, two consecutive marked cycles read real mail, wrote a draft that Vavio verified at Gmail, held the reply, and delivered it only after explicit owner approval.
That is Vavio's product test, not a customer result. A stranger connecting their own Gmail through Vavio's branded consent still awaits Google's restricted-scope verification; it does not guarantee a recurring inbox result for a new owner, and unattended sending remains unproved.
The employee’s Skills and the situation determine the Action it proposes. Run evidence helps the owner decide whether that Action should require approval. Current safety floors can still hold work, and this public proof makes no unattended-send claim.
Start with one ready employee in Chat. Give it the job, the facts, and the boundaries—then inspect the work and correct the same employee.
Free trial · No card required · The demo sample is fictional; no customer data is shown and nothing in the walkthrough was sent.