See Vocion run

Want it built around your own use case instead? Request a free demo — we build it on your workflow before the call.

The fastest way to understand Vocion is to watch one run land: a ticket in, a grounded draft out, a person approving it, and the whole path on the record. Clone the repo and you are looking at this screen in about two minutes from git clone.

Run Trace
  1. Triggered
    New enterprise support ticket — Acme Health
  2. Context retrieved
    Ticket, contract, history, escalation policy
  3. Decision record
    Classified as billing escalation with renewal sensitivity
  4. Tools called
    Account lookup · KB search · SLA check
  5. Draft generated
    Response draft created · eval check passed
  6. Human review requested
    “Mention the open credit memo; remove refund commitment.”
  7. Approved & logged
    Approved by Morgan, CX Lead · CRM updated
Accountability: reviewed outputs ship with the approval, the decision record, and the cost — so “why did it do that?” has an answer on screen.
Live demo

Support reply drafting with approval

L1 · ticket in → draft out → human approval

A real workflow: summarize an inbound ticket, draft a reply, route to a review queue, audit every step. Eight sample tickets cover shipping delays, refunds, billing, angry escalations, and a thank-you note (which should NOT auto-draft a fix).

Run it locally

Prereqs: Node 22+, Docker Desktop, git. About 2 minutes end-to-end.

git clone --recurse-submodules https://github.com/vocion/vocion-local.git
cd vocion-local
./bootstrap.sh
docker compose up -d
cd vocion-demos/demos/support-reply && ./scripts/dev.sh

Then open localhost:3001/sign-in — the banner autofills demo@example.com / demo123.

More demos

Each starter ships as a separate package once the L1 demo proves the pattern. These are the next two on deck.

Want a hosted “click and try” URL?

That ships with vocion-cloud — the hosted overlay (Clerk auth, multi-account, Stripe billing) that pins a specific vocion-core release. The demo infra is open source today; the public demo URL is the next phase. Subscribe to the blog or watch the repo for updates.