Kim books jobs straight into your Blikk.
Kim takes the call, works out who is free and puts the job on the right person. It lands as a task in Blikk, in the same planning view you already work in.
What actually happens
Blikk has no calendar of free times, it holds tasks. So Kim works out who is free by reading the tasks in the window and comparing them against the people you ticked.
Once the customer says yes the task is created with the right person already on it, in a single call. The customer's name, phone and address are in the description, so whoever drives out has everything.
If the time needs to move, Kim rewrites the task and keeps the person, the length and everything else that was on it. If the job is cancelled the task is archived and the person released, so the time is bookable again.
The connection in short
Four steps
- 1Create an API application in Blikk and give it the Task_Read and Task_Write permissions. A new application has no permissions at all, and without them signing in works but no bookings do.
- 2Paste the application ID and the secret into VOCA.
- 3Tick which people Kim may book. The list is fetched from Blikk, you just choose from it.
- 4Done. Kim books from the next call, and the tasks appear in your normal planning view.
What Kim will not do here
We spell this out because it is cheaper for everyone to know up front than to find out with a guest on the phone.
- Blikk does not push changes to us. If you move a task in Blikk, Kim sees it on the next read rather than on the second, which in practice means within a minute or so.
- Kim reads back a set number of days to catch long jobs that are still running. A job that started further back than that is not counted in capacity. You set the number yourself, and 60 days covers almost everyone.
- Kim counts one person per job. If several need to go out on the same visit, add them to the task in Blikk afterwards.
Read on for your industry
About this connection
Do we have to give away full access to Blikk?
No. The application needs to read and write tasks, nothing else. If you want Kim to link a booking to an existing customer you add read access to contacts, and that one is optional.
What if we add a task by hand at the same time?
It blocks the time for Kim too. Capacity is read from the same tasks your own planning view shows, so a task you enter yourself is counted.
Do you create customers in our register?
No. Your customer register feeds your invoicing, and filling it with near-duplicates cannot be undone. Kim links the job to an existing customer only on an exact name match, otherwise the customer's details sit in the description.
