docs
EnglishChatigram website ↗Open Chatigram
AI & assistants

Plan appointment changes and cancellations

Collect a reschedule or cancellation request, identify the intended booking, and prepare a deliberate Calendar change.

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 #

Collect a reschedule or cancellation request, identify the intended booking, and prepare a deliberate Calendar change.

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 #

ChatGPT prompt
Prepare an appointment-change assistant for our existing Google Calendar bookings. Inspect the current workflow and how it records Event IDs without exposing credentials or unrelated customer data. Add separate reschedule and cancellation paths. Identify and review the intended appointment, check a proposed new time, and use the supported Show, Update, or Delete Google Calendar Event action only in the appropriate path. Require a clear customer decision and the access checks our process needs before any live change. Save the new draft disabled; do not modify or delete any existing event during this request.

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.

Download prompt text

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.

Keep building.Need help with this? Explore troubleshooting ↗

Find an answer. Try “welcome workflow”, “database”, or “Telegram”.