Recalls and continuity
The periodic recall decided by the clinic, rebooking and the waitlist: the owner’s reply is received, and exceptions go up to a person.
Zenvox finds the owner and their animal in Provet, creates the booking, moves it or cancels it. Without access, the request is written into Zenvox.
7 days, 20 answered calls, no card
The request is written into Zenvox: owner, animal, reason, urgency under the clinic’s protocol, workable time ranges. Provet keeps the truth of the record: the receptionist finds the owner and the animal there, creates the booking with the authorised service and the duration, and moves or cancels an appointment under your rules.
On access, two paths: the Zenvox partner path, or the access a clinic requests from the vendor itself. No password is asked of you. Without access, the clinic keeps its software as the single truth, and the receptionist works in your Zenvox app.
Provet separates the client, the patient and the consultation — the same owner and animal split that stops two cats from one household being mixed up; clinical questions go to the team instead of being handled on the phone.
For each action, what the connection does in Provet, with your account permissions.
| Action | What that means |
|---|---|
| Read | Zenvox finds the owner and their animal, and reads consultations, in Provet. It is the first step of every call, because everything else depends on it. |
| Create | Zenvox creates the booking in Provet with the authorised service, the resource, the duration and your account permissions. |
| Update | Zenvox moves an appointment in Provet, told by the software about every addition and change. An update therefore starts from the real state of the record, and one truth holds between the two tools. |
| Cancel | Zenvox cancels the appointment in Provet once, even when the cancellation has to be retried, and the freed slot feeds your recalls. |
Answering, separating owner from animal, applying the clinic’s emergency rule, routing a refill for approval and sending the summary sit in your veterinary base. Follow-up recalls and coordinating a referral between teams are named add-ons. Every add-on is included in the free trial.
Two paths lead to access, and the shorter one differs depending on whether you are one clinic or a group.
Lunch hour, one person on the front desk and already on a call. The second call is taken by Zenvox.
OwnerHi, I am down to two servings of my cat's prescription food. Can I reorder?
ReceptionistLet me take your name, a callback number, and your cat's name. Which product exactly, and how long has she been on it?
ReceptionistI am routing this to the veterinarian for approval. I cannot confirm a refill myself; the clinic gets back to you with the answer.
The request lands filed in the approval queue, with owner, animal, product and reported time on it. The front desk was not interrupted, and the owner gets the answer once the veterinarian has approved it.
The clinic keeps its software as the single truth, and the receptionist works in your Zenvox app.
Yes. The receptionist creates the booking in Provet with the authorised service, the resource, the duration and your account permissions, then confirms it to the owner.
Yes, the vendor allows it, alongside the Zenvox partner path. Zenvox asks for no password and does not sign in on your behalf.
Provet tells Zenvox about every addition and change, and Zenvox takes them into account before moving an appointment. An update therefore starts from the real state of the record, and Provet keeps the record.
No, she records, she does not advise. The veterinarian keeps the clinical decision and the explanation of care, and clinical questions go to the team instead of being handled on the phone.
Its documents stay attached, ready for the receiving team. Sending and accepting are two different things: a referral holds when documents are collected and the receiving team confirms it has taken over.
See the practice concerned, or the full list of connected software.
Provet