Vex is the AI customer support engine built by Voxil Studio. Every reply is assembled from your own approved knowledge base — deterministic answers, no invented promises, and a clean handoff to a human the moment certainty runs out.
No investors, no roadmap committees, no engagement strategies. Just one product, the person who maintains it, and a first-reply time you can put in a contract.
Tech stack
Next.js
React
Node.js
Tailwind CSS
Framer Motion
Lucide
Next.js
React
Node.js
Tailwind CSS
Framer Motion
Lucide
Product overview — live now
Meet Vex.
The AI Customer Support Engine.
Not a roadmap item — the studio’s first shipped product, already answering real tickets. Everything below goes deeper: the console it runs in, and the four promises the whole thing is built on.
Live
Vex
AI customer support engine
Support that keeps its promises. Vex answers from a knowledge base a human approved, says so out loud when it has nothing to say, and hands a real person the whole thread the moment certainty runs out. It is deployed, in use, and the reason this studio exists.
100% deterministicEvery reply comes from a rule someone wrote down.
A logged handoffThe human picking up gets the whole thread, not a summary.
Local / BYOKYour knowledge base stays where you put it.
One control plane
Every conversation, one dashboard.
Vex runs on a single surface that shows what it answered, what it refused to guess and what it handed to a human — with the latency and the audit trail sitting next to it.
vex.voxilstudio.host — inbox
Conversations today
1,204
3 nominal1 watch
Resolution rate
98.2%
Median first reply
1.4 s
Languages live
11
Uptime · 12 mo
99.98%
Vex traffic · last 24 h
1,204 resolved
resolved / hescalated / h
Vex queue status, last 24 hours
Queue
Last 24 h
Δ 24 h
State
Email
412 resolved
+2.1%
live
Live chat
611 resolved
+6.4%
live
Human queue
181 escalated
-3.2%
watch
Knowledge base
9,430 articles
+112
live
What Vex does
Four promises Vex actually keeps.
Each one is a behaviour you can test in the first week of a deployment: what it answers, what it refuses to guess, who it escalates to, and what it sounds like doing any of it.
Architecture
Deterministic Logic
Software-first architecture
Vex resolves a ticket the way a build system resolves a dependency: by rule. Every answer is matched and assembled from your approved knowledge base, so the model chooses between things a human wrote instead of authoring its own. When nothing qualifies, Vex says so rather than guessing.
Anything Vex cannot close lands in an inbox with a name on it — thread, history and the reason it escalated already written up. Nothing ages out quietly, nothing is marked resolved because the chat timed out. Follow-up is a queue you can audit, not a hope.
Support has the same shape everywhere: an ask, a policy, an answer, a human. Vex models that shape instead of a vertical, so a clinic, a logistics firm and a game studio configure it with their own words and their own rules — no fork, no re-platform, no six-week integration.
The voice was written by someone who has de-escalated a real lobby at eleven at night, not tuned to demo well. Vex acknowledges the inconvenience before it answers, apologises once, and drops its register when a customer is genuinely upset rather than cheerfully repeating itself.
A studio the size of one person and one product done properly.
Voxil Studio came out of guest relations — the part of a business where you find out, fast, what happens when software promises something it cannot deliver. Support tickets are where bad engineering becomes someone’s bad evening.
So Vex is built the other way round: predictable behaviour first, then speed, then polish. Nothing ships because it demos well. It ships because it held up under real load for a month and nobody had to be woken up.
System promise
100% Deterministic
Hallucination rate
0%
Data privacy
Local / BYOK
Audit trail
Included
Deterministic by default
If a product makes a promise to a customer, that promise comes from a rule someone wrote down — not from a model guessing in the dark.
Own the whole stack
No vendor in the middle that can raise prices, change terms or disappear on a Tuesday. Everything here runs on infrastructure we control.
Ship small, ship often
Releases are boring and frequent. If a build takes more than a week to describe in one sentence, it was too big.
About the creator
Built by a Guest Relations Expert.
Vex wasn’t coded in a vacuum; it was engineered by someone who spent years managing real customer complaints.
“That’s why it doesn’t sound like a robot.”
Escalations are never about the ticketThe person writing in has already explained this once. Repeating the question back to them is what turns a bad day into a churned account.
A confident wrong answer costs more than silenceHandlers learn fast which promises they can keep. A support engine has to learn the same limit, and say so when it hits it.
Handoffs fail on context, not on speedThe worst part of being transferred is starting over. The human picking up should already know everything the machine knew.
Contact
Let’s build something.
Deployments, integrations, or a problem that deserves its own product — leave an address and you get a reply from the person who actually wrote the code.