Use this prompt recipe for community reply for a product launch. It gives the AI a clear job, visible source inputs and a review step so the result can be edited instead of blindly copied.
| Best for | social media managers, creators, brand teams and community managers |
|---|---|
| Search intent | Readers usually need prompt structure for hooks, captions and calendars that match a brand voice instead of generic post ideas. |
| Expected output | Post angle, Hook options, Caption or script draft, Review checklist |
When this recipe is useful
Use this recipe when the task is specific enough to benefit from AI structure but still needs human judgment. In the situation "for a product launch", the prompt should make the audience, source material and quality bar explicit before asking for a finished answer.
The goal is not to make a generic community reply. The goal is to create a draft that reflects the real context, avoids unsupported claims and gives the reviewer a clear path for improving the result.
Source inputs to prepare
| Platform | Add the real detail for community reply for a product launch. If this detail is unknown, ask the AI to return a missing-information question. |
|---|---|
| Audience concern | Add the real detail for community reply for a product launch. If this detail is unknown, ask the AI to return a missing-information question. |
| Content pillar | Add the real detail for community reply for a product launch. If this detail is unknown, ask the AI to return a missing-information question. |
| Proof point or source | Add the real detail for community reply for a product launch. If this detail is unknown, ask the AI to return a missing-information question. |
| Brand voice boundary | Add the real detail for community reply for a product launch. If this detail is unknown, ask the AI to return a missing-information question. |
Copy-ready prompt
Recommended output structure
- Post angle: Make this section specific to community reply for a product launch and easy for a human reviewer to check.
- Hook options: Make this section specific to community reply for a product launch and easy for a human reviewer to check.
- Caption or script draft: Make this section specific to community reply for a product launch and easy for a human reviewer to check.
- Review checklist: Make this section specific to community reply for a product launch and easy for a human reviewer to check.
Review checklist
- The post has a clear intent beyond filling a calendar.
- The hook does not exaggerate the outcome.
- The caption uses source material or brand proof.
- The call to action fits the platform.
Common mistakes
- Starting with hooks before choosing the post intent.
- Repeating the same angle across posts.
- Using engagement bait.
- Publishing claims that the source material does not support.
How to adapt it
If the first output feels too broad, add one concrete example of the audience, one example of the tone you want, and one example of a claim the AI must avoid. This usually improves the next answer more than adding more adjectives.
If the output is too long, ask the AI to keep the structure but shorten each section around the decision the reader needs to make. If the output is too shallow, add source notes and ask for missing questions before another draft.
FAQ
When should I use this prompt?
Use it when you need community reply for a product launch and want the AI output to stay tied to your real source inputs, audience and review rules.
What should I prepare first?
Prepare the practical inputs: Platform, Audience concern, Content pillar, Proof point or source. If one of those is missing, keep it marked as unknown instead of asking the AI to guess.
Can I publish the output directly?
Treat the output as a draft. Check facts, claims, names, dates, policies and promises before using it in public or customer-facing work.