The RCVS Under Care Line: The UK Vet Practice Messaging Stack That Actually Fits

The five rulebooks a UK vet practice actually meets when it turns on client messaging

The day a UK small-animal veterinary practice switches on any digital client-messaging system — a purpose-built vet-comms platform, a WhatsApp Business API integration, or an informal WhatsApp thread — five separate rulebooks come into play. The RCVS Code of Professional Conduct at rcvs.org.uk sets what a Registered Veterinary Surgeon can and cannot do professionally, including the boundaries on remote advice and referral. The RCVS Under Care guidance (rcvs.org.uk/setting-standards/advice-and-guidance/code-of-professional-conduct-for-veterinary-surgeons/supporting-guidance/under-care/) — refreshed in 2023 with staged implementation — governs when a vet can prescribe POM-V medication after a remote consultation and when a physical examination is required. The Veterinary Medicines Regulations 2013 (legislation.gov.uk/uksi/2013/2033), enforced by the Veterinary Medicines Directorate (gov.uk/government/organisations/veterinary-medicines-directorate), sets the categories and prescribing rules for animal medicines. Professional indemnity via the Veterinary Defence Society (thevds.co.uk) sits underneath every consultation and every message — the VDS's position on informal or WhatsApp-based advice shapes practice-level policy. And UK GDPR plus PECR, interpreted by the ICO at ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications, controls both client-data handling and any WhatsApp broadcast that constitutes marketing. Every section below picks one of these five threads.

Why 'Bird alternative' is the wrong lens for a UK vet practice

Bird (formerly MessageBird) is a CPaaS — Communications Platform as a Service — built for enterprise engineering teams that need programmable messaging APIs across WhatsApp, SMS, email, and voice. Pricing is per-message and per-service, engineering effort is required to stitch it into a practice's operational systems, and the value it delivers scales with in-house developer capacity.

A UK vet practice does not have that shape of problem. Clients are not API events — they are the primary safeguarding contact for their animal, the counterparty on a paid consultation, and often the person whose informed consent is legally required before treatment or medication. What a UK vet practice actually needs sits at the intersection of three tools:

• A practice management system (PMS) that holds the animal record, clinical history, consent forms, dispensing log, prescription record, and invoicing.
• A vet-comms platform or a WhatsApp BSP that carries appointment reminders, vaccination-due nudges, dispensing-ready alerts, and two-way client questions.
• A consent and record-keeping workflow that keeps every clinical decision documented against the RCVS Code and the VMR 2013 requirements.

The realistic UK-market shortlist:

• Purpose-built vet-comms platforms with UK adoption: PetsApp (petsapp.com, UK-origin), Vetstoria (vetstoria.com, UK-founded, now global). Both purpose-built for the vet workflow — appointment booking, reminders, in-app messaging tied to the PMS.
• UK-common vet PMS platforms: Merlin (merlin-management.com), VetIT (vet-it.com), Provet Cloud (provetcloud.com), IDEXX Cornerstone (idexx.co.uk), Vetter (vetter.io). Each has different depth on clinical, dispensing, and lab integration.
• WhatsApp BSPs as a client-messaging rail: WATI, Respond.io, Callbell — supplementary to the PMS and vet-comms platform, not a replacement.

Bird's role in a UK vet stack is narrow: usable at a chain-scale operator with in-house engineering capacity that wants a programmable messaging API. For an independent 4-vet practice, purpose-built vet-comms plus the PMS is a materially better fit.

The RCVS Code, the Under Care rule, and the WhatsApp prescription every UK vet must not send

The RCVS Code of Professional Conduct at rcvs.org.uk sets what a Registered Veterinary Surgeon can and cannot do professionally. The Under Care supporting guidance (rcvs.org.uk/setting-standards/advice-and-guidance/code-of-professional-conduct-for-veterinary-surgeons/supporting-guidance/under-care/), refreshed in 2023 with staged implementation, is the specific rulebook governing when a vet can prescribe POM-V (Prescription Only Medicine – Veterinarian) medication after a remote consultation and when a physical examination is required. This is the single biggest RCVS-compliance decision in any UK vet WhatsApp workflow.

Core Under Care principles:

• Prescription of POM-V typically requires the vet to have carried out a physical examination of the animal, or to have assumed responsibility on the basis of a recent physical examination — the Under Care guidance sets the specific conditions and exceptions.
• Remote consultation can support a wider range of advice-giving and follow-up work, but its role in initial POM-V prescribing is limited under the current guidance.
• Repeat prescriptions may be issued remotely where the vet has an established Under Care relationship and the conditions of that relationship remain met.
• Antimicrobials and controlled drugs have additional prescribing controls beyond the general POM-V rules.

Where WhatsApp workflows walk into an Under Care issue:

• A vet replying to a WhatsApp message with a specific POM-V product recommendation for an animal the vet has not examined is issuing a de-facto prescription without the physical-examination basis.
• An automated WhatsApp reply template that suggests 'try [POM-V product name]' for a described symptom is a prescription-by-template.
• A WhatsApp thread with a client about a new symptom that ends with 'come in and we can dispense X' is fine if the vet then examines the animal and issues the script; it is not fine if the practice dispenses without the examination.
• A repeat-prescription request handled purely by WhatsApp is defensible if the Under Care relationship is documented, current, and reviewed at the intervals the guidance sets.

Safe pattern for WhatsApp intake:

• Route symptom questions to a real appointment (in-person, video-based remote consult, or in-clinic examination) rather than a template that recommends medication.
• Repeat-prescription requests routed to the vet who holds the Under Care relationship, with a documented review process.
• Automated messaging templates cleared with the responsible vet against the Under Care guidance before deployment.
• Client-facing FAQ that names 'we cannot prescribe without an examination' rather than an implicit template that appears to do so.

Veterinary Medicines Regulations 2013, POM-V categories, and messaging templates that stay compliant

The Veterinary Medicines Regulations 2013 (SI 2013/2033) at legislation.gov.uk/uksi/2013/2033, enforced by the Veterinary Medicines Directorate (gov.uk/government/organisations/veterinary-medicines-directorate), classify animal medicines and set the prescribing controls. The four categories UK vet practices work with:

• POM-V (Prescription Only Medicine – Veterinarian): can be prescribed only by a veterinary surgeon following a clinical assessment of the animal under their care.
• POM-VPS (Prescription Only Medicine – Veterinarian, Pharmacist, SQP): can be prescribed by a vet, a pharmacist, or a Suitably Qualified Person (SQP).
• NFA-VPS (Non-Food Animal – Veterinarian, Pharmacist, SQP): non-prescription but supply-controlled by a vet, pharmacist, or SQP.
• AVM-GSL (Authorised Veterinary Medicine – General Sales List): general sale.

Messaging patterns that stay compliant:

• Reminder-of-repeat-prescription for an existing Under Care relationship: 'Your pet's [flea/worm/general] treatment is due — we can arrange dispensing at your next collection or delivery' is fine.
• General advice on AVM-GSL products ('over-the-counter wormers are available at any pharmacy'): fine.
• Post-examination follow-up ('The medication we dispensed yesterday should be given morning and evening — reply here with any questions'): fine.
• Vaccination-due reminder: fine.
• Dispensing-ready alert for an already-issued prescription: fine.

Messaging patterns that create a VMR 2013 or Under Care issue:

• An auto-reply that recommends a specific POM-V product for a described symptom without a clinical assessment.
• A template that suggests changing dose, duration, or product without vet review.
• A client-facing 'ask the AI vet' surface that answers medication questions with product recommendations.
• A repeat-prescription auto-issue for a client whose Under Care relationship has lapsed without review.

RCVS Practice Standards Scheme (PSS) accreditation at rcvs.org.uk/setting-standards/practice-standards-scheme/ has specific standards on dispensing, prescription record-keeping, and client communication — WhatsApp workflows should be audited against the practice's PSS accreditation level.

VDS practice-standards guidance and the insurance implication of informal WhatsApp advice

The Veterinary Defence Society (VDS, thevds.co.uk) is the mutual professional indemnity provider that insures most UK vets and vet practices. Its Risk Management team publishes practice-level guidance on record-keeping, consent, and client communication — including on remote consultation and messaging channels.

Where VDS positioning shapes practice-level policy:

• Every clinically-relevant conversation is a record. VDS guidance is consistent that clinically-relevant client contact needs to be in the patient record — including WhatsApp threads about symptoms, medication questions, or treatment response. Free-text messages in a manager's personal WhatsApp are not a defensible record on a claim.
• Informal 'quick advice' is a risk vector. The pattern where a client messages a familiar vet or nurse for informal advice outside a paid consultation creates a duty-of-care question without the corresponding examination, consent record, or fee. A vet who advises via WhatsApp on a symptom they have not examined and where the animal deteriorates has an exposed insurance position.
• Consent documentation. For any treatment or medication, informed consent needs to be documented. A WhatsApp thread that ends with 'yes go ahead' from the client can support the consent record only if it is preserved and imported into the PMS — not left on a phone that can be lost or wiped.
• After-hours cover. Out-of-hours (OOH) messaging via WhatsApp — where the client contacts a familiar vet outside official OOH provision — creates a personal-liability question that VDS guidance addresses directly. The safe pattern is OOH contact via the practice's official OOH provider (or the practice's own OOH channel) with clinical decisions logged against the OOH provider's record.

Safe practice patterns for WhatsApp under VDS-aligned standards:

• All clinically-relevant WhatsApp messages exported or synced into the PMS as part of the patient record.
• Practice policy on informal 'friend and family' vet advice — usually a written prohibition on giving clinical advice outside a formal consultation.
• Consent documented in the PMS, not just in a chat thread.
• OOH questions routed to the practice's official OOH cover, not to individual staff personal numbers.
• Staff BYOD (Bring Your Own Device) policy covering WhatsApp use for client contact — usually a prohibition on personal-number use with clients.

The UK-market vet-comms and PMS platforms that actually fit RCVS documentation

Two overlapping software categories: vet-comms platforms that carry client messaging, appointment booking, and reminders; and practice management systems (PMS) that hold the animal record, clinical history, dispensing log, and invoicing. Most UK practices run one of each, integrated.

UK-market vet-comms platforms:

• PetsApp (petsapp.com) — UK-origin, purpose-built for vet-client communication. Appointment booking, in-app messaging, video consultation, payment collection. Strong integration path to UK PMS platforms.
• Vetstoria (vetstoria.com) — UK-founded (now global) online appointment booking. Deeper on booking than messaging, but integrates with WhatsApp workflows through partners.

UK-common PMS platforms:

• Merlin (merlin-management.com) — UK-common independent PMS.
• VetIT (vet-it.com) — UK-origin PMS.
• Provet Cloud (provetcloud.com) — Nordic-origin cloud PMS with UK adoption.
• IDEXX Cornerstone (idexx.co.uk) — global PMS with strong UK footprint, particularly at multi-site groups.
• Vetter (vetter.io) — modern SaaS PMS.
• RxWorks / VetIT / Ascend (from IDEXX and other providers) — used at UK groups.

Chain-level PMS at UK corporate groups (CVS, IVC Evidensia, Vets4Pets, Medivet, Linnaeus): often a group-standard IDEXX Cornerstone or a bespoke enterprise deployment.

What to check on the shortlist:

• Under Care documentation — the PMS can hold the physical-examination record that supports an Under Care relationship, and its search surface lets the vet check current Under Care status before responding to a repeat-prescription WhatsApp.
• Dispensing log — full VMR 2013 record with batch numbers, expiry dates, and prescription linkage.
• Consent documentation — treatment consent, sedation consent, image-use consent stored per-purpose and per-patient.
• RCVS Practice Standards Scheme compatibility — the PMS supports the record-keeping standards required by the practice's PSS accreditation level.
• Integration with vet-comms platforms — PetsApp, Vetstoria integrations pre-built rather than bespoke.
• UK GDPR / hosting / DPA terms — UK or EU data residency preferable; if outside, check the transfer mechanism.

Where a WhatsApp BSP fits at a UK vet practice — and where it can't replace the PMS

A WhatsApp Business API deployment via a Business Solution Provider is a supplementary client-messaging rail. It does not replace the PMS or the vet-comms platform. Where it earns its place at a UK vet practice:

• Clients who prefer WhatsApp over a proprietary vet-comms app. Some clients will never install PetsApp; a WhatsApp Business API number gives them a channel they will actually read.
• Vaccination-due nudges for the practice's client list — a broadcast that hits WhatsApp read rates well above email.
• Dispensing-ready alerts — the client's ordered medication is ready for collection.
• Post-consultation follow-up — a check-in the day after a procedure.
• Fee-reminder follow-up — email carries the invoice, WhatsApp carries the light reminder a few days before due.

BSP options with UK relevance:

• WATI (wati.io) — SMB-tier WhatsApp Business API platform. Growth pricing sits in the USD 40–50 per month range on monthly billing; Meta per-conversation charges pass through on top.
• Respond.io (respond.io) — omnichannel (WhatsApp, Instagram DM, Facebook Messenger, SMS, email).
• Callbell (callbell.eu) — EU-hosted (Italy). EU jurisdiction hosting simplifies UK GDPR analysis.
• 360dialog (360dialog.com) — Germany-based direct BSP with pay-per-conversation pricing (Meta rates plus platform margin, no monthly SaaS floor). Efficient at higher volume; no bundled inbox.

Meta's official BSP directory at business.whatsapp.com/partners is the source of truth for approved providers.

What a WhatsApp BSP cannot do for a UK vet practice:

• Hold the animal clinical record.
• Model POM-V dispensing with batch numbers, expiry dates, and prescription linkage.
• Track Under Care relationships and physical-examination dates.
• Handle RCVS Practice Standards Scheme record-keeping.
• Route clinical concerns through the vet's assessment workflow.

All of that lives in the PMS. The BSP is a channel, not a record.

Cost model for a 4-vet UK SMB practice

Realistic monthly stack cost for a UK 4-vet independent small-animal practice running full appointment schedule, dispensing log, and weekly client broadcasts (all figures should be verified on live vendor pricing pages before committing):

Platform layer:

• Practice management system (Merlin, VetIT, Provet Cloud, IDEXX Cornerstone or equivalent): typically £150–£500+ per month for a 4-vet practice, often priced per-user or per-site. Largest single line item; covers clinical, dispensing, invoicing, and client record.
• Vet-comms platform (PetsApp or equivalent): typically £100–£300 per month for a 4-vet practice on a mid-tier plan.
• Optional WhatsApp BSP (WATI, Callbell, Respond.io): £25–£100 per month for clients who prefer WhatsApp.
• Payment processing (Stripe, GoCardless): standard per-transaction fees (1% capped for GoCardless direct debit; 1.4-2.9% for Stripe cards).

Meta per-conversation fees. WhatsApp Business Platform charges per 24-hour conversation window per user by category at developers.facebook.com/docs/whatsapp/pricing. The UK sits in the higher-cost European pricing band. Utility conversations (appointment reminder, vaccination-due nudge, dispensing-ready alert) are cheaper than marketing conversations (new-service launch, seasonal promotion). Service conversations in the customer-initiated 24-hour window are free.

Integration overhead. Zapier or Make.com to bridge the PMS, vet-comms platform, and WhatsApp BSP where no native connector exists: £20–£50 per month.

Total monthly stack cost: £150–£500 (PMS) + £100–£300 (vet-comms) + £25–£100 (WhatsApp BSP) + £20–£50 (integration) = £295–£950 per month, before Meta per-conversation fees and payment-processing fees.

Offsetting benefit: admin time reclaimed on appointment reminders, vaccination-due follow-up, dispensing-ready alerts, and fee chase — typically 15–30 hours per week at a 4-vet practice — plus a documented, RCVS-inspection-ready record that a paper-and-personal-WhatsApp system cannot deliver. VDS-aligned record integrity in the PMS itself materially reduces insurance-claim risk on any dispute.