Design customer support handoff

Prepare a support workflow for [business]. Start with a clear choice of [topics]. Ask for a short description of the issue when needed, and use an existing appropriate conversation status for team follow-up. Inspect available statuses rather than inventing an ID. Make it clear which workflows should stop replying during handoff; do not assume changing a label alone disables automation. Include a friendly fallback when the request cannot be processed. Do not assign the new workflow to a live Line.

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.