Recalls and continuity
The periodic recall the clinic decided goes out on your instructions, the owner reply is received, and exceptions go up to a person.
Owner and animal are two separate objects, and the request is written into Zenvox carrying both. At ezyVet, access needs a partnership or a private integration.
7 days, 20 answered calls, no card
The request is written into Zenvox: owner, animal, species and breed, reason — exam, vaccines, a health problem, a refill, an emergency. ezyVet keeps the truth of the animal record. A prescription or food refill is captured and routed into the veterinarian approval queue; it is not confirmed on the phone, and nothing is written into the software while no access is open.
Access has two documented routes: a commercial partnership for wide distribution, and a private integration for a single organisation. Fees, client minimums and licensing remain to be confirmed — nothing here should be assumed free. Worth naming: the clinic screen is richer than some interface surfaces, and seeing a feature does not prove it can be driven from outside.
ezyVet holds the owner, the animal, the consultation and billing for small animal clinics and emergency hospitals: here contact and patient are two separate objects, because one household often has several animals.
The status below comes from vendor documentation and from what stays open: account access, fees and transaction trials.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | Appointments read through a delta on the last-modified timestamp, and appointment scopes are visible. The route is described; account access and a sandbox still have to be obtained before it gets announced. |
| Create | To qualify | Creating an appointment has to be proven endpoint by endpoint, with full validation: species, authorised service, resource and duration. Until that test happens, the receptionist prepares the request and the clinic enters it. |
| Update | To qualify | Updating carries the same dependency. It is even more sensitive in an emergency hospital, where a calendar alone reflects neither kennels nor the on-call team: moving an appointment is decided at the clinic. |
| Cancel | To qualify | Cancelling touches the approved estimate and billing. Until it is proven, a cancellation is taken, time-stamped and passed on, and the freed slot feeds your recalls — with no automatic write. |
Answering, separating owner from animal, applying your emergency rule, routing a refill for approval and sending you the summary all sit in your veterinary base. A connection removes re-keying, it unlocks nothing. Vaccine recalls, referrals between teams and mobile rounds are named add-ons.
Two access routes, two different conversations. Picking the right one avoids paying for scope you will not use.
A weekday evening, the clinic is closed and the line is answered by Zenvox. Nothing is written into the software.
OwnerMy dog ate chocolate about an hour ago, I do not know what to do.
ReceptionistLet me take your name, your number and your dog name. For an ingestion like that, go straight to the emergency veterinary hospital or call the on-call line — I cannot assess how serious it is.
ReceptionistI am sending your call through to the clinic right now with what you just told me, word for word, and the time of the ingestion.
The team gets the alert with owner, animal, timing and the words the owner used, no interpretation added. No ordinary appointment is booked on top of an emergency: that is the veterinary preset rule, and it holds whether a connection exists or not.
The clinic keeps its software as the single truth, and the receptionist works in Zenvox native mode.
Not today. Creating one has to be proven endpoint by endpoint, with full validation — species, authorised service, resource and duration. Until that test happens, the receptionist prepares the request and the clinic enters it.
No. It is captured and routed into the veterinarian approval queue, with owner, animal, product and reported time on it. Nothing is promised to the owner that the veterinarian has not approved.
Because one household often has several animals, and contact and patient are two separate objects on file. The request is written with both, along with species, breed and reason.
A private integration targets one organisation: that is the route for a clinic or hospital connecting its own account. A commercial partnership targets distribution, where fees, client minimums and licensing get discussed and remain to be confirmed. Nothing here should be assumed free.
No, that is the veterinary preset rule, and it holds whether a connection exists or not. In an emergency hospital a calendar alone reflects neither kennels nor the on-call team, and moving an appointment is decided at the clinic.
See the practice concerned, or the full list of software studied.
ezyVet