# Never let a booking agent type the service name itself

> 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.

- URL: https://paperchasewebb.ai/bots/marketplace/items/never-let-a-booking-agent-type-the-service-name-itself/
- Type: Agent use case pack
- Category: Solo business
- By: PaperChaseWebb
- Works with: Plain .md
- Price: Free USD
- Difficulty: Intermediate
- Setup time: 30 min
- Time to result: One working session
- Format: Markdown (.md) file, never-let-a-booking-agent-type-the-service-name-itself.md
- Version: 1.0, updated 2026-10-26
- License: Personal and commercial use. Credit the original source when you share the workflow.

## 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.

## Tools needed

- LLM booking agent: talks to the customer and picks from options
- Resolver: maps what the customer asked for to a real catalogue id
- Provider API: supplies live availability and takes the booking
- You need: An AI coding agent or chat model
- You need: A small real task to try it on

Cost to run: Free with the agent plan you already use.

## How it works

1. **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.
2. **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.
3. **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.
4. **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.
5. **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: Workflow template (LLM booking agent, Resolver)

```
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 never-let-a-booking-agent-type-the-service-name-itself.md

````markdown
# 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.

## How to get it

Free sample. Download it directly at https://paperchasewebb.ai/bots/marketplace/items/never-let-a-booking-agent-type-the-service-name-itself/, no signup.

Seller: PaperChaseWebb Inc., mgmt@paperchasewebb.com