Customer Feedback Survey

Collect ratings and comments in one flow: a five-star tap, a follow-up question, promoter/detractor tagging, and an instant alert to the owner.

The user wants a rate-us bot that collects a star rating plus a written comment and pushes every response straight to the owner or team.

• What are you collecting feedback about — the service overall, an order, an event?
• Who should receive new feedback alerts?
• Should low ratings also open a live chat with staff, or is the alert enough?
• Tag yourself (and anyone else who should see new feedback) with the alert tag you chose during setup on the Contacts page — the Notify feedback owner action messages everyone carrying that tag.
• Send /feedback to your bot once to test the full loop and confirm the alert arrives.

• Start via /start or /feedback
• Show the rating question with five star buttons
• Each button saves the numeric score (5..1)
• Scores 4-5 take the positive path: thank-you + what did we do well
• Scores 1-3 take the improvement path: apology + what should we improve
• Capture the free-text comment into a variable
• Tag the contact promoter or detractor
• Notify the owner by tag with score, comment, and user ID
• Send the closing thank-you message

Good to know

• Routing is per-button: 4-5 star buttons link into the positive path, 1-3 star buttons into the improvement path — no numeric CONDITION is needed, so there are no comparison-shape pitfalls.
• The Notify feedback owner action messages every contact carrying the alert tag; the install resolves or creates the tag automatically from its name.
• The /feedback command trigger lets returning users leave feedback anytime without restarting the bot.
• Promoter/detractor tags make it easy to later broadcast a review request to promoters only.

Keep in mind

• Do not promise analytics dashboards, NPS score charts, or aggregate reports — this template delivers each response as an alert message, nothing more.
• Do not replace the per-button routing with a numeric CONDITION on the score; the button paths are simpler and cannot mis-compare string values.
• Do not ask users to type a number for the rating; the star buttons are faster and validate themselves.
• Do not dead-end low ratings — the improvement path must always ask what to improve and still notify the owner.