Availability and recalls
On the health side: a slot freed by a cancellation is offered to an approved list, and follow-up recalls go out on practice instructions.
GOrendezvous
GOrendezvous tells you when an appointment is booked, changed or cancelled. An outbound event is not an inbound command: the request is written into Zenvox, and your calendar stays in charge.
7 days, 20 answered calls, no card
Where your request lands
The request is written into Zenvox: the person, service type and duration, a preference for a specific therapist, workable time ranges. Your calendar stays in charge: the vendor documents outbound events, and an outbound event is not an inbound command. No third-party write is announced on this page.
Documented access runs through an automation gateway, by private invitation, with a key tied to your business. That gateway documentation is flagged as English-only while the software itself is in French: a real install friction, better planned with your team. Until the invitation is granted there is nothing to install, and the service runs in native mode.
GOrendezvous is a booking product born here, used by allied health practitioners as well as salons and spas; Zenvox answers the call that lands during a treatment and captures service type and duration.
Read, create, update, cancel
The vendor documents outbound events. An outbound event is not an inbound command, and this page keeps that distinction.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | Documented events cover a client added or updated, and an appointment booked, cancelled or moved to another status. They are useful and precise. They assume the private invitation and access key, neither obtained for Zenvox at checking time. |
| Create | Zenvox native mode | No inbound action allowing a booking is confirmed by the documentation. A trigger proves you get told, not that you can write. So the receptionist files the request in Zenvox and texts out your online booking link. |
| Update | Zenvox native mode | Moving an appointment would need that same unconfirmed write. The move is prepared — client identified, service and duration, workable ranges — and carried out by your team inside the software. |
| Cancel | Zenvox native mode | Cancellation, though, reads well: the event exists. That is what makes a waitlist worth having. Writing the cancellation stays with your team, and your cancellation policy is read out exactly as you wrote it. |
What is included, what needs an add-on
Answering, qualifying, stating your cancellation policy, turning away an inappropriate request and handing you everything with the transcript sit inside your base. A connection removes re-keying. Filling a freed slot and bringing back a dormant client are named add-ons, picked depending on whether you run a clinic or a salon.
The authorisation, and what holds the truth
Here authorisation is commercial, not only technical. It gets asked for, and it can be turned down.
- Access rests on a private vendor invitation and a business key; Zenvox asks for no password
- Until that invitation is obtained, the matrix stays exactly as written above, and this page does not change its tone
- Your software stays the system of record for appointments: Zenvox reads a change, it does not decide one
- Gateway documentation is English-only: plan who on your team performs the setup
- You withdraw the key whenever you want; the receptionist returns to native mode and service carries on
A booking was just cancelled inside the software. The receptionist answers the next call; she writes nothing into the calendar.
CallerHi, do you have any room left for a therapeutic massage this week?
ReceptionistLet me take your name and a callback number. Which type of massage and what length would you like, and do you have a therapist preference?
ReceptionistI am also reading out the clinic cancellation policy so it is clear right now. I am passing your request along; the clinic confirms the freed spot.
The clinic gets a request ready to enter: service, length, therapist preference, workable ranges, policy stated. The freed slot finds a taker without anybody calling down a list one name at a time.
When the invitation is not granted
That is today status. The service runs fully in native mode, and your calendar stays in charge.
- The request is created inside Zenvox, qualified and time-stamped
- Your online booking link is texted to the caller
- You find the call, its transcript and its reason in the app
- Inappropriate requests are turned away politely and flagged, with no booking
- No capability in your base depends on the automation gateway
Questions about this connection
Can Zenvox book inside GOrendezvous?
No. No inbound action allowing a booking is confirmed by the documentation: a trigger proves you get told, not that you can write. The receptionist files the request in Zenvox and texts out your online booking link.
What are the events the vendor documents good for?
They say when a client is added or updated, and when an appointment is booked, cancelled or moved to another status. That is what makes a waitlist worth having: the cancellation reads well, even though writing it stays with your team.
How is access obtained?
Through a private vendor invitation and a key tied to your business; the authorisation is commercial as much as technical, and it can be turned down. Until it is obtained there is nothing to install.
Is there an install difficulty to plan for?
One, and it is real: the automation gateway documentation is flagged as English-only while the software itself is in French. Plan who on your team performs the setup.
Does my calendar stay in charge?
Yes, your software stays the system of record for appointments. Zenvox reads a change, it does not decide one, and your cancellation policy is read out exactly as you wrote it.
Where to next
See the practice concerned, or the full list of software studied.
GOrendezvous