Availability and recalls
The freed slot is offered to a list the clinic approved, and hygiene recalls follow the practice rule — after inventorying what your software already sends.
Progident
The request is written into Zenvox, attached to one site. Progident keeps its reminders: the patient gets one confirmation, not two, and external access is not established.
7 days, 20 answered calls, no card
Where your request lands
The request is written into Zenvox, attached to one site and in the patient language: identity, reason, urgency, workable time ranges. Progident keeps the truth of the chart, of the multi-practitioner calendar and of its own reminders. External access is not established, so nothing is written there, and the online booking link is the explicit fallback.
The first install rule follows from that. We inventory what your software already sends: confirmation, day-before reminder, hygiene recall. The receptionist slots into what is missing, not on top of what already works — a patient who gets two reminders for one appointment stops trusting either. On external access, the research is blunt: it is not established, and documentation has to be requested per version and per region.
Progident is used in Quebec by independent clinics and by groups; two clinics in one network have patients with the same name, and escalation to another location happens only toward sites you authorised.
Read, create, update, cancel
The status below reflects an access qualification that was not established. It moves only on documentation obtained from the vendor.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | Finding a patient at the right site, reading appointment types and authorised resources are the required operations. External access is not established; it has to be requested per version and per region. |
| Create | Zenvox native mode | While no access is granted, the receptionist books nothing in your software. She prepares the request, attached to the right location and the right language, and texts out your online booking link when one exists. |
| Update | Zenvox native mode | A move commits the chair and the hygienist at the site concerned. It stays with your front desk, which also decides whether a request may migrate to another location in the group. |
| Cancel | Zenvox native mode | A cancellation is taken, time-stamped and passed to the right site with the freed slot. Reminders from your software are not duplicated: the no-duplicate rule is written before go-live. |
What is included, what needs an add-on
Answering overflow and after hours, identifying location and language, telling a new patient from an existing one, applying the emergency protocol and passing it on: that is your healthcare base. Waitlists and coordination across sites are named add-ons.
The authorisation, and what holds the truth
For one practice, one technical rule. For a group, three identity rules. They get written before day one.
- Zenvox asks for no password and does not sign into your software on your behalf
- Messages your software already sends are inventoried before go-live: the patient receives one
- Same-name identities across two locations are not merged; matching is verified per site with an authorised person
- Escalation to another site in the group is limited to locations you explicitly authorised
- The dentist keeps the clinical decision; no firm price and no insurance coverage is confirmed on the phone
Lunch hour, one site front desk is on break and the other line is busy. The call is taken by Zenvox; nothing is written into the software.
PatientHi, I would like to move my cleaning. I think it is at the main street clinic, but I am no longer sure.
ReceptionistLet me confirm your name and date of birth, then check with you which location gave you the appointment — we do not want to mix up two charts.
ReceptionistI am recording your request to move it and your preferred time ranges. The clinic concerned confirms the new appointment; I do not move it myself.
The right location receives a request attached to the right chart, with the patient language and workable ranges. No identity was merged on a name resemblance, and the automatic reminder from the software runs its course with no duplicate.
When access is not granted
That is today status. The online booking link is the explicit fallback, and your software keeps its reminders.
- The request is created inside Zenvox, attached to the site and to the patient language
- Your online booking link is texted out when one exists
- Messages your software already sends stay its own: Zenvox does not double them
- You find the call, its transcript and its reason in the app, per location
- The day the vendor grants access, the matrix changes line by line without redoing your setup
Questions about this connection
Will my patients get two reminders?
No. Messages your software already sends are inventoried before go-live, and Zenvox does not double them. The receptionist slots into what is missing, not on top of what already works.
Does she write into Progident?
No, external access is not established: it has to be requested from the vendor, per version and per region. The request is prepared, attached to the right location and the right language, and your online booking link is texted out when one exists.
Two locations have patients with the same name — how is that handled?
Same-name identities across two locations are not merged: matching is verified per site with an authorised person. No merge happens on a name resemblance.
Can a request move from one location to another?
Only toward locations you explicitly authorised. Each site keeps its rules, its hours and its requests, so requests from one site do not spill into another by accident.
What about the patient language?
It is attached to the request, along with the site, from the call onward. The receptionist answers in French and in English, and that depends on no connection.
Where to next
See the practice concerned, or the full list of software studied.
Progident