Design a salon and spa booking assistant
Route haircut, color, and spa requests into clear conversation branches, then configure service-specific Calendar booking rules.
Target assistant #
ChatGPT · Required connection: Chatigram plugin.
The public ChatGPT plugin listing is under review. These prompts are for workspaces where the Chatigram plugin is available and connected. Status reviewed 2026-11-10.
What this prompt helps you do #
Route haircut, color, and spa requests into clear conversation branches, then configure service-specific Calendar booking rules.
This request checks your organization’s actual capabilities instead of assuming a provider, plan, or node is available.
Customize before using #
Replace the bracketed placeholders with your organization and business details. Keep passwords, API keys, bot tokens, and private customer data out of the prompt. The Chatigram plugin currently requires an Admin role in the selected organization.
Copy the prompt #
Design a salon and spa booking assistant using Google Calendar. Offer the service categories [services] and use our actual duration for each service. Model the required stylist/therapist and room resources explicitly. Discover the supported availability and event nodes rather than inventing a booking action. Use our timezone [timezone], working hours, unavailable days, and preparation buffers. Add clear Created, Unavailable, and Error messages. Keep customer preferences separate from confirmed appointments. Prepare the flow disabled and explain how to test every service branch.
Use the Chatigram plugin for organization [organization name]. Discover the current permissions, plan limits, triggers, node types, and compatible connections before designing the solution. For conversation workflows, check the selected Line’s Private AI mode before proposing Inbox follow-up or a human handoff. Do not promise human access to private AI conversations. Prepare and save the requested workflows disabled, after showing the draft preview and any unresolved setup. Do not activate, run, assign to a live Line, send messages, or use paid processing. If a paid capability or connection is needed, explain the service, account, transferred data, and required spending approval before adding or binding it. Do not ask me to paste credentials into chat; use protected setup links. Keep unrelated resources unchanged.
Finish with: what was prepared, what is still missing, which plan-dependent features are involved, and the next safe test. Do not claim execution or delivery from a draft preview.
Review the actual result #
Check the preview, branch behavior, required accounts, plan-dependent resources, and any missing setup. A prepared definition is not proof of live execution. Give a later, explicit request for activation, assignment, sends, or paid processing only when you intend those actions.
Return to the AI prompt library for more ideas and target-specific guidance.