Connecting a booking system you already use
If you already run a booking system, the agent should book into it rather than keep a second calendar.
How it goes
1. Tell us which system you use. Rezerv, Mindbody, Fresha, Calendly, an in-house sheet — the name is enough to start. What matters is not the brand, it is whether that vendor gives your account API access.
2. Add us as a dev or test user. We need to see the account before we can tell you which route applies. Until we have looked, any date we give you would be a guess.
3. We confirm the route in writing. A direct API connection if the vendor exposes booking endpoints to your account, a browser extension if not. Either way it is named in your proposal before you commit.
4. We connect availability first, writes second. Reading real availability is what stops the agent inventing a slot. Writing the booking back comes after that, once reads are proven correct.
A demo agent that confirms a booking is showing you the conversation, not a live write to your calendar. Ours says so on screen. Until the connection above is built, no real booking is being made.
What goes wrong without a real connection
- The agent offers a slot that was taken thirty seconds ago. This is why availability must be read live, not cached
- Two customers confirm the same slot at once. The first write wins; the second is offered alternatives
- A class is cancelled in the booking system but the agent still offers it. The sync interval decides how long that window stays open
When you do not need a calendar write at all
Sessions that need a person to approve the time — a private class, a site visit — do not need one. The agent notifies your team, holds the thread while they decide, then replies to the customer.
Frequently Asked Questions
Can the agent keep its own calendar instead?
It can — see appointment booking — but running two calendars means reconciling them, and that job lands on your team. If you already have a booking system, connect it.
What if my booking vendor has no API?
Then it is Route B: a browser extension driving the same screens your staff use. See Connecting your systems.
How current is the availability the agent sees?
On a direct API connection, live at the moment it answers. On a browser-extension route it depends on the sync interval, which we agree with you and state in the proposal.
Up next
Taking payment in the conversation
The agent can collect payment in the same thread as the order, so the customer never moves to another channel.
Still need help?
Our team is available Mon–Fri, 10 AM–6 PM MYT (GMT+8).