When should you use it?
- Clients prefer messaging to booking pages
- Booking rules are specific (tutor, subject, length)
- Staff spend hours on scheduling chats
Not for: Businesses without clear booking rules; Payments inside chat without a checkout step
What do you need, and what do you get?
You need
- Tutor calendars
- Booking rules
- WhatsApp Business number
You get
- Bookings in the calendar
- Confirmations in chat
How does it work, step by step?
- Write the rulesDocument which tutor teaches what, lesson lengths, buffers and cancellation terms.
- Connect calendar and chatLink the WhatsApp number and calendars through your platform.
- Confirm every bookingHave the agent read back time, tutor and subject before saving.
- Catch dropped messagesLog every incoming message and alert on any that did not lead to a reply.
- Hand off edge casesRoute complaints and special requests to staff.
The prompt
Our own prompt, inspired by MarcoKueks on Hacker News and written to work in Custom agent and n8n. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You book lessons for {tutoring_company} on WhatsApp. Rules: {booking_rules} Find a slot that fits the student's subject and preferred times, read back tutor, subject, date, time and time zone, and book only after the client confirms. Send complaints or special requests to staff.
Inspired by MarcoKueks on Hacker News: Hacker News post on building WhatsApp booking agents for clients. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Messages that arrive but never trigger a booking are the classic failure; monitor for them.
- Time zones and daylight saving cause double bookings; store times with zones.
Our take
The honest lesson is where the effort goes: once plumbing works, business rules are the project. Who teaches what, buffers between lessons, cancellation windows and payment rules decide success. Marco's two-day build is a useful reality check for anyone selling chat agents to small firms: most of the effort went into the firm's own rules, not the plumbing. Write down which tutor teaches what, lesson lengths, buffers and cancellation terms before connecting anything. Have the agent read back the time, tutor and subject before saving a booking. The classic failure is a message that arrives but never leads to a reply or booking, so log every incoming message and alert when one goes unanswered. Store times with their time zone to avoid double bookings around daylight saving changes. Route complaints and special requests to staff, give parents an easy way to reach a person, and keep payments out of the chat.
Where the time goes back: Scheduling chats become self-service, and staff only handle the unusual requests.
FAQ
Where does the time go?
Is Struere required?
Source and credit
Inspired by MarcoKueks on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Hacker News post on building WhatsApp booking agents for clients
- Creator
- MarcoKueks on Hacker News
- Published on
- Hacker News
- Original date
- Apr 14, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.