GuluStock and AutoServa · GuluStock and AutoServa: User Guide
Getting started with AutoServa means checking that one of your workflows is a good fit, contacting VYROX, and moving through a staged engagement that begins with a decision audit and ends with a supervised AI operator running your queue. This guide is for business owners and managers in Malaysia and elsewhere who are considering AutoServa.
Any three of these signs usually justify a decision audit:
There is no email enquiry channel and no contact form. Replies usually come the same working day, and you can ask questions before you book anything.
| Stage | Timing | What Happens |
|---|---|---|
| Observe | Week 1 | Watch a real queue with the people who work it |
| Capture | Weeks 1 to 2 | Write down the unwritten rules, including exceptions |
| Codify | Weeks 2 to 3 | Produce an explicit decision framework |
| Fine-Tune | Weeks 3 to 5 | Train the operator on your material and vocabulary |
| Run | Weeks 5 to 8 | Shadow running, then supervised live running with humans releasing |
| Prove | From week 6 | Every decision carries its evidence |
| Improve | Continuous | Corrections feed back into the framework |
Nothing is automated until the operator can already reach your team's answer on its own.
| Role | Time | Purpose |
|---|---|---|
| Process Owner | 2 to 3 hours a week, weeks 1 to 3 | Settles disagreements and signs off the framework |
| The Person Who Decides | 3 to 4 hours a week, weeks 1 to 3 | Explains how cases are really decided |
| IT or Systems Lead | A few hours, weeks 2 to 4 | Sets up the operator's account and access |
| Compliance or Risk Lead | One session plus a week 5 review | Confirms guardrails match policy |
You do not need a clean labelled dataset. If your process is not documented anywhere, that is the normal starting point: writing it down is the first thing the decision audit produces.
AutoServa is priced per workflow, not per seat, and there is no published price list.
In rough order of impact:
The baseline is agreed during the decision audit, usually a mix of throughput, how often a case needed rework, and how often two people would have decided it differently. Results are compared with your own prior numbers, not an industry benchmark.
After the first workflow is live, nothing is added automatically. Further workflows are added only as the deployed ones earn trust, and each is faster to tune because the vocabulary, standards and precedent are already in place. Stopping at one queue is a legitimate outcome.
A supervised live run is typically reached in five to eight weeks.
No. Each stage is committed separately, and you keep the decision framework from the audit.
You keep the framework, precedent library and evidence trail in an open format, and VYROX access is removed.
The process owner and the person whose judgement the team actually defers to, often not the manager. They need roughly two to four hours a week each during the first three weeks.