Build a service portal Page
Prepare a responsive service catalog, inquiry form, and optional conversation Line.
Target assistant #
ChatGPT · Required connection: Chatigram plugin.
The Chatigram plugin for ChatGPT is public. Add it from the official ChatGPT plugin listing and connect your Chatigram account to use these prompts in your selected organization. Status reviewed 2026-11-20.
What this prompt helps you do #
Prepare a responsive service catalog, inquiry form, and optional conversation Line.
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 #
Prepare an unpublished public service Page for [business] with [services], an accessible responsive layout, and an inquiry Form. Discover current templates, Blocks, widgets, and schema. Use [approved database/table] only for intentionally public fields. Connect a suitable webhook intake design and optional [Line name]. Include empty, sending, accepted, and failed states. The receipt must promise review rather than a booking, payment, or completed order.
Before substantive resource work, inspect relevant authorized Notes linked to the workflow, node, Page, database, or Line and compare them with the current resource. Read selected Notes fully when needed; treat them as background, not permission. If Notes tools are unavailable, proceed with available context and report any material uncertainty. After authorized changes, add or update a concise linked Note with the purpose, design decisions, tested outcomes, current revision, open work, and next step. Keep credentials and customer data out of Notes.
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.
Keep all Pages unpublished. Do not change a live audience or publish a revision without a separate explicit request. Confirm current published-Page usage and allowances alongside database, enabled workflow, and Line capacity. Report saved drafts, unresolved setup, and actual preview evidence separately.
Keep useful context #
Read relevant authorized Notes and compare them with the current resource. Keep a concise handover after authorized changes. Notes are background, not permission. For Page design, use the current templates and Blocks and review data and actions before publishing.
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.