Vet prescription refill requests, organised for the vet to decide
Refill requests arrive by phone, voicemail, email, web form and pharmacy platforms, and each one needs the patient's history in front of the vet. We build a workflow that collects every request into one queue, attaches the last exam date and current prescription from the PIMS, flags when an exam is due under your policy, routes it to the right vet and updates the owner once a decision is made. The vet decides every refill. A typical build costs $1,000 to $2,200 and takes about four weeks.
The problem
Why refill requests interrupt vets
Refill requests are constant, and each needs a quick but real check: when was the pet last examined, what is the current prescription, has anything changed. Requests written on notes or left in voicemail get lost, owners call back twice, and vets are interrupted mid-consult to look things up.
Prescribing rules also limit what can be automated. In the UK, RCVS guidance requires a clinical assessment and the animal to be under the vet's care before prescribing POM-Vs, with a physical examination normally required for antibiotics, antiparasitics and controlled drugs. In the US, the veterinarian-client-patient relationship is defined in federal rules and state law. A refill workflow can prepare the decision; it cannot make it.
What we build
What our vet prescription refill workflow includes
One refill queue
Requests from web forms, the AI receptionist, email, voicemail transcripts and pharmacy platforms collected and matched to the client and patient.
History attached
Last exam date, current prescription and recent notes pulled from the PIMS and shown with the request.
Exam-due flag
Requests flagged when the last exam is older than your clinic's refill policy allows, so the vet can ask for a visit.
Routing to the right vet
Requests go to the patient's usual vet or the duty vet, with a due time.
Owner updates
Approved, needs an exam or declined messages sent with pickup or delivery details once the vet decides.
Pharmacy hand-off
Approved home-delivery requests passed to your online pharmacy route, such as Vetsource, where it is connected.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Request received
A refill request arrives from any channel.
-
02
Automated
Matched and enriched
The patient, last exam and current prescription are attached from the PIMS.
-
03
Automated
Policy flags
Exam due, controlled drug or other policy flags are added.
-
04
Front desk or nurse review
Nurse prepares
A nurse or technician checks the request and adds anything the vet needs.
-
05
Veterinarian decides
Vet decides
The veterinarian approves, asks for an exam or declines every refill.
How it behaves
How refill requests behave
What the owner sees
- A simple way to request a refill online or by phone
- A message when the vet has decided
- A booking link if an exam is needed first
What staff see
- One queue with history attached to every request
- Exam-due and controlled drug flags
- Requests routed to the right vet with a due time
What the automation does
- Collects and matches requests from every channel
- Attaches PIMS history and policy flags
- Updates owners only after a vet decides
Edge cases and fallbacks
- Request cannot be matched to a patient
- Sent to the desk to identify before it reaches a vet.
- Usual vet is away
- Routed to the duty vet.
- Owner requests a different medication
- Flagged for the vet; nothing is substituted.
- PIMS unavailable
- Requests are queued and staff are alerted to check history manually.
Architecture
Prescription refill routing for a vet clinic at a glance.
- Input
- Logic and services
- Data
- People
- Output
How it flows
- 1 Refill requests from every channel are collected into one queue and matched to the patient.
- 2 The last exam date and current prescription are attached from the PIMS, with policy flags added.
- 3 A nurse or technician prepares the request, then it goes to the right veterinarian.
- 4 The vet decides, and the owner is told whether it is ready, needs an exam or was declined.
Project planner
How the project runs, phase by phase.
Prescription refill requests routed to the vet project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Refill channels, current process, clinic refill policy, PIMS fields and pharmacy routes.
-
02
Design
2 to 3 days
Queue fields, matching, policy flags, routing and owner messages.
-
03
Build
1 to 2 weeks
Intake, PIMS enrichment, flags, routing, owner updates and pharmacy hand-off.
-
04
Shadow run
About 1 week
Requests flow into the queue while staff keep the old process, and we compare.
-
05
Launch
1 to 2 days
Switch on and train nurses and vets on the queue.
-
06
Support
Ongoing
Policy changes and monitoring.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Channels, policy, matching and routing.
$200 – $350
-
Build
Queue, enrichment, flags, routing and owner messages.
$500 – $1,100
-
Integrations
PIMS, inboxes, messaging and pharmacy route.
$150 – $400
-
Testing and shadow run
Side-by-side week with the current process.
$100 – $250
-
Launch and training
Nurse and vet walkthrough.
$50 – $100
-
Total project estimate
$1,000 – $2,200
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. PIMS read access may need vendor enablement. Messaging and n8n are billed to you directly; pharmacy platforms bill under their own terms.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
UK: under care and clinical assessment
RCVS guidance, in force since 1 September 2023, requires a clinical assessment and the animal under the vet's care before prescribing POM-Vs, with a physical examination normally required for antibiotics, antifungals, antiparasitics, antivirals and controlled drugs.
Source: www.rcvs.org.ukUS: veterinarian-client-patient relationship
Federal rules define a VCPR as the vet taking responsibility for medical judgments, having sufficient knowledge of the animal and being available for follow-up, having recently examined it; state laws add their own rules.
Source: www.law.cornell.eduUS: owner confidentiality
Refill messages reveal as little as possible about the animal and its owner, in line with state confidentiality laws such as California's.
Source: www.hipaajournal.comFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Prescription refill requests routed to the vet questions, answered.
Never. It collects, matches and prepares each request. A veterinarian approves, asks for an exam or declines every refill.
That is a clinical and business decision for your practice, within your regulator's rules. We encode the policy you set, such as how recent an exam must be, so every request is flagged the same way.
Yes, through a web form, the AI receptionist or your app, with the request going straight into the queue and the owner told when it is ready.
Approved home-delivery requests can be passed to your online pharmacy route, such as Vetsource, where it is connected to your PIMS. The vet's decision always comes first.
Controlled drug requests are flagged and handled only by your vets under the rules that apply to you. The workflow never messages owners about them without a vet's decision.
Requests per week, time from request to vet decision, share needing an exam and repeat calls from owners chasing refills.
Free 20-minute call
Want this for your veterinary & pet care?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for veterinary & pet care
All servicesVeterinary CRM & new-client pipeline
Capture new-client enquiries from calls, web forms, chat and social into one veterinary CRM pipeline, with quick replies, booking links, front-desk tasks and a monthly report on where new clients come from.
From $1,000 · About 4 weeks Details
Preventive care reminders & post-op check-ins
Vaccination, parasite control, dental and wellness reminders built from your PIMS reminder dates and each pet's status, with follow-ups, a lapsed-patient call list and post-operative check-ins for the nursing team.
From $1,000 · About 4 weeks Details
Veterinary AI receptionist & chat
Answer hours, prices, new-client, boarding and directions questions on your phone line, website or text from approved answers, take booking requests and send anything about a sick animal straight to your team.
From $2,500 · About 5 to 8 weeks Details