---
name: al-560-never-let-your-ai-say-booked-until-it-s-really-on-the-cal
description: "An AI that answers messages and takes bookings can fail quietly. Charleston AI's Nov 1, 2026 write-up describes a five-person oyster roast caterer in Awendaw, SC, whose Meta Muse agent kept quoting, collecting deposits and telling customers they were booked for five weeks after a password change silently broke its calendar connection; it was also still quoting last season's $34 a guest instead of $38. By the time he noticed, 23 deposits sat against a calendar that knew about 14, one Saturday held three roasts for a rig that can run two, and 19 bookings were priced low. The fix: the agent writes each roast to the calendar, reads it back, and only then says 'booked'; if a write fails it stops taking deposits and texts him; every morning at 6 it tests each connector; and the price lives in one sheet he edits, not in its instructions. It never books more than two roasts a day and never refunds, discounts or handles complaints. On Oct 28 the morning test caught an expiring payment…"
---

# Never let your AI say 'booked' until it's really on the calendar: have it write each booking, read it back, and only then confirm, test every connection each morning, and stop taking deposits the moment one breaks

An AI that answers messages and takes bookings can fail quietly. Charleston AI's Nov 1, 2026 write-up describes a five-person oyster roast caterer in Awendaw, SC, whose Meta Muse agent kept quoting, collecting deposits and telling customers they were booked for five weeks after a password change silently broke its calendar connection; it was also still quoting last season's $34 a guest instead of $38. By the time he noticed, 23 deposits sat against a calendar that knew about 14, one Saturday held three roasts for a rig that can run two, and 19 bookings were priced low. The fix: the agent writes each roast to the calendar, reads it back, and only then says 'booked'; if a write fails it stops taking deposits and texts him; every morning at 6 it tests each connector; and the price lives in one sheet he edits, not in its instructions. It never books more than two roasts a day and never refunds, discounts or handles complaints. On Oct 28 the morning test caught an expiring payment connector, and since the fix 38 roasts were booked, each on the calendar before the customer heard 'booked'. The write-up comes from the AI firm that did the fix. The same guardrails fit any agent that books showings, viewings, appointments or jobs.

## Inputs to collect first
Ask the user for anything below that they haven't already given you. Don't guess missing facts.

- Sheet name
- Calendar

## Instructions

Do the task below with the user's inputs in place of each [bracket].

1. List every system your AI booking assistant touches (calendar, payment link, CRM, spreadsheet) and write down what should happen when a booking comes in.
2. Move prices, fees and limits out of the assistant's instructions into one sheet you edit, and tell it: "Always quote from [sheet name]. Never use a price from memory or an old message."
3. Add this rule: "After you create a booking, read it back from [calendar]. Only tell the customer it is booked if the read-back matches the date, time, address and guest count. If the write or read-back fails, do not take a deposit, tell the customer we'll confirm shortly, and text me right away."
4. Set your capacity limits in writing, for example "never more than [2] bookings per day" and "never refund, discount or answer a complaint; hand those to me".
5. Schedule a daily check at [6 AM]: "Test each connection (calendar, payments, CRM) with a harmless read. Send me one short message: all OK, or which one failed and what to re-connect."
6. Once a week, ask it to compare payments received against calendar bookings and list any mismatch for you to fix.

## Safety checks (share these with the user)

- Check every figure, price and total against your own records before anything is sent, posted or booked. A person approves refunds, discounts, payments and price changes.
- Remove names, contact details, account numbers and other personal data the task doesn't need before you paste, and check your AI tool's data and training settings.
- Read and edit the draft before it reaches a customer or goes public. If you later automate this prompt, start with "draft and notify me", not "send automatically".
- Check names, dates, numbers and any claim against your own source material before you use the answer. AI can misread or invent details.
- Say clearly which parts need a person to review or approve before anything is sent, paid, posted or filed.

## About this skill

- Works with: ChatGPT, Claude, Meta AI, Google Calendar, Stripe or payment links, Google Sheets
- Based on this real-world example: https://ai-chs.com/intelligence/2026-11-01-ai-roast-season-manager/
- Free prompt from AgentPlaybook Real Estate: https://agentic-library.netlify.app/prompt/al-560-never-let-your-ai-say-booked-until-it-s-really-on-the-calend/
- To install in an agent that supports Agent Skills, save this file as SKILL.md in a folder with the same name as `name` above (for example in your skills directory). Install steps for Claude.ai, Claude Code, Cursor and Codex: https://agentic-library.netlify.app/skills/