The mechanics
How Volty works
Volty's front office runs on two things: a shared inbox that decides what reaches a person, and automation rules you describe in plain English. Here is how each one works.
The inbox
How Volty's inbox works
Volty puts WhatsApp and email into one inbox and decides what reaches a person.
Every channel, one inbox.
WhatsApp and email flow into a single shared inbox, so nothing slips between apps.
Instant replies in your brand's voice.
Volty handles greetings, questions and follow-ups 24 hours a day, then hands the hard ones to your team with the full thread attached.
Conversations sort themselves.
Volty files each thread as Active, Snoozed, Resolved or Spam. Snooze a thread and it stays parked until you are ready, and a customer's reply waits quietly instead of jumping back to the top.
Your people, your voice.
Staff reply under their own name. Draft mode holds every Volty reply for a person to approve, live mode lets Volty send on its own, and you set it per inbox.
A CRM that builds itself.
Volty remembers who each customer is, labels leads as the conversation moves, and logs every enquiry to your tracker, so your team knows who to follow up with and when.
Team chat beside the work.
Internal Rooms and DMs keep the discussion next to the conversation it is about, rather than scattered across other apps.
A personal lens on the inbox.
Each person saves the filters that matter to them, so the urgent surfaces and the noise waits.
Automations
How Volty builds automations
Volty turns a plain-English rule into a standing automation, then runs it, logs every run, and pauses it if it fails.
Rules you describe in plain English.
Tell Volty what should happen every time, for example “ping the assignee when a conversation is unanswered for 30 minutes” or “acknowledge messages that arrive after hours”, and Volty turns it into a standing rule.
Triggered by anything.
Volty runs a rule on a schedule, on an event such as a new message or a new row or a lead being assigned, or from a webhook one of your other tools calls.
Set and forget.
Every rule runs on time, every time. When one fails, Volty pauses it and tells you, so nothing spirals quietly in the background.
Acts on your behalf.
Volty sends, resolves, snoozes, labels and writes to your tables.
Reaches your other systems, never your passwords.
Volty can call the other tools your business runs on, but only the ones an admin ticked off when approving that rule. Your passwords are swapped in at the last moment, so they never sit inside the automation or turn up in its history. Switch an integration off and every rule using it stops immediately.
A full journal of every run.
Volty records when a rule ran, why it ran, and what it did. No black box: the history is one click away.
Nothing ships without your say-so.
A new rule arrives with a preview of exactly what it would have done, and waits on your approval card. Volty does the heavy lifting, you keep the decision.
Start from a template, not a blank page.
Pick an SLA alert, a daily digest or an out-of-hours acknowledgement, tell Volty what should differ, and it goes live.
Mini apps
How Volty builds mini-apps
Volty writes the app, holds it behind an admin's approval, and runs it sandboxed away from your session.
Volty writes the app, not a form.
A mini-app is two source files, so authoring is Volty's job rather than a builder you have to learn. You describe the screen you want and Volty writes it.
Every deploy waits for a person.
An app deploy is code served to your team's browsers, so it arrives unconditionally pending approval. There is no tier that skips the gate.
Only an admin can approve it.
Approval is enforced on the server, so someone without the permission sees the wait spelled out rather than a button that would fail.
It runs sandboxed, away from your session.
The app's frontend runs in an opaque-origin sandboxed frame with no access to your session. It reaches your data only through its own backend.
A version trail you can read.
Volty records every deploy as pending, active, superseded, rejected or withdrawn, with who submitted it and when, so you can see what changed and who let it through.
Approving publishes it to everyone.
Approving a version makes it the live one for the whole organisation, and it appears on your Mini Apps page for the team to open.
Keep reading
The Volty whitepaper. The architecture underneath: how one agent serves many businesses, isolated by design and auditable to the row.
Keep reading
- The Volty whitepaper.
- The architecture underneath: how one agent serves many businesses, isolated by design and auditable to the row.
- Hire your AI agents. Don't install them.
- The framework for deciding which work an agent should take, and how it earns autonomy.
- What Volty does.
- The six jobs Volty handles in your inbox, and what it costs.
● Start with a conversation
Volty starts by asking
about your business.
No implementation project and no engineers on site. Volty interviews your team, drafts how it should answer, and tests itself before it talks to a single customer.
Free 7-day trial. We set your workspace up for you.