Connections scoped
around your systems.
Today VOCA is a customer screen, a voice agent and a team workspace. Links to your other systems are assessed first, and built only where we agree.
Illustrative
01 / Where things stand
Three honest groups.
We keep what exists, what needs assessing and what is planned separate.
Built into VOCA
The customer web screen, the voice agent, the team workspace for requests and conversations, and knowledge setup. These need no connection to your other systems.
Connections to your systems
Property-management, task, booking and CRM systems, and messaging or notification channels. None is connected by default; each is assessed against your system and its interfaces, then scoped.
Roadmap
We list planned connections only where a roadmap is documented. None is published yet, so none is promised here.
02 / Where VOCA could connect
Categories we assess.
A category is not a promise of support for a product.
| Category | What a connection could do | Status |
|---|---|---|
| Core operations systems | Look up a customer, booking, stay or policy record, so a request carries the right context. | Assessed per project |
| Service and task systems | Create or update a task in the system your teams already use. | Assessed per project |
| Booking systems | Check availability or create a booking or appointment. Until connected, such services stay requests. | Assessed per project |
| CRM | Record an enquiry against a customer or contact. | Assessed per project |
| Messaging and notifications | Notify staff or reach customers on a channel you use. | Assessed per project |
03 / An example flow
Request, action, confirmation.
How a connected request could work once a connection is agreed.
01
Customer request
A customer asks for something.
02
VOCA
Understands the request and records it.
03
Agreed system action
Only an action you approved, in a system you named.
04
Staff confirmation
Your team acknowledges and updates the status.
This is a diagram of a design, not a live connection. No connector is shown as connected.
04 / How a connection is controlled
Agreed per connection.
These points are settled with you before anything is built.
What it may read
Only the fields we agree, such as a record’s reference or dates. Nothing else in the system is requested.
What it may write
Only actions you approve, such as creating a task. Anything with a price or a binding commitment stays a request for a person to confirm unless you decide otherwise.
Permissions
A dedicated account in your system, with the least access that works, set up and approved by your own IT team.
When it fails
VOCA is set up to tell the customer nothing was sent and to offer your team. The request stays visible to staff, and a person can take over.
Next step
Tell us which system you use.
We’ll tell you plainly what a connection would involve.