Vocion 6.0: Routines
Vocion 6.0 adds Routines. A specialist teaches a task once from a narrated Slate recording, and Vocion runs it for every row of a list, each in a browser of its own, with every exception sent to the routine's expert.
Status: shipped. #1376, cut as v6.0.0. One migration (0211_routines). Turn it on with plugins: [routines].
Some work is the same few screens, done again for every name on a list: adding people to a training console, setting up accounts, updating records in a system with no API. With Routines, the person who knows the task shows Vocion once, and Vocion does the rest of the list.
What you can do now
- Teach a task from a recording. Record it in Slate on the real system and say why each step happens. Share the link in chat, or press Teach a routine on
/dashboard/routines. - Check the draft against the recording. Vocion drafts the routine: the steps, each linked to its moment in the recording, the rules, when to ask the expert, and what is never allowed. It asks the expert what one recording cannot settle.
- Set how much it does on its own. The expert approves the routine and sets its trust. At Drafted every change waits for a person. At Approved the changes the routine names run on their own and anything else waits. Autonomous is earned after 20 verified runs.
- Run it for a list. Each row runs in a browser of its own, many at once, and you watch them as one live queue. A row the routine already did is skipped.
- Answer exceptions one at a time. When a row hits an exception, the routine's expert gets one decision, with the page as evidence and the recommended answer first. The answer goes back to that run.
- Trust what it saved. Every change is read back and kept as a receipt. A run that cannot confirm a change is never replayed. The expert checks it by hand.
- Find what the list missed. Afterwards Vocion checks the system against the list, for example users in the account who are not on the roster, and asks the expert what to do with them. That answer runs as its own batch.
- Read the report. Results verified by read-back, how each escalation was answered, time against doing it by hand, and cost.
What changed for browser runs
This is a major version because browser runs ask for approval more often. A browser run now waits before it clicks a button that creates, invites, enrolls, adds a user or member, archives, launches, activates or deactivates, as it already did for submit, save, pay and delete. A run that clicked one of these on its own before now waits for a person. Workflow steps with action: routine.run now start a real batch.
Where to find it
- Routines on the app rail, at
/dashboard/routines. Try the practice routine there runs on a practice training console with made-up people. - Docs: Routines. The full guide is in vocion-core.
Get it
Update to v6.0.0 or later and add routines to plugins in workspace.yaml, or turn it on from Apps → Routines. Routines run as browser runs, so set those up first. To teach from a recording, connect Slate on Connections.
From v6.1.0, Remember these for this routine on the Run it form keeps a routine's sign-in, sealed, so a batch you ask for in chat needs no password.