We need one thing: to know when a visit has finished. Every booking tool can tell us that in at least one of three ways. Setup is part of your onboarding call and takes under thirty minutes.
If your diary publishes an iCal or ICS link (most do: look for "subscribe to calendar"), paste it into your settings. We read finished entries every few minutes and ask each customer after your chosen delay. Nothing to install, nothing for your team to do.
Your booking tool triggers a Zap when a booking completes and the Zap sends it to us. Works with Vagaro, Timely, Phorest, Acuity, Mindbody, Calendly, Google Calendar and hundreds more. We give you the exact recipe.
Export the day's visits from your system and upload the file, text one line to our number from your mobile, or type a name and number into the dashboard. Under a minute a day.
In Zapier, choose your booking tool and the event "Appointment completed" (some tools call it "ended" or "status changed").
Add "Webhooks by Zapier", choose "Custom Request", method POST. Paste the endpoint shown on your Connect page.
Authorization: Bearer YOUR_KEY (create a key on your Connect page) and Content-Type: application/json.
Map the booking's reference, first name, mobile or email and end time into the JSON we show you. The same reference twice is ignored, so re-runs are safe.
Send one test booking. It appears on your dashboard as "scheduled" within seconds. Make users: the HTTP "Make a request" module works the same way.
Then CSV or text-in. Every system can export a list, and texting "Done: Sam, 07911 123456" takes ten seconds. Several of our pilots run this way.
When several customers share one system that has a proper API, yes. Until then the three routes above cover everything we have met, and they are what we set up on the onboarding call.
A first name and a mobile or email from each finished entry, and the entry's end time. For health businesses the entry title is never stored. The calendar link itself is kept private and never logged.
Popagain