Nine booking backends out, eight channels in. Kim asks your system which times are free, reads the answer, and books only a time the system itself said yes to. You change nothing.
The same path every time, whether the guest calls, types in the chat or sends an email. Kim works out what the guest wants, asks your booking system whether the time exists, and writes the booking there. One booking system is active per venue, and you switch by connecting a new one.
What Kim can promise depends on what your system answers. If it has a real availability endpoint we ask it and compute nothing ourselves. If it has none, we work the free times out from the bookings already sitting there. If there is nothing to check against, Kim says it is a request and emails it to you.
Kim never invents a time. That rule sits behind every entry below, and it is built into each connection rather than written into an instruction a model can forget.
All nine are built and switchable from the portal. Open one for what actually happens, what it takes to connect, and what Kim will not do there.
The calendar is already your booking book. Kim reads it to see what is free and writes the booking into the same calendar, where staff are already looking.
Read from the calendarYes, the guest gets a bookingRead moreIf you run Microsoft 365, the calendar is already where the day gets decided. Kim reads it to see what is free and puts the booking in the same place.
Read from the calendarYes, the guest gets a bookingRead moreBokaMera already knows which times are free, which services you sell and how long they take. Kim asks and books. We compute nothing ourselves.
Asked from the systemYes, the guest gets a bookingRead moreKim reads your free times from EasyPractice and books the client onto the right service in the right calendar. Kim sees bookings and times. Never clinical notes.
Asked from the systemYes, the guest gets a bookingRead more
Restaurant booking systemRight party size, right sitting, right room. Kim asks GastroPlanner what can be booked and takes only what can.
Asked from the systemYes, the guest gets a bookingRead moreThe same tables, booking types and free times your own booking page shows. Connecting takes exactly one detail from you.
Asked from the systemYes, the guest gets a bookingRead moreEvery bay and every mechanic is a resource. Kim puts the job on one that is free and writes the registration number and mileage straight onto the bar.
Worked out from bookingsYes, the guest gets a bookingRead more VOCABuilt-in booking systemIf you have no booking system you do not need to buy one to get started. The bookings live in VOCA behind a real capacity gate.
VOCA's own capacity gateYes, the guest gets a bookingRead more FormulärRequestsNo automatic confirmation. Kim takes the name, time, party size and what it is about, emails it to you, and tells the guest it is a request.
Not checkedNo, becomes a requestRead moreThe channel decides how the guest gets in touch, not what Kim can do. A call, an email and a DM land in the same conversation list and book into the same system.
A local number. Kim answers around the clock, books during the call, and hands over to staff when the question is not a booking.
We set it upOne script tag on your site. The same Kim as on the phone, with the booking done before the visitor leaves the page.
Switch on yourselfKim reads incoming mail and replies with the booking already made, instead of asking for a phone call.
Switch on yourselfConfirmations and reminders out, and guests who would rather text than call in. Same conversation as everything else.
We set it upConnects to your Facebook page. Messages to the page turn into bookings without anyone sitting in the inbox.
Switch on yourselfKim answers DMs to the account. Useful where half the booking flow already runs through Instagram.
Switch on yourselfOne bot per venue. You paste the token into the portal and the rest wires itself up.
Switch on yourselfBuilt and ready. Needs an approved Meta app, so we connect it rather than you doing it in the portal.
We set it upThen we say so plainly rather than talking around it. Here is where things stand for the systems we get asked about, and what is missing before we can build them. We have read the API documentation for every row.
Running something that is missing entirely? Email the system name to hej@hivoca.com. We reply with whether it can be built and what it takes, including when the answer is no.
VOCA has its own MCP server with 19 tools, its own OAuth, and a connect button in the portal. Ask your assistant how the day went, which calls Kim could not handle, or change the opening hours, without logging in anywhere.
Do we have to change booking system to use VOCA?
No. That is the entire point of this list. If you run BokaMera, EasyPractice, GastroPlanner, easyTable or Ganttic, Kim writes into it. If a Google or Outlook calendar is all you have, that is enough. If you have nothing, VOCA is the booking system.
What does an integration cost?
Nothing beyond the subscription. The connections are included and we do not charge per booking. What can cost money is something your vendor charges for, such as BokaMera's API licence.
How long does it take to connect?
The calendars take under a minute: sign in with Google or Microsoft and pick a calendar. The booking systems take as long as it takes you to get hold of an API key, and that is usually the only thing that drags.
Can Kim double-book?
Not on a system with a capacity gate, and eight of the nine have one. Kim only books a time the system itself returned as free, and for most connections the time is checked again at the moment the booking is created. Requests are the exception, which is why they promise nothing.
What happens if your system loses contact with ours?
Kim stops offering times and hands over to staff rather than guessing. You see the error with a timestamp under Integrations in the portal, so you find out visibly instead of through a guest calling to ask.
We look at what you run today and tell you whether Kim can book into it. Twenty minutes.
Book a demo