Availability and recalls
Reuse a slot that just opened up, keep a waiting list on the criteria you approve, and chase a follow-up. The connection hands over the open time; the add-on decides what to do with it.
Google Calendar
The appointment is written into the calendar you designate, and the authorisation can be pulled back in one move. With no connection, it is written into the native agenda in your workspace.
7 days, 20 answered calls, no card
Where your appointment lands
The appointment is written into the calendar you designate — the receptionist can write into a calendar created for it rather than into your personal agenda, which makes pulling the authorisation back a clean, painless decision. With no connection, it is written into the native agenda in your workspace, which already carries your resources, your durations, your buffers and your time zone.
Access goes through an authorisation you grant from your own account, at the narrowest scope that still does the job: no key to create, no connector to program. The vendor’s official documentation was read end to end; no authorisation has been installed from Zenvox yet, and no run has been done on a live account.
Small businesses here run their whole schedule out of one shared calendar. A calendar holds dates and events; it does not hold your floor plan, your class credits, or the rule that says one treatment chair cannot serve two people at once.
Read, create, update, cancel
The status below is the technical qualification as of the last check. The vendor's official documentation was read end to end; no authorisation has been installed from Zenvox yet, and no run has been done on a live account. A status changes when an authenticated test changes it, and not before.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | Reading the events and checking the open time on the calendars you select are both documented, and they are separate rights from the right to write. That is what makes a careful first step possible: the receptionist looks and proposes, and touches nothing. |
| Create | To qualify | Inserting an event into an authorised calendar is documented. Every write carries a stable identifier tied to the action, so a call that gets resumed after a dropped connection does not end up creating two appointments under the same name. That behaviour has to be proven on a live account before we announce it. |
| Update | To qualify | Moving an existing event is documented. The two situations that make two calendars drift apart are known and still untested: rebuilding the sync from scratch once the vendor reports that a tracking token has gone stale, and renewing the subscription to change notifications. |
| Cancel | To qualify | Deleting or cancelling an authorised event is documented. The case that still needs proving runs the other way: an appointment erased by hand in the calendar has to make it back down to the receptionist, or she keeps treating it as live. A booking written in one block across two systems at once is not assumed here. |
What is included, what needs an add-on
Answering, qualifying and booking a visit into the slots you authorise is part of your base, together with one calendar or system of record. So the connection does not unlock booking: it only decides WHERE the appointment lands, and it saves you from writing it down twice. What sits above that line — re-offering a slot that just opened, calling back a client nobody has seen in a year, filling a last-minute hole — belongs to named add-ons, with or without a connection.
The authorisation, and what holds the truth
A connection is granted, reviewed and revoked. These six points are what make an installation clean, and they are written here because they concern you, not because they are technical.
- You authorise from your own account, and your password does not go through Zenvox
- The rights are separate: seeing your open time is not the right to write in your calendar, and you can grant one without the other if you would rather start carefully
- The receptionist can write into a calendar created for it instead of yours, so your personal appointments stay out of reach
- One system holds the truth for the appointment: the calendar you chose carries the event, and Zenvox carries the rules of your trade
- If records software already owns the appointment, that software holds the truth; the calendar is only a mirror of it, and a mirror grants no right to write back
- You revoke the authorisation from your own account whenever you decide to, and the receptionist falls back on the native agenda without an interruption
Ordinary use of the vendor's interface is announced at no surcharge. The vendor has said it will bill heavy use later in 2026: that is their rule, we watch it, and we name it here rather than letting you discover it.
An esthetics salon with three chairs. The whole schedule lives in one shared calendar. Reading the open time is authorised; writing is still being qualified, so the receptionist proposes and has the owner confirm.
ClientHi, I would like to book an appointment for colouring.
ReceptionistHappy to. Let me take your name and a number to reach you on first. Is this your first time having it coloured here?
ClientYes, first time.
ReceptionistGood to know. For a first colouring we ask for a patch test 48 h ahead — I am writing that down. I have open time Thursday afternoon and Saturday morning. Which one works better for you?
The slot is held, the patch test is written into the request, and the owner gets the summary by text with the confirmation to give. The price is not improvised over the phone: the receptionist quotes the posted menu and stops there.
If the connection is not there
A missing connection blocks no booking at all. The receptionist works on the native agenda in your workspace instead, which already carries your resources, your durations, your buffers between appointments and your time zone.
- The appointment is taken in your workspace, with the same qualification questions and the same text confirmation
- You see it in the app on your phone, with nothing else to install
- You copy it into your calendar if you feel like it, or you leave it where it is
- The day the connection is qualified, it is added on top without redoing your setup or moving the appointments you have already taken
Questions about this connection
Will the receptionist see my personal calendar?
She can write into a calendar created for her rather than into yours, and your personal appointments stay out of reach. That is also what makes pulling the authorisation back a clean, painless decision.
Do I have to grant write access right away?
No: seeing your open time and writing in your calendar are two separate rights, and you can grant one without the other if you would rather start carefully. The receptionist looks and proposes, and touches nothing.
Two appointments under the same name after a dropped call — is that possible?
That is what the stable identifier tied to the action is there to rule out, and the behaviour has to be proven on a live account before we announce it. Inserting an event into an authorised calendar is documented.
What if I erase an appointment by hand in the calendar?
That is the case still to prove: the deletion has to make it back down to the receptionist, or she keeps treating it as live. A booking written in one block across two systems at once is not assumed here.
Does the connection unlock booking?
No: it only decides where the appointment lands, and it saves you from writing it down twice. With no connection it is written into the native agenda in your workspace, which already carries your resources, your durations, your buffers and your time zone.
Is use of the interface billed?
Ordinary use is announced at no surcharge by the vendor, which has said it will bill heavy use later in 2026. That is its rule, we watch it, and we name it here rather than letting you discover it.
Where to next
See how booking behaves during the call, look at the other calendar on the same journey, or open the full software list.
Google Calendar