Qualify an after-hours booking inquiry

What you’ll produce

A structured inquiry containing dates, party size, property preference, and a next-action draft.

Inputs & connections

• Booking inquiries from approved channels
• Booking-engine links and reservation policies

Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.

Replace the bracketed fields. This is our suggested prompt, not a quote from the source.

Read [inquiries] for [hotel group]. Extract requested dates, adults and children, room requirements, property preference, and stated special requests. Mark absent values unknown and suggest the fewest questions needed to proceed. Provide an official booking link where relevant. Do not invent rates, room inventory, or a reservation confirmation. Produce a staff review queue and an unsent reply draft.

How to run it

1. 01

   Define the fields reservations needs to handle an inquiry.

2. 02

   Use historic examples to check date ambiguity and party-size extraction.

3. 03

   Add read-only booking access only if its permissions and failure behavior are clear.

4. 04

   Route unresolved or policy-sensitive cases to reservations on opening.

Limitations & success checks

• A drafted reply is not a booking.
• Date formats, time zones, and special requirements need explicit checks.

Measure: Complete inquiries received, incorrect field extractions, and unresolved handoffs.

Sources & attribution

The sources below support the reported example or a tool capability. They do not validate our prompt or prove the outcome in your environment.

Editorial review: 2026-10-11. How we label evidence.