We take the call. You keep the booking.
VOCA answers when customers reach out: phone, chat, email, SMS, social media. Around the clock, even after closing. We take the call and write the booking straight into your system through your API. We replace nothing. Your system stays the one that counts.
We sit in front of your platform, not in place of it.
Businesses lose bookings every time the phone rings unanswered or a message sits unread. VOCA answers instead: by phone, in web chat, and over SMS, email and social media. It reads what the customer wants and completes the booking for them.
The booking lands in your system, through your API, exactly as if one of your own users had typed it in. Your product, your data and your customer relationship. We don't touch them.
You're the booking engine. We're the front door.
The customer reaches out.
We handle the conversation.
The booking lands in your system.
The same flow on every channel, in every industry. Everything on our side is generic. Your platform is the one fixed point everything lands in.
One small, well-defined API. That's genuinely all.
There's not much to do on your side. One way to log us in, four operations, and something to match the customer on. No login to your interface, no database dump, no migration.
What we ask for
What we never touch
Four operations. One contract.
Map them onto what you already have, and you're done. They look the same whether the customer's booking a table, a vet visit or a tyre change.
Check availability
What's actually free, in real time. We never promise the customer a time without asking you first. No guessing.
Create booking
A new booking with the customer's details and any notes. It carries an idempotency key, so a retry never becomes a double booking.
Modify booking
A new time, a bigger party, or changed details. Only after we've verified it's the customer's own booking.
Cancel
Frees up a time the customer owns. Same check as modifying, so no one can cancel someone else's table.
No public API yet? We work with what's there. A direct API is ideal, but a partner gateway, an aggregator, calendar-level access, or a structured handoff while you build something deeper all work too.
How we know it's really the customer.
Creating a booking is harmless. Touching one that already exists isn't. Here's how the check works, using a phone number as the example.
Built so your security team can say yes without a six-month review.
The surface is small on purpose. Everything around it is traceable, revocable and EU-compliant from the start.
Keys only reach booking endpoints. You rotate or revoke them instantly. We never ask for more than the four operations require.
Conversation data sits on servers within the EU, under a data processing agreement. The list of subprocessors is open, and the right to erasure is built in.
Every booking is preceded by a real availability check. Create carries an idempotency key. Your change webhooks keep both sides in sync.
Every action traces back to a conversation and its history. You can always see what was done, for whom, and why.
VOCA always tells the customer it's an AI. The system follows the transparency requirements in the EU AI Act.
We respect your rate limits and back off when needed. A spike on our end never becomes a flood of calls on yours.
One contract, whatever “a booking” means for you.
The four operations stay the same. Only the words change. The same core serves a restaurant platform and a veterinary system without a single new kind of endpoint.
An AI front door for your customers, that you didn't have to build yourself.
The businesses running your system are already losing trade to missed calls and unread messages. We catch them and turn them into bookings, in your platform. That makes you more essential, not less.
More completed bookings, straight to you
Every call we save after closing or in the middle of a rush becomes a booking in your system. New volume on rails you already own.
A voice & chat layer with no build cost to you
No AI team to staff, no models to keep running, no channel integrations to maintain. We carry that. You expose four operations.
Zero churn risk for your product
We sit in front of you, not on top of you. You keep the data, the bookings and the customer relationship. We just make them worth more.
The questions partners actually ask.
Are you trying to replace our system?
No. You stay the source of truth. We're a client against your API. The booking lives in your platform, managed by you, exactly like today.
What access do you actually need?
Limited keys for four operations: check availability, create, modify, cancel. Plus a way to match a customer, usually phone or email. Nothing more.
How do you avoid double bookings?
We never confirm without a real availability check. Every create carries an idempotency key. A change webhook from you keeps both sides in sync.
How do you know it's really the customer?
We match the number or email getting in touch against the contact on the booking before we change anything. When needed, we add a one-time code.
Where is the data stored?
Within the EU, under GDPR data processing agreements. Subprocessors are listed openly, and you control the retention period.
What if we don't have a public API?
Then we work with what's there: partner gateway, aggregator, calendar-level access, or a structured handoff until you've built something deeper.
Who owns the customer relationship?
The business, and you. We're the plumbing in the conversation, not a party to the relationship.
How heavy is the integration?
Light, on purpose. Four endpoints and one login method. Count on weeks, not quarters.
Let's map your API to ours.
Send us your API documentation, or just your questions. We'll get back to you with exactly how the four operations fit together on your end.