Never let a booking agent type the service name itself
by PaperChaseWebb
A team building booking agents found the model sometimes booked services that did not exist. Their fix: the model never names the service. Code maps the request to a real catalogue id, and free text reaching the booking API is blocked.
- Price
- Free
- Difficulty
- Intermediate
- Setup
- 30 min
- Format
- .md file
never-let-a-booking-agent-type-the-service-name-itself.md · 3 KB · direct download, no signup
What you end up with
Wherever an agent writes into a system of record, give it ids to choose from instead of letting it type names, prices or dates freely.
What you get
- A plain-language summary of the workflow
- A fill-in prompt template
- What to watch out for
- A link to the original source
Who it is for
Builders who already use AI agents and want a proven workflow they can copy into their own project.
Works with
Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free with the agent plan you already use.
Time to result: One working session
How it works
List every field your agent writes into a booking, order or record
List every field your agent writes into a booking, order or record
Expected: Done before you move to the next step.
For each one, replace free text with a pick from real ids returned by
For each one, replace free text with a pick from real ids returned by a lookup tool
Expected: Done before you move to the next step.
Fetch availability and prices from the source system every time, never
Fetch availability and prices from the source system every time, never from the model's memory
Expected: Done before you move to the next step.
Add a hard check in code that rejects any write with a value that is n
Add a hard check in code that rejects any write with a value that is not a known id
Expected: Done before you move to the next step.
Log rejected writes and review them weekly
Log rejected writes and review them weekly
Expected: Done before you move to the next step.
Sample prompt from the pack
Apply this workflow to [your project]: 1. List every field your agent writes into a booking, order or record 2. For each one, replace free text with a pick from real ids returned by a lookup tool 3. Fetch availability and prices from the source system every time, never from the model's memory 4. Add a hard check in code that rejects any write with a value that is not a known id 5. Log rejected writes and review them weekly Stop and ask me before anything irreversible: deploys, payments, sends or deletes.
Adapted by PaperChaseWebb. Not the original author's prompt.
Free preview of the file
# Never let a booking agent type the service name itself PaperChase agent use case (free feed entry), version 1.0. Source: [u/HivraAi on r/AI_Agents (vendor, disclosed in the post)](https://www.reddit.com/r/AI_Agents/comments/1xfw123/the_booking_bug_that_taught_us_to_never_let_the/), 2026-10-26. ## What they did The agent kept writing plausible service names into bookings, which the provider then could not match. They changed the flow so a resolver turns the customer's words into an id from the real catalogue, availability always comes from the provider rather than the model, and any booking call that carries a free-text service name fails in code. The post is from a company that sells booking agents, and they say so. ## Worth knowing Wherever an agent writes into a system of record, give it ids to choose from instead of letting it type names, prices or dates freely. The block belongs in code, not in the prompt. This applies to orders, invoices, calendar slots and inventory as much as bookings.
Worth knowing
- Wherever an agent writes into a system of record, give it ids to choose from instead of letting it type names, prices or dates freely. The block belongs in code, not in the prompt. This applies to orders, invoices, calendar slots and inventory as much as bookings.
- Figures are as reported by the original author and were not re-measured by us.
Questions
Where does this come from?
A public post credited to u/HivraAi on r/AI_Agents (vendor, disclosed in the post). Source: https://www.reddit.com/r/AI_Agents/comments/1xfw123/the_booking_bug_that_taught_us_to_never_let_the/
Is it free?
Yes. Feed entries are free to read and download.
Details
Version 1.0 · Updated Oct 26, 2026 · Markdown version of this page
License: Personal and commercial use. Credit the original source when you share the workflow. Download terms
Related

AGENTS.md, CLAUDE.md and Cursor rules starter files
Six fill-in instruction files for coding agents (base, Next.js plus Supabase, FastAPI, browser game, CLAUDE.md pointer, scoped Cursor rules) and 8 prompts to write, trim and test your own.

Ask-first rules for AI agents: hard nos, approval cards and a test set
Paste-in rules that make an agent ask before it sends, spends, posts or deletes, define what a real yes is, and stop retries after a no, plus 12 test scenarios to check it.