Design how chat requests reach a booking system

Text exercise: Provide fictional bookings, resources and booking rules. Draft the field mapping and state tests between chat and the system.

Execution environment and usage

AI / software

Text chat (ChatGPT, Claude or Gemini)

Where to operate

Text chat such as ChatGPT, Claude or Gemini, adapted to supplied inputs

Getting started

  1. For example, open claude.ai and start a new chat where the location, account and usage conditions permit.
  2. Paste the prompt below and its de-identified text inputs. Provide fictional bookings, resources and booking rules.
  3. Check the output against the original inputs; a draft does not connect or operate the original automation service.

Setup and plan requirements

Complete authorized text, synthetic records, field definitions or rules specified by the exercise. This chat route uses already-obtained text or excerpts. Later checks of pages, files or test results require separate human inspection; mark missing results unverified.

Prompt portability limits

Portable as an adapted draft/analysis exercise, not equivalent functionality or output to the original automation.

Usage limitations

Historical stack: n8n + conversational intake + deterministic booking backend + state storage. Not hands-on tested. Check current version, plan, regional and integration permissions; a prompt does not configure the workflow.

Environment sources

適用情境 / When to use

Provide fictional bookings, resources and booking rules. Draft the field mapping and state tests between chat and the system. This design adaptation does not build a complete n8n booking workflow or handle real reservations. The author reports errors when the model handled the logic directly.

步驟 / Steps

  1. Prepare fake bookings, resource lists, time zones, opening hours and booking rules.
  2. Define intent and field contracts, clarifying ambiguous times before rule checks.
  3. Test conflicts, duplicate requests, updates and cancellations; confirm only explicit results.

提示詞 / Prompt

Design a conversation-to-booking field contract using [synthetic records/resources/booking rules]. Specify clarification, conflict, success and failure states, with rule-based availability rather than model guesses. Plan duplicate-request and update tests. Output a sandbox design only; do not create, change or cancel real bookings.

留意事項 / Cautions

  • Never let the model invent booking IDs or availability.
  • Tests must not use real customers or production calendars.

來源限制 / Evidence limits

No independent reliability testing establishes protection against double bookings.

流程說明 / Workflow note

These steps and prompts are original, untested exercises by this site, not the author’s verbatim workflow. Reported results do not guarantee exercise outcomes.

原始工具組合 / Original tool stack

n8n; conversational agent; booking workflow; Google Sheets

Source checked: 2026-10-20

Separating conversation from logic in an n8n booking workflow