Bokadirekt has no open booking API, so VOCA does not pretend to have an integration. Instead Kim does the next best thing: answers questions, takes the request and sends the customer a link straight to your own booking page. The customer picks a time and books themselves, like always.
Kim answers questions about services, prices and opening hours from what you have added in VOCA. Kim never reads your Bokadirekt calendar, so Kim never promises that a time is free.
When the customer wants to book, Kim asks what it is about and roughly when, then sends the link to your Bokadirekt page: by SMS on phone calls, in the chat otherwise. If you have added service links, the customer lands straight in the right service's calendar.
The customer's request is saved in VOCA so you can see who wanted to book and roughly when. The booking itself is made by the customer through the link, and it shows up in Bokadirekt as usual.
We spell this out because it is cheaper for everyone to know up front than to find out with a guest on the phone.
Is this an integration with Bokadirekt?
No, and we would rather say that outright than pretend otherwise. Bokadirekt has no open booking API today. Kim sends an ordinary link to your own public page, the same page your customers already book on.
Does Kim book appointments for the customer?
No. Kim cannot see your Bokadirekt calendar and therefore never promises that a time is free. Kim finds out what the customer wants and sends the link; the customer then picks a time and confirms themselves.
What do we see in VOCA?
Every request: who wanted to book, which service and roughly when, plus the whole call or chat. The booking itself you see in Bokadirekt as usual once the customer completes it.