Handle inquiries and reservation requests
Review the right type of customer request, check its location and status, and keep responses and private details under control.
Chris Luke
4 min read
Start by identifying what the customer submitted. A contact inquiry, a table reservation, a booking for a bookable Product and a stay are different records. Do not use a table-reservation summary as a complete list of all bookings.
1. Choose the right view
Choose the correct business and open Messages. Contacts, table reservations, product bookings and stays share the business inbox, while their operational records remain distinct. For a direct stay, the guest needs a name and an email address or phone number for a conversation to be created.
A connected assistant uses list_guest_conversations to filter contact, reservation, booking or stay conversations by current/past mailbox and whether attention is needed. It follows every relevant results page, then uses get_guest_conversation with the returned request ID to read the full conversation, proposals and delivery receipts.
For operational lists, use list_product_bookings for product bookings and list_table_reservations for table reservations. Use list_stays and get_stay for a stay’s dates, home and recorded status. The reservation creation window refers to when the request was made, not necessarily the guest’s visit date.
2. Read before taking action
For contact inquiries, check the message, submission time and the customer's preferred contact details. For a table reservation, check the location, visit date and time, party size, requests and stored status. Read the individual record when making a decision; a total or status count is only a summary.
Do not infer a payment, a reply or a new confirmation from the presence of a record. Report the status the system actually returns.
For a stay, check the actual home, check-in and checkout dates, guest party, booking source and recorded payment state. A mapped Airbnb inquiry can have a home without a booked stay. Read get_guest_messaging_context before using private arrival instructions, so you share the right home's details.
Try with your connected assistant
Replace the example business, page and details with your own.
Review recent table reservations
For Harbor Studio, summarize table-reservation inquiries submitted in the last two days, grouped by location and stored status. Include visit dates and party sizes. Omit guest phone numbers and email addresses from the summary. Do not change records or contact anyone.
3. Respond through a supported channel
Review the recipient and exact reply before requesting a send. reply_to_guest saves the reply in the conversation and uses its supported address. Direct conversations use email when an address is available; if a direct guest has no email, they must accept an invitation to the conversation before replies can reach their KrabiClaw inbox. A phone number alone does not enable an email reply. Mapped Airbnb conversations use the connected Airbnb channel even when the guest's email is withheld. Check the current reply_to_guest tool reference and this conversation’s reply controls for supported photo attachments. If the available tool or composer does not support a photo, send it in Airbnb directly.
A draft written in chat has not been sent. For an identical retry, reuse the same operation key so a delivered reply is not sent twice.
Read the conversation again to check the saved reply and delivery result. Report a failed delivery as failed; do not ask the guest to submit another request merely because a response could not be sent.
request_table_reservation_change emails a proposal for a different location, local date, time or party size. The current reservation remains unchanged until the guest accepts. cancel_table_reservation cancels the reservation and releases capacity, but a required refund returns a dashboard handoff before cancellation. Product booking actions use their own tools.
Private arrival-guide fields are not sent merely because they were saved. Share the details deliberately in the correct conversation, or review the home's explicit message schedule and delivery result. See Prepare arrival guides and guest messages.
4. Check reservation availability and alerts
Table-reservation policies are location-specific. A location with no policy does not accept reservations; there is no fallback site-wide policy. To set up or amend a policy, first read the selected location's policy, choose the actual terms and check the resulting guest-facing summary. Do not fill unspecified terms with invented defaults.
Check your notification preferences separately. Seeing a request in the inbox does not prove every team member received an alert. If delivery seems wrong, inspect the request and personal notification settings before asking the guest to submit again.
Read get_reservation_policy before update_reservation_policy, and reuse its current timestamp when changing saved terms. Use create_table_reservation only for the explicitly named guest and actual local date and time. A required deposit returns a dashboard handoff before confirmation.
Next: Manage bookings or update locations and hours. See the current tool reference for the exact inputs and effects. For lodging, set up a home or manage nightly availability and Airbnb.