Turn one piece of content into a comment funnel that can actually be built, tested, and measured. This skill is responsible for designing the specification and copy; without the user's explicit authorization, do not log in, do not activate, do not publish, and do not modify any external automation.
First, gather the necessary information
Before starting, confirm:
- Platform, post/Reel topic, and target audience
- Unique comment keyword
- Gift name, contents, actual link, and delivery method
- The service/product to transparently introduce, who it is for, and the link
- Real evidence that can be used, and information that must not be made public
When links or evidence are missing, use [待補], and do not fabricate. If the user only provides an idea, a draft can still be produced, but it must be marked "not yet live".
Three-step design
- Comment prompt: Write a CTA directly related to the content, a single easy-to-enter keyword, and 2–3 natural public replies.
- Manychat auto-reply: Specify the trigger post scope, keyword, Opening DM, selection buttons/Quick Reply, gift message, and optional follow-up. First read Manychat current limitations。
- Deliver the gift and introduce the service/product: First fully deliver the promised gift, then clearly state that the related service/product is optional, and do not hide the sales pitch inside the gift.
For the complete decision order, see Three-step process, and for sentence patterns that can be directly rewritten, see Message templates。
Fixed output
Deliver in order:
- Status and assumptions: confirmed, to be supplemented, not yet live.
- One-line flowchart: content CTA → comment keyword → public reply → Opening DM → user interaction → gift → optional service/product.
- Process node table: for each node, list the purpose, trigger condition, text the user sees, next step, and failure fallback.
- Copy for each message: post CTA, public reply, Opening DM, buttons, gift message, transparent invitation, and follow-up message when necessary.
- Fields and tags: campaign source, post ID, keyword, gift version, interaction/delivery/click status; do not request passwords or tokens.
- Build checklist: node specifications that can be completed manually using the Manychat interface, without treating UI names as permanently unchanging facts.
- QA test table: at minimum cover the correct keyword, typos, duplicate comments, non-followers, broken links, conflicts with old flows, and real mobile testing; use QA checklist。
- Measurement table: comment count, Runs, Opening DM interaction, Sends, gift clicks, service/product clicks, and qualified replies; Runs and Sends must not be conflated as the same metric.
Quality and safety boundaries
- Do not guarantee deals, revenue, reach, or conversions; write numbers as hypotheses to be tested.
- Do not mass-wash comments, do not bypass Meta/Instagram/Manychat restrictions, and do not collect personal data for users without disclosing its purpose.
- A first private reply does not mean the user has opted in; interactions and the 24-hour messaging window are handled according to current official rules.
- The same user's first comment on the same post/Reel triggering restrictions, trigger priority order, and post ownership must all be included in testing.
- If the giveaway includes affiliate links, a sales page, or a service invitation, clearly indicate the relationship and purpose.
- Delivery completion stops at "buildable specification." When actually going live, first confirm the account, permissions, costs, privacy notice, and publishing authorization.