From a support link to a verified reply.

What would you like to make?

Generated page → a real support reply

Actual runtime · internal test, not a customer case

The input

Internal acceptance used the existing SiSkill inbox and explicitly labelled synthetic messages, with no customer content.

The work

Generate from the final package, connect, send a test message, reply from the operator dashboard, then reload and continue the same conversation.

From your material to the finished files

1. Map sites and inboxes

   Reuse your website project and a separate public Website token per site. Missing settings produce a disabled preparation state.

2. Integrate and test recovery

   Generate a dedicated support page, link it from your site and check loading, retry, privacy and viewport behavior.

3. Verify before handover

   Verify a round-trip with an authorized test conversation. Confirm email and locked-phone alerts separately with the target account and device; retain unfinished checks.

Bring this task into your Agent

Prepare these materials

Provide editable website source, site URLs, your Chatwoot public Website tokens, support email and language. Your Agent prepares the configuration.

1. Sign in to acquire the package.
2. Extract the entire folder into your project: .agents/skills/support-launch-kit/SKILL.md (Codex).
3. Open a new chat in that project, attach your materials and replace the bracketed fields in the brief below. Ask the Agent to check package instructions and dependencies first.

Use support-launch-kit and read SKILL.md. Project: [path], site: [domain]. I need a dedicated support page. Inspect the project and routes; ask only for missing public Website settings, email and language. Generate and integrate it, checking loading, retry, privacy and revision rollback. Record account/device checks separately; leave unverified items pending and do not send messages or publish without authorization.

The first result can be revised

Generate revisions into a new directory, compare changes, keep prior files and retest. Old evidence does not certify revised artifacts.

What the package includes

• A dedicated support page, public configuration and integration notes for your existing website.
• Separate inbox configurations, a missing-configuration fallback and explicit retry.
• Acceptance records and handover for conversations, notifications, privacy and rollback.

What you provide separately

• Node 24, your own Codex access and editable website source; local generation has no npm dependencies.
• Your own Chatwoot account or existing HTTPS instance. Service, seat, model and device costs are separate.

Before you start

Version one uses a dedicated support page for 1–3 websites. It excludes an embedded overlay, server provisioning, AI replies and support seats. An internal test verified the message round-trip; verify email and phone notifications with your own account and device.

More to make

• Waitlist Landing Page — Create a responsive prelaunch page with a product story, FAQ and clearly labeled local demo form. Includes editable source and desktop/mobile previews.
• SaaS Landing Page — Create a full SaaS marketing prototype with positioning, features, workflow, billing-period controls, FAQ and an implementation handoff.
• Editorial SaaS Design — For writing and knowledge products. Upright editorial serif, generous paper margins, deep green actions, asymmetric manuscript composition. Give your Agent a brief to create a visual system and editable responsive page, or apply the direction to an existing project.
• Industrial Catalog Design — For hardware, furniture and industrial products. Ruled catalogue grid, square geometry, product-first imagery and compact model annotations. Give your Agent a brief to create a visual system and editable responsive page, or apply the direction to an existing project.