{"id":108338,"plugin_id":"plugin_asdk_app_6956e6ff740481919946ceae8e5d6304","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-20T18:10:53.378Z","digest":"ea0b5a6490fc0182eb8b7f48fda9da3dd42956ada0f10ab3cd310b5060bda933","against":null,"payload":{"description":"Add online appointment booking to a small-business app with the AppDeploy booking module. Ask the owner five critical questions with quick defaults or dig-in options, then build. Use when the user wants clients to book appointments, time slots or classes (salon, clinic, studio, tutor, court).","included_files":[],"name":"booking-setup","skill_md_contents":"---\n{\n  \"name\": \"booking-setup\",\n  \"description\": \"Add online appointment booking to a small-business app with the AppDeploy booking module. Ask the owner five critical questions with quick defaults or dig-in options, then build. Use when the user wants clients to book appointments, time slots or classes (salon, clinic, studio, tutor, court).\"\n}\n---\n\n# Booking setup\n\nUse this when the owner wants clients to book appointments or classes (salon, clinic, studio, tutor, court, barber, pet groomer). The booking module does slots, holds, cancel and move rules, waitlist, reminders by email and push, calendar files and the widgets. You decide five things with the owner and leave the rest on defaults.\n\nKeep the conversation short. Ask the five questions in one message, each with a one-line **quick** default. When the host has a native ask-user tool (`request_user_input_async` or `request_user_input`), put the five questions in one call with the quick default as the first option and \"let me dig in\" as the second; otherwise ask them as one chat message. The owner answers what they care about; anything they skip takes the default. Only open a **dig in** block when the owner asks for it or their answer needs it.\n\n## The five questions\n\n### 1. What can be booked, and by whom\n**Quick:** list your services with duration and price, e.g. \"haircut 45 min 40, color 90 min 90\". One person (you).\n\n**Dig in** when there is a team or classes:\n- Team: names; who gets the staff role (they sign in and see the day view); which staff do which service.\n- Classes with seats (yoga, workshop) in addition to or instead of appointments.\n- Clean-up buffer after a service (default 0; 10 to 15 for color, treatments).\n- More than one location (branches).\n\n### 2. When\n**Quick:** weekly hours, e.g. \"Mon to Fri 9 to 18, Sat 9 to 14\". Same for everyone.\n\n**Dig in:**\n- Different hours per staff member; lunch breaks; days off and holidays.\n- Slot grid (default 15 minutes; 30 for long services, 10 for quick ones). It locks after the first booking, so settle it now.\n- How far ahead clients can book (default 60 days) and minimum notice (default none; for example nothing in the next 2 hours).\n\n### 3. Cancellation\n**Quick:** 24 hours. After that the client is told to call.\n\n**Dig in:**\n- Different cutoff (48 hours for long treatments is common).\n- Can clients move a booking themselves (default yes, same cutoff).\n- Max open bookings per client (default 3).\n- No-shows: marked by staff; no automatic penalty.\n\n### 4. Money\n**Quick:** no payment in the app; pay at the visit.\n\n**Dig in:** deposits and online payment are not available yet. When the owner asks for them, say so plainly and do not build a payment step or add a payment provider by hand. Offer instead to show each price and one sentence about how and when to pay (and the no-show policy) on the booking page.\n\n### 5. Messages\n**Quick:** email confirmation and a reminder the day before at 18:00, in the app's language when the platform has it (English otherwise). The owner gets a daily summary of tomorrow's bookings.\n\n**Dig in:**\n- An email to the owner on every booking and cancellation (off by default; a busy business is better served by the daily summary).\n- Quiet hours: no messages at night or on the owner's days off.\n- WhatsApp and SMS messages are not available yet; when the owner asks, say so and keep email and push.\n- Push notifications for clients who install the app.\n- Sender: the platform address, or the owner's own domain (Plus).\n- Waitlist when a day is full: on by default, first in line gets a 15-minute offer when a slot frees up.\n\n## Not questions, just do it\n\n- Clients sign in to book (Google, Apple, email). No guest booking. Free times are visible without sign-in; sign-in is asked when the client presses Book.\n- Set the business timezone from where the business is (the city or country the owner mentioned); ask once when it is unclear. Never leave the default and never copy a timezone from an example.\n- Widgets: `<appdeploy-booking>`, `<appdeploy-my-bookings>`, `<appdeploy-booking-admin>`, with a full labels object in the app's language and `{hours}` / `{max}` in the error texts.\n- Admin area for the owner (and staff): day view, services, hours, settings. Owner only for services, hours and settings.\n- Make the signed-in role obvious: anyone with a role sees a badge in the header with their role and name (for example \"Owner · Alex\" or \"Therapist · Downtown\"), the admin link has its own look (filled button, not one more menu item), and after sign-in staff land on the admin page while customers land on the home page. Customers keep the plain header.\n- Public page: services and prices, hours, address, the booking widget, \"my bookings\", contact.\n- Staff records show a name to clients (\"Sam\", or \"Therapist 1\" when no name was given), never an email. Staff who sign in are linked to their staff record through the invite, the same way for everyone (see staff-setup).\n- With more than one branch: every staff record carries its branch, the client picks a branch before a time (the booking widget takes the branch), and a team member invited for a branch sees and changes only that branch's bookings. The booking module enforces this from the role's branch; do not write your own branch checks.\n- Removing a service or a staff member hides it; bookings already made keep the name. Hours that pass midnight are entered as two days.\n- Seed services, staff and hours on first run from the answers; make the seed idempotent and safe for parallel first requests (claim a setup row, wait for it to complete).\n- Calendar: .ics and Google link come with the widgets; the confirmation email carries the event.\n\n## After it is deployed, tell the owner\n\n1. Sign in to the app with the same email as your AppDeploy account: that makes you the owner.\n2. Check the services, hours and cancellation cutoff in the admin area; change them there, no redeploy needed.\n3. Optional: connect a custom email sender (Plus) so emails come from your domain.\n4. Book a test appointment yourself and check the email and the calendar card.\n\n## Example answer set (a salon)\n\n> Services: women's cut 45 min 55, men's cut 30 min 30, root color 90 min 95 (10 min buffer), blow-dry 30 min 35. Just me. Tue to Fri 9 to 19, Sat 9 to 15. Cancel until 24h before. No deposits. Email plus reminder at 18:00, nothing on Sundays.\n\nEverything else is the default.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}