VETERINARY RECORDS-REQUEST STARTER
Free planning resource for Burki. Checked October 10, 2026.

Administrative scope only. This is a prompt and manual staff-review
worksheet, not an integration, released record or accepted request.
It does not establish diagnosis, care advice, urgency decisions, identity,
release permission, a universal legal deadline or delivery.
Actual model, voice, platform and telephone usage may incur costs.

1. APPROVED PRACTICE FACTS
Practice name / location:
Jurisdiction and owner responsible for reviewing the records process:
Public facts owner / effective date:
Public office hours / timezone:
Approved records-request process:
Actual public submission or staff contact method, if verified:
Minimum caller / pet identifiers approved for initial collection:
Information that must NOT be collected in this starter:
Staff identity and authority verification process:
Staff method for verifying the receiving clinic and destination:
How staff determine permitted release scope:
How staff record actual sending and available delivery evidence:
Approved qualified-staff route for clinical questions:
Retention / access / review permissions:

Leave unverified timing, fees and requirements unknown. Have practice
staff approve the real process before using these facts. Do not insert a
consent rule, chart-access promise or integration because it sounds useful.

2. BURKI SETUP CHECKLIST
Assistant name / identifier:
The creation form has Assistant name and a Business setup section.
Create path: Assistants -> New assistant -> Set up manually -> Receptionist.
Assistant job, where shown: select Receptionist.
Business name: actual practice name.
Business facts: approved public process from section 1.
Desired outcome: explain the process and clarify the intended receiving
clinic and approved request details for staff review.
Apply business details to instructions: review resulting Instructions and
First greeting. GPT Live uses this as guidance and may paraphrase it; it
is not proof of exact wording or first-turn playback. Applying text is not
a save or working phone route.
Create assistant / save existing settings only within authorized setup.
Voice configuration / provider requirements / funding checked:
Actual publication state and route:
Read Publish -> Published version before changes. An unpublished assistant
needs reviewed Publish assistant before real calls. Published telephone calls
use the published version; saved edits remain drafts until Publish saved
changes. Legacy live settings warns that saving changes connected calls.
Knowledge content, provider credentials/policies and calendar availability
remain live. Publication does not verify a phone connection or record release.
Actual publication performed, if any / version / evidence:

The downloadable worksheet is manual. An instruction does not create an
email sender, practice-management integration or automatic staff task.
Do not promise that a request reached staff without an actual result.

3. INSTRUCTIONS TO ADAPT
Help with administrative records-transfer enquiries using the approved
practice facts. Ask only for the minimum request details the practice has
authorized. Treat the caller's identity, relationship and receiving clinic
as caller-stated information until staff verifies them. If the caller
corrects a destination, repeat the latest intended clinic and ask for
confirmation; do not keep the earlier clinic as the intended recipient.
Explain that practice staff must verify the requester, authorize any
release and confirm the correct destination and scope. Do not disclose
chart content, offer clinical advice or decide care urgency. Use the
practice-approved qualified-staff contact route for clinical questions.
Do not say records were sent, delivered or accepted, or that a request
reached staff, unless a separately verified result establishes it.

4. REQUEST WORKSHEET
Conversation / approved evidence reference, if retention is authorized:
Caller-stated name:
Caller-stated relationship to pet:
Minimum pet identifier approved for this request:
What records or purpose the caller requests:
Earlier destination, if corrected (superseded; do not use for sending):
LATEST intended receiving clinic:
Caller confirmation of latest intended clinic:
Caller-provided receiving contact, if operator permits collection:
Contact preference:
Unclear or missing details:
Approved next step explained to caller:
Whether actual submission to staff occurred / evidence:
Staff review owner:

Caller confirmation of the intended clinic is NOT independent destination
verification. Caller-stated ownership is NOT authenticated identity.
Do not insert diagnoses, full histories or unnecessary identifiers here.

5. STAFF-OWNED VERIFICATION AND ACTUAL RELEASE
Requester identity: pending / verified / not established
Date / authorized reviewer / evidence reference:
Requester authority: pending / approved / not established
Date / authorized reviewer / evidence reference:
Correct patient record: pending / established / not established
Date / authorized reviewer / evidence reference:
Receiving contact: pending / independently verified / not established
Date / verification method / evidence reference:
Release scope: pending / approved / not established
Date / authorized reviewer / evidence reference:
Actual records sent: not established / sent
Date / approved sending system / evidence reference:
Delivery evidence, if available: unknown / recorded
Date / evidence reference:
Remaining issue / next owner:

Use the practice's approved system for these records. A conversation
summary is not a substitute for the actual release record.

6. FICTIONAL CORRECTION EXAMPLE
Initial caller request: Send Milo's records to East Practice. I am his owner.
Correction: Sorry, West Practice. East was our old clinic.
Expected readback: West Practice is the intended receiving clinic. Correct?
Caller: Yes. When will they have them?
Expected answer: Staff must review the request, verify the receiving
contact and arrange an authorized transfer. No delivery time established.

Correct worksheet state:
- Latest intended clinic: West Practice, caller-confirmed.
- East Practice: superseded, not the current destination.
- Requester identity / authority: pending staff review.
- Correct patient / receiving contact / release scope: pending.
- Submission to staff / records sent / delivered: not established unless
  separate evidence actually exists.
This is illustrative, not a real patient or completed transfer.

7. EXPECTED VERSUS OBSERVED ACCEPTANCE
Write expected results before any authorized test. Do not invent results.

Case A: East corrected to West
Expected: Latest clinic read back; old destination superseded.
Observed / evidence / next owner:

Case B: Caller says they are the owner
Expected: Caller-stated claim, not authenticated identity or release approval.
Observed / evidence / next owner:

Case C: Caller asks if the records were sent
Expected: No completion claim without actual evidence.
Observed / evidence / next owner:

Case D: Caller asks for clinical chart contents
Expected: No disclosure from this administrative starter; approved staff route.
Observed / evidence / next owner:

Case E: Caller asks a clinical question
Expected: Approved qualified-staff contact process; no care or urgency decision.
Observed / evidence / next owner:

Case F: Receiving contact uncertain
Expected: Staff verification pending; no guessed recipient or email address.
Observed / evidence / next owner:

8. BOUNDED IMPROVEMENT REVIEW
Review period and comparable request cohort:
Actual request count:
Destination corrections missed:
Missing minimum details requiring follow-up:
Requests with staff disposition recorded:
Unknown / unavailable outcomes:
Approved prompt or process change:
Next review date / owner:

Do not turn a national establishment count or a vendor case study into
claimed savings, market demand or a Burki customer outcome.

Article: https://burki.dev/blog/veterinary-records-transfer-request-voice-agent
Commercial context: https://burki.dev/use-cases/ai-receptionist
Current cost review: https://burki.dev/pricing