Training and handover
Your team learns it on real cases.
We train the people who accept and close requests, and hand over the setup so your owner can run it.
A focused pilot.
A clear path to launch.
Every stage has a deliverable and a checkpoint. Dates are set with you and depend on your readiness and on any integrations.
Fig. 01 — Thirty days
Illustrative
01 / Five stages
Who does what.
An illustrative sequence. The pilot plan sets the dates.
01
Discover
Vocalabs does
Runs a scoping session and writes the pilot scope.
You provide
A named owner, the first use case, and your policies and information sources.
Checkpoint
The pilot scope is agreed in writing.
02
Configure
Vocalabs does
Sets up services, facts, routing and languages, and runs the quality check.
You provide
Approval of the knowledge and wording, and a named owner for each team.
Checkpoint
The quality check passes and you approve the setup.
03
Connect Where required
Vocalabs does
Assesses and builds only the connections you agreed.
You provide
Access and permissions, and a technical contact for each system.
Checkpoint
Each connection is tested for its agreed actions, or marked out of scope.
04
Validate
Vocalabs does
Runs test scenarios in both languages and trains your team.
You provide
Time for your team to test, and sign-off on outcomes.
Checkpoint
The agreed scenarios behave as expected and handoff rules are confirmed.
05
Pilot and review
Vocalabs does
Supports the pilot and reviews results with you.
You provide
Real use within the agreed scope, and feedback from your team.
Checkpoint
A review against the agreed measures, then a decision on what comes next.
Dates depend on four things: how quickly knowledge is approved, system access, any integration work, and testing time.
02 / Readiness
Are you ready to start?
Tick what you already have. It stays on this page and is not sent anywhere.
03 / Success measures
Agree the measures first.
We don’t publish benchmark numbers. You and we agree what success means.
Correct routing
Requests reach the right team with the right context.
To agreeResponse quality
Answers match your approved information, in both languages.
To agreeStaff adoption
Your team accepts and closes requests in the workspace.
To agreeSupport and incidents
Confirmed in your agreement.
Support contacts, hours, escalation paths and response expectations are agreed in writing for your pilot.
Changes after launch
Knowledge and workflows evolve.
Update knowledge, adjust routing, and review regularly. Changes go through the same quality check and approval, and can be rolled back.
04 / Deployment questions
Good questions.
How long does a pilot take?
It depends on your readiness and any integrations. We give you a dated plan once the scope is agreed, with the dependencies named.
What support do we get?
Support arrangements are written into your pilot agreement. We don’t assume a standard on your behalf.
Where is our data hosted?
Hosting and retention are agreed during scoping so they match your requirements.
Can we stop after the pilot?
Yes. The review ends with your decision: continue, change the scope, or stop.
Next step
Plan your pilot.
Tell us about your business and we’ll propose a scope.