Tour Enquiry or Inventory Reservation? Make the Status Clear

A tour enquiry is not an inventory reservation. A guest can express interest in a date, provide a party size and discuss a preferred activity without any capacity being held. The answering workflow should make that status clear before the guest plans the rest of their day around it.

If the assistant is collecting enquiries only, say so. If it can perform a booking action through a verified integration, describe only the outcome that the authoritative system actually confirms. A smooth conversation cannot substitute for that record.

Map the operator's real booking stages

Different systems use different labels, so start with the operator's process. Identify when availability is checked, when capacity is held, when payment is required and when confirmation is issued. Do not assume those steps happen together.

Bókun's API reference documents separate reservation and confirmation operations. That is a concrete example of why a request and a confirmed booking should not share the same status label. It does not establish a native Burki connection to Bókun.

Write down what evidence staff would use to prove each stage. An enquiry note, a reservation reference and a confirmation receipt may represent different commitments. The assistant's closing message should match the available evidence.

Collect the details that affect the enquiry

Ask for the activity, intended date, number of participants and any information the operator requires to assess suitability or availability. Keep adult, child or other participant categories aligned with the operator's definitions rather than inventing age bands.

If pickup, accessibility or special arrangements need review, preserve them as questions. Do not promise that the activity can accommodate a request merely because the caller supplied it.

An AI receptionist can be useful at this stage even without inventory access, provided the enquiry reaches a responsible person and the caller understands what remains pending.

A hypothetical family enquiry

A guest asks about a Saturday activity for two adults and two children. They would like pickup and need to know whether the departure works with their later travel plans. The assistant has approved product information but no live inventory or booking permission.

A complete note would include the date, party composition as reported, pickup question and timing constraint. It would ask staff to confirm availability and arrangements. It should not issue a confirmation number or announce that four places are reserved.

If the guest asks whether they should pay now, the assistant should provide only the operator's approved process. It should not improvise a payment link, request card details in a general conversation, or treat a payment attempt as proof of confirmed inventory.

Plan for changed availability

Availability may change between the initial question and staff review. The business should decide how to offer alternatives and who communicates the result. Avoid language that implies the caller's first preference will remain open indefinitely.

For a connected workflow, test a slot that becomes unavailable, a failed write and a response that arrives after the conversation has ended. Each case needs a truthful caller outcome and an operational recovery path.

The phone-call API guide explains the communication layer. Inventory management is a separate business-system responsibility and needs its own integration and acceptance evidence.

Review the final sentence

At the end of a test call, ask a reviewer whether they believe places are held. If the intended outcome was enquiry capture and the reviewer thinks a booking exists, change the wording.

Your next step is to write one approved closing sentence for enquiry received, reservation pending and booking confirmed. Use only the states your actual workflow supports, and verify the corresponding record before letting the assistant speak as if the commitment is complete.