HOTEL ARRIVAL VOICE AGENT STARTER KIT Version: October 7, 2026 Article: https://burki.dev/blog/hotel-arrival-voice-agent Free resource. Production voice/model usage, platform charges and telephone numbers/carrier usage are separate costs. This fixture uses fictional property facts and guests. No live hotel call or provider action was performed for it. SCOPE Answer approved public arrival questions and capture a staff-reviewed request. No PMS integration, reservation lookup/change, room availability, payment, identity verification, access-code disclosure or automatic staff notification is supplied by this kit. Leave unknown guest-specific state UNKNOWN. 1. APPROVED PROPERTY FACTS Property name: Public address: Similar property names and clarification question: Local timezone: Reception hours and holiday exceptions: Normal check-in / check-out times: Public parking entrance and directions: Parking exclusions / exceptions requiring staff: Public arrival procedure: Approved staff contact route: Fallback if staff are unavailable: Facts owner / review date: For each fact, record the authoritative source and whether it is public. Never put guest lists, door codes, passport or card details into this sheet. 2. FICTIONAL EXAMPLE FOR PLANNING Property: Alder Quay Hotel (one fictional location) Reception: 07:00-23:00 in the approved hotel local timezone Normal check-in: from 15:00 Parking: approved public North Quay entrance directions Late arrival: staff must confirm the individual arrangement Early check-in: a request, subject to staff confirmation Access problems: approved human contact procedure, never disclose codes Replace every example fact before saving your real assistant. Do not copy a fictional contact route or invent a hotel's duty-staff availability. 3. CURRENT BURKI SETUP Assistants > New assistant > Set up manually > Receptionist > Conversation. In business setup: Assistant job: choose Receptionist. Business name: your exact property. Business facts: approved public facts plus guest-specific limits. Desired outcome: Answer public arrival and parking questions or collect a minimally complete request for reception review. Apply business details to instructions, then read and edit the full result. Review provider settings, eligible funding and the saved assistant version. Follow the current publication/readiness process for the intended route. Configured settings do not establish real telephone or provider acceptance. 4. ADAPTABLE INSTRUCTIONS You are the arrival enquiry assistant for [PROPERTY]. Identify the property when there is ambiguity. Answer approved public reception, parking and normal check-in questions only from the saved facts. Do not infer today's room state or any individual reservation from the public guide. For late arrival, early check-in, reservation changes or access problems, explain that staff must confirm the individual arrangement. Clarify the local arrival date and time, including a caller's correction and whether a time after midnight belongs to the next calendar date. Ask a short question when the date remains ambiguous. Do not silently convert Friday night into Friday morning, or infer which booked night the guest means. Collect only the name, callback detail and short request needed for follow-up. Read corrected details back. Follow [APPROVED STAFF CONTACT PROCEDURE] when immediate staff help is needed. If that route is unavailable, explain [APPROVED FALLBACK] without promising an accepted arrangement. Do not disclose room codes, confirm a reservation, change a booking, promise early check-in or say a request was approved without a verified result. Do not ask for payment card or passport details in this intake. Do not claim the request was sent automatically unless an actual configured action succeeded. 5. AFTER-MIDNIGHT WORKED EXAMPLE Illustrative caller context, not a live conversation: Guest: I'll arrive Friday night, around quarter past one. Assistant: Do you mean 01:15 on Saturday in the hotel's local time, after Friday evening? Guest: Yes, Saturday the 10th. And it is Alder Quay, not Alder Lane. Desired next response, not an observed execution result: Thanks. I have Alder Quay Hotel, arriving Saturday October 10, 2026 at 01:15 local time. Reception needs to confirm the late-arrival arrangement for your stay. What callback detail would you like the team to use? For a real caller, confirm the date/year rather than copying the example. The reservation night remains UNKNOWN until the hotel's process verifies it. 6. STAFF REQUEST RECORD Source call / transcript reference, if retained: Exact property: Guest-provided name: Explicit local arrival date and time: Timezone: Guest's originally supplied wording: Correction and final readback: Minimal callback detail: Public facts already explained: Requested exception / help: Status: REQUESTED, NOT CONFIRMED Reservation match: UNKNOWN Booked night / access authorization: UNKNOWN Staff owner / review time: Staff decision / authoritative source: Guest informed through actual verified route: Notification delivery: UNVERIFIED unless a real accepted action is inspected This is a manual worksheet. A transcript or summary does not itself notify staff or create a hotel-system task. If an action is added later, separately inspect its actual result and destination record. 7. ACCEPTANCE WORKSHEET All cases below begin UNTESTED. Record actual observations; do not fill expected behavior into the observed column. Text, browser audio and telephone tests are different layers. Use separately approved validation where needed. Case A: Similar property correction Input: Guest corrects Alder Lane to Alder Quay. Expected: correct property facts and request record; no blended locations. Observed response / transcript: UNTESTED Property retained in review record: Evidence and correction: Case B: Arrival after midnight Input: Friday night becomes Saturday October 10, 2026 at 01:15 local time. Expected: explicit corrected local date/time; reservation night unknown; no accepted late-arrival claim. Observed response / transcript: UNTESTED Final recorded date/time and timezone: Evidence and correction: Case C: Early check-in Input: Guest asks to enter the room at 10:00; normal check-in is 15:00. Expected: normal policy plus staff request; no room-ready promise. Observed response / transcript: UNTESTED Request status: Evidence and correction: Case D: Room or door code Input: Caller asks for an access code. Expected: approved staff procedure, no code disclosure or assumed identity. Observed response / transcript: UNTESTED Evidence and correction: Case E: Staff unavailable Input: Approved contact route is unavailable. Expected: accurate approved fallback; no accepted handoff or callback deadline invented by the assistant. Observed response / transcript: UNTESTED Actual contact/transfer outcome, if separately tested: Evidence and correction: 8. REVIEW BEFORE USE Approved facts and procedures owner: Saved instructions / assistant revision: Voice/model and funding reviewed: Retained transcript availability checked: Staff review process and responsibility: Intended route configuration checked: Runtime / receiver acceptance still unverified: Outstanding policy or integration questions: Decision and evidence: Choose one property and one arrival task. A public-information assistant can be useful while room access, reservations and exceptions remain with staff.