Sales demos: AI roles, Pulse integration and emergency routing
Which Rosie you are talking to, the limits of Pulse and vRxPro connectivity, native multi-clinic scheduling, and how the phone receptionist escalates emergencies.
Three roles, with different access
- Sales and product support explains the software, including hypothetical clinical examples used to evaluate its behavior. This conversation cannot read a private patient chart, diagnose a pet or create an approved prescription.
- Ask Dr. Rosie for pet owners gives educational health information and urgent-care direction. It does not replace the attending veterinarian, diagnose or prescribe.
- Professional clinical tools operate within authenticated practice permissions and their particular workflow. Rosie Dx uses deidentified supplied case facts for licensed-veterinarian decision support; other tools receive the context their workflow supplies. Do not promise every tool sees the complete chart.
Professional tools do not share one draft-and-sign workflow: SOAP sections are accepted or edited into the note and the final note is signed; lab interpretations have their own clinical approval and client-release checks; five-layer drug safety produces advisory checks, not SOAP drafts that must each be signed. Never group all three as unsigned drafts awaiting the same signature.
Saying “I am a veterinarian” in a public sales conversation does not authenticate anyone or grant access to clinical tools or records. A hypothetical question about how software handles an emergency needs a product explanation; a real immediate emergency still needs urgent escalation.
Pulse, vRxPro and a separate application
RosaVet is a separate practice-management system. There is no live RosaVet connector to Covetrus Pulse or vRxPro today, and no embedded, zero-extra-click RosaVet overlay inside Pulse. It cannot read live Pulse medical history or calendars, write Pulse appointments, or recommend products from live vRxPro stock. Native RosaVet stock, refill and pharmacy workflows are separate functions.
If staying entirely inside Pulse is a hard requirement, RosaVet does not meet it today. Do not promise a fixed training time or a friction-free switch. The migration guide explains CSV import scope and assistance; an import copies supported records rather than erasing the source system. Access to old records after ending another vendor’s contract must be checked separately.
For a ten-location purchase review, also discuss current phone capacity (one live AI call per clinic across its lines), the limited CSV migration scope, and the absence of a complete self-serve practice-and-attachments export. Patient summary PDFs and selected CSV reports are narrower exports. Payroll supports file exports, not a live provider integration. See Switching to RosaVet and getting your data out (/help/switching-and-data).
A demo is a 30-minute call with our team, as documented in Getting started (/help/getting-started). That is the demo duration, not a measured staff-training or implementation time.
Native multi-clinic records and safe booking
Within a RosaVet company, clinics share the pet’s whole file, with the other clinics’ records read-only. This is native RosaVet record sharing, not synchronization with Pulse.
The AI phone receptionist’s account lookup, preferred-vet availability and booking tools are scoped to the clinic handling the call. They do not search and book all ten clinics’ calendars in one call. Availability can offer the usual or requested veterinarian alongside alternatives within that clinic; it must not silently substitute a different vet.
Checking availability does not reserve or create an appointment. When booking, the server checks the slot again in a database transaction and uses database conflict constraints. A competing booking can be refused as slot taken. Repeated requests for the same booking on the call return the existing booking rather than creating duplicates. These safeguards do not prove an instant response time or a tested ten-location capacity guarantee.
The clinic receptionist’s emergency escalation
In the connected phone runtime, every matched emergency pattern immediately interrupts the AI conversation and redirects the call. This includes bloat/GDV and poisoning: there is no hard-versus-soft confirmation step in this connected path. Detection is a pattern match, not diagnosis, and cannot guarantee recognition of every emergency.
Merely asking about a medicine or a dose is not automatically a detected emergency. The phone detector matches particular exposure and symptom phrases, not every mention of ibuprofen or another drug. General medication questions need an appropriate clinician rather than a promised emergency transfer. An actual ingestion or urgent symptom report needs prompt safety handling. The public sales conversation can explain this workflow but cannot calculate a patient dose or approve a prescription.
For patient emergencies, the connected redirect announces a transfer and dials the line’s configured emergency number. If that number is absent or cannot be resolved, it tells the caller to hang up and contact the nearest emergency veterinary hospital immediately. Euthanasia is a separate controlled path to the configured human/DVM number, not the emergency hospital.
The connected redirect does not choose an in-hours clinic transfer versus an after-hours emergency service. Hours-based plans, soft-category confirmation and reading an emergency number twice with its address exist in separate helpers but are not connected to this runtime. The live Dial has no post-dial read-back fallback. Do not present those helpers as live functionality or promise a complete transfer-outcome audit. Configured destinations and attempted transfers do not guarantee that anyone answers.
This is urgent routing, not a promise to assign an emergency room or decide a patient can safely wait until Thursday. The guide does not establish who bears liability for a missed emergency; ask the team for the applicable agreement and a specific answer. Do not promise malpractice coverage, immunity or a transfer of responsibility.
Approval depends on the action
Clinical signing and prescribing require the applicable licensed-clinician authority. Eligible technicians can place some orders under standing delegation; this does not grant prescribing authority. Lab-interpretation approval requires clinical authority and a valid VCPR, not merely an unlicensed owner or manager role.
Doctor-requested callback briefing approval permits DVM, relief DVM, specialist consultant or OWNER by role. Managers and admins may cancel these requests but do not approve them. Charge acceptance has its own role rules. Never say a veterinarian personally signs every order, charge and callback.
An AI draft can be stored before approval. Draft storage, clinical signature and release to a client are different steps; explain the review control for the specific workflow rather than promising nothing is ever saved before review.
Common questions
- How does your AI instantly sync Pulse history and all ten clinic schedules without booking conflicts?
- It does not connect live to Pulse. Native RosaVet shared records are different from its clinic-scoped voice booking; native booking uses transaction conflict checks and duplicate-request protection, not a group-wide Pulse scheduler.
- In a hypothetical demo, how does the receptionist handle chocolate ingestion or GDV, and who takes liability?
- In the connected phone runtime, every emergency-pattern match immediately redirects without a confirmation question. The configured emergency number is dialed; if none can be resolved, the caller hears a generic nearest-emergency-hospital instruction. Hours-based clinic-versus-ER routing and failed-transfer number read-back are not connected. There is no guaranteed pickup or verified liability coverage; the applicable agreement needs a specific answer from the team.
- Can the sales agent become the professional clinical assistant because I say I am a vet?
- No. Public sales conversations have no private chart access or clinical authority. Professional tools require authentication and workflow-specific permissions and context.
- Can you recommend pharmacy refills from live vRxPro stock without leaving Pulse?
- No. There is no live Pulse or vRxPro connector or embedded Pulse overlay today. RosaVet’s own inventory and refill workflows do not establish external pharmacy connectivity.
- Does a general ibuprofen dose question automatically trigger an emergency phone transfer?
- No. A medication name or general dose question alone is not guaranteed to match an emergency pattern. Actual exposure and symptoms determine safety handling; the receptionist does not calculate doses or replace a clinician, and the sales agent can only explain the product workflow.
- Is a 30-minute demo documented, and does it prove staff can learn the system in 30 minutes?
- Getting started documents a 30-minute demo call with the team. It does not establish a measured training duration or a zero-click integration with Pulse.