Create Appointment Config for Availability and Forms

In this series — Part 2 of 5 (Appointments). · Previous: WhatsApp Appointment Booking Guide with Wapilot · Next: Schedule View & Bookings List: Manage Day-to-Da… · Series start

Before you start: If you skipped earlier steps, read WhatsApp Appointment Booking Guide with Wapilot first so nothing here feels confusing.

Booking buttons without rules create double-books. When you create appointment config, availability, questions, and templates become the source of truth.

Open hours that ignore buffers stack appointments. Missing intake wastes the visit. Confirmation copy that never ships leaves customers unsure.

In this guide, you'll discover availability windows, buffers, intake questions, and confirmation templates — without over-collecting data. As a WAPilot team that tunes clinic configs weekly, we see clear durations beat vague “come anytime” slots.

Soft goal: one tested config before schedule view and automation. Series overview lived in the WhatsApp appointment booking guide.

Operators who rush this step usually rebuild buffers twice after back-to-back overruns.

Keep the path short enough that a new manager can explain each service duration in one minute.

Operators who skip this step usually rebuild the same journey twice after customers complain.

Keep the path short enough that a new teammate can explain the habit in one standup minute.

Keep consent visible, Approved templates ready when the care window is closed, and a named owner for the first week after go-live so the team does not invent shadow processes.

How do you create appointment config without double-books?

Sources: Meta's Cloud API get-started guide and send messages docs. Define services and durations, set availability windows and buffers, add only necessary intake questions, attach confirmation/reminder template intents, then test a real booking on a staff number.

Series hub: WhatsApp appointment booking guide. Forms: WhatsApp forms guide.

Which availability and buffer rules actually work?

Honor real staff hours, add cleanup buffers between slots, block holidays, and keep timezone explicit. Do not publish slots you cannot staff.

Attributed example, from a WAPilot salon group (2026): zero buffers caused constant overruns. Adding ten-minute buffers and trimming open hours cut same-day chaos within one week.

1. List services + durations in writing.
2. Set hours and buffers staff can keep.
3. Add minimal intake questions only.
4. Attach confirm intent and cancel path.
5. Test on staff number before go-live.

Rule sources: Meta Cloud API get-started and send messages docs. Wapilot runs the workspace workflow; Meta still governs messaging quality and limits on the Cloud API number.

What intake questions belong in config?

Only what changes the visit—service type, party size, allergy notes, or location. Save deep forms for special cases. Pair confirmations with clear time and cancel path.

A forty-to-sixty word answer: create appointment config is the booking contract—hours, duration, buffers, questions, and confirmation copy tested once before you invite customers. Skip the test and the schedule view inherits fiction.

How we know: WAPilot operators review this workflow weekly against Meta’s public Cloud API docs — not unofficial blast shortcuts.

What mistakes break appointment configs?

Publishing every hour as available, collecting twenty questions, no confirmation template plan, and never retesting after hours change.

Templates primer: message templates explained.

Treat this guide as an operations checklist, not a one-time read. Print the ordered steps and assign an owner for each gate before you flip traffic live.

When something fails in production, capture the customer wording, the node that fired, and the Meta-facing symptom before you redesign the whole canvas.

Keep internal links few and intentional — adjacent series posts and the hub beat random keyword stuffing across twenty URLs.

Respect quiet hours and staffing plans. Automation that earns replies without inbox coverage creates the same unread spikes as careless campaigns.

Version names, changelogs, and a fifteen-minute post-publish review prevent mystery drafts from becoming the source of truth.

If quality rating slides after a launch, pause broad triggers first, fix consent and relevance, then warm traffic again on official Cloud API.

Keep these phrases in your team glossary so search and training stay aligned: availability windows; intake questions; buffers; confirmation templates; service duration.

Treat this guide as an operations checklist, not a one-time read. Print the ordered steps and assign an owner for each gate before you flip traffic live.

When something fails in production, capture the customer wording, the node that fired, and the Meta-facing symptom before you redesign the whole canvas.

Keep internal links few and intentional — adjacent series posts and the hub beat random keyword stuffing across twenty URLs.

Respect quiet hours and staffing plans. Automation that earns replies without inbox coverage creates the same unread spikes as careless campaigns.

Direct answer for operators: ship one clear habit, keep a human exit for exceptions, measure what customers actually do, and retest after every material change. Prefer official Cloud API paths over unofficial shortcuts, and staff the shared inbox whenever automation earns replies that need a person.

FAQs

How many intake questions is too many?

If customers abandon booking, cut—start with three or fewer.

Can one org have multiple configs?

Yes for distinct services or locations—name them clearly.

Do reminders live in config too?

Plan them here; detailed no-show flows come later in the series.

Does a bot-to-agent handoff reset the window on a shared number?

No. One customer thread, one service window. Two brands on one Cloud API line share that clock — split numbers before you scale support and promos on the same line.

Recap: create appointment config locks hours, buffers, questions, and confirmations before automation. When you are ready, start a free trial and grow on official Cloud API.