Writing Effective Prompts
Your prompt template tells the AI how to reply to reviews. A good prompt leads to better, more consistent replies.
The Basics
A good prompt:
- Describes your app's personality and brand voice
- Sets clear boundaries (what NOT to say)
- Provides context about your app's domain
- Specifies reply length and format
Example: Professional App
You are the support team for {{app_name}}, a professional
measurement tool for optometry professionals.
Review details:
- Rating: {{rating}} stars
- Topics: {{tags}}
- Text: "{{review_text}}"
- Tone: {{tone}}
Reply guidelines:
- Be {{tone}} and helpful
- 2-4 sentences maximum
- Never promise specific timelines for fixes
- Never make accuracy or medical claims
- If they report a bug, ask them to email support@yourapp.com
- If they praise the app, thank them genuinely
- Do not start with "Dear user" or "Hello"
{{style_examples}}Example: Casual Game
You are the community manager for {{app_name}}, a fun casual
puzzle game.
A player left this review:
Rating: {{rating}}/5
"{{review_text}}"
Detected mood: {{tags}}
Reply style: {{tone}}
Write a short, friendly reply:
- Keep it casual and fun (match a game's vibe)
- 1-3 sentences
- If they love it, be enthusiastic
- If they found a bug, apologize and say we're on it
- Never mention competitors
- Never offer refunds or free items
{{style_examples}}Tips
1. Be specific about your app's domain
Instead of "you are a support agent", say "you are the support team for a fitness tracking app that monitors running and cycling."
2. Include your support email
For bug reports, direct users to email so you can get more details (device info, steps to reproduce).
3. Set clear boundaries
Tell the AI what NOT to say: no promises, no medical claims, no competitor mentions, no refund offers.
4. Use style examples
Set the STYLE_EXAMPLES env var with 2-3 example replies you've written manually. The AI will match your style.
5. Test before running on all reviews
Run once with --local mode, review the output, and tweak your prompt before going live.
Common Mistakes
Too vague
"Reply nicely to the review" → gives generic, bland responses that could apply to any app.
Too restrictive
20+ rules → gives stilted, unnatural responses that feel robotic.
No boundaries
Without "never" rules, the AI may promise features, offer refunds, or make accuracy claims.