Data boundaries
Define what your agent can access and retain. Each organization’s data is kept separate.
The details that make
it your platform.
Start with the operating requirements. Build the pilot around them.
Fig. 01 — The controls, agreed
Illustrative
Operating controls
Team permissions
Agree who configures, reviews and approves — and who can only see.
System connections
Scope the integrations your workflow needs. Nothing is connected without being agreed.
Human oversight
Set the moments that call for your team, and the time they have to respond.
01 / How it is controlled
What the platform does today.
Specific behaviours, not slogans.
| Area | How it works |
|---|---|
| Secrets | Credentials such as a Wi-Fi password are stored encrypted. They are never placed in instructions, never spoken, and are shown only to a verified stay. |
| Customer access | Access is verified per customer. In hotels it is bound to a stay, stored as a hash, locked after repeated wrong codes and ended at checkout. |
| Honest states | A request is shown as sent only after it is recorded. Switched-off services are refused everywhere. |
| Staff and customer separation | Private staff notes are stored separately and there is no path for a customer to read them. |
| Change control | Setups are versioned. A quality check and an approval come before launch, and earlier versions can be restored. |
| Record | Requests keep a history of status changes and who made them. |
Compliance. We do not claim formal certifications today. Data residency, retention and regulatory requirements are captured during scoping and agreed before launch.
02 / A considered rollout
Start focused. Expand with confidence.
One use case. A clear owner. An agreed measure of success.
DAY 01
Discover
DAY 07
Configure
DAY 14
Connect
DAY 21
Validate
DAY 30
Pilot
Illustrative 30-day plan. Timing depends on scope, access, integrations and testing.
03 / Questions procurement asks
Good questions.
Where is our data stored?
Hosting location and retention are agreed during scoping so they match your requirements. We will not assume them for you.
Can we restrict who changes the setup?
Yes. Configuration, review and approval are separate steps, and nothing goes live without approval.
Does VOCA connect to our booking or billing system?
Connections depend on your systems and available APIs and are scoped in the pilot. Until connected, those services create requests for your staff, not bookings.
What happens when VOCA cannot help?
It says so, does not guess, and offers to connect the customer with your team. Your team can also take over at any time.
Next step