Prepare a guest-service scheduling handoff
Turn a guest request into a complete scheduling brief before staff confirm an appointment or service.
What you’ll produce
A staff queue showing the requested service, preferred time, missing details, and the department that must confirm it.
Inputs & connections
- Redacted guest service requests and their source IDs
- Approved service hours, scheduling rules, and department contacts
Start with approved message exports. Availability checks require a separately configured scheduling connection. This template does not reserve a slot or contact a guest.
Your starting prompt
Replace the bracketed fields. This is our suggested prompt, not a quote from the source.
Use [guest requests] and [property service rules] to prepare a scheduling handoff. For each request, preserve the source ID and exact requested date or time; extract the service, stated party size, relevant constraints, responsible department, and missing information. Distinguish a guest preference from confirmed availability. Flag ambiguous dates, time zones, and requests outside published service hours. Draft the shortest clarification question needed. Do not book, cancel, send a message, promise a slot, or invent a service price. Return the queue for staff approval.
How to run it
- 01
Choose a small set of historical requests for services your property actually offers.
- 02
Have the responsible department define required fields, service hours, and escalation rules.
- 03
Run the prompt, comparing extracted dates and requirements with the original requests.
- 04
Have staff check the scheduling system and confirm availability before sending any reply.
Review before you act
The service owner checks dates, availability, special requirements, and guest permission before confirming a service.
Limitations & success checks
- The source describes a platform spanning housing and hospitality; it does not prove this exact hotel workflow was deployed.
- A text model cannot know live capacity from a service-hours document or a stale calendar export.
Measure: Missing scheduling details, incorrect date extractions, and back-and-forth messages needed before staff confirmation.
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.
Y Combinator describes Conduit agents for leasing, onboarding, scheduling, and retention with human handoff. This service-scheduling checklist is an editorial adaptation of that broader announcement, not a tested Conduit setup or a claim of achieved savings.
Creator / publisher: Y Combinator
Editorial review: 2026-10-12. How we label evidence.