Collect product feedback as tagged conversations
Ratings and comments open as tagged conversations in a Feedback mailbox you can filter, search and revisit when planning.
New Submission on your "Product feedback" form
Create a conversation in the Feedback mailbox with the rating and comment, tagged "feedback"
One-directional. A submission triggers the action — nothing is written back into your form.
Ratings and comments have a habit of ending up in a spreadsheet nobody opens after the first month. Routing the feedback form into its own Help Scout mailbox makes each response searchable, taggable and, when it deserves one, answerable.
Customer success teams use this when they want feedback in the same tool as everything else, so the week before planning starts with a tag filter rather than a hunt through exports. The customer stays attached, which keeps a reply one click away.
Setting it up
- 1
Set up a dedicated Feedback mailbox in Help Scout so ratings never distort the response-time figures your support team is measured on.
- 2
Publish the feedback form with Product Name or Model as a choice list of what you actually sell. Free text splits one product across several spellings and breaks the search you will do later.
- 3
In Zapier, set formformform's "New Submission" as the trigger and select the feedback form.
- 4
Add Help Scout's "Create Conversation" action and set Mailbox to Feedback.
- 5
Build the subject from Product Name or Model plus the Ease of use rating, so scanning the mailbox shows which products are being scored badly.
- 6
Map the two open questions, what is missing and what is liked, into the thread body in that order, each behind a short heading.
- 7
Add the static tag feedback on the action, and set the conversation status to Closed if the team reads this mailbox in batches instead of replying to each response.
- 8
Send a test rating, check that the tag and subject arrived as expected, then turn the Zap on.
What maps where
Using the Product Feedback Survey as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Help Scout |
|---|---|
| Product Name or Model | Conversation subject, so the mailbox sorts by product |
| Ease of use | Rating line at the top of the conversation body |
| What features are missing or need improvement? | Main body of the conversation |
| What features or aspects do you like most? | Body, below the improvement request |
| Email Address | Customer on the conversation, for following up when something ships |
| Your Name | Customer name on the record |
Variations worth knowing
Add a Zapier filter on the Ease of use rating so anything at the bottom of the scale opens as Active and assigned, while the rest arrive closed and tagged. Customer success sees the unhappy responses first without reading every one.
Map Product Name or Model to a tag as well as the subject. A saved search on that tag then gives you every piece of feedback about one thing, which is exactly what you want on screen the week before planning.
If something isn't arriving
Help Scout counts every open conversation in a mailbox's reports. Create these with the status set to Closed so they never enter the queue, or exclude the Feedback mailbox from the reports your support team is measured against.
A mapped answer with a stray space or a different capitalisation becomes its own tag. Use a static tag on the action wherever you can, and trim the value in Zapier when you do need to map a form answer into one.
Frequently asked questions
How do I find every request for the same feature later?
Search the feedback tag together with the product tag, then merge the duplicates onto one conversation. Each customer stays attached to the merged thread, so a single reply reaches everyone who asked for that thing when it finally ships.
What happens if someone submits feedback without an email address?
The conversation still opens, but with no customer attached it cannot be replied to and it will not appear in anyone's history. Make Email Address required if you intend to follow up, and leave it optional if you only want the rating.
Does closing the conversation email the person who sent it?
No. Closing is an internal status change, and Help Scout only sends what an agent writes as a reply. The submitter hears from you when someone answers the thread, not when the status moves from active to closed.
Related automations
- Create the customer record before the first reply
Onboarding intake answers become a Help Scout customer record, so agents see who the person is before the first conversation opens.
- Land demo requests in the sales mailbox
Demo requests open as conversations in the Sales mailbox, carrying company size, the problem to solve and the timing.
- Open a support conversation from every contact form message
Each contact form message arrives in your Support mailbox as a conversation, attributed to the sender and ready to assign.
- Route bug reports into a tagged engineering conversation
Bug reports open in the Engineering mailbox, tagged and carrying the severity and reproduction steps the reporter filled in.
- Send refund requests to the billing mailbox
Refund requests become trackable conversations in the Billing mailbox, with the order number in the subject and an owner attached.
- Capture feature requests as labelled tickets
Product ideas from your feedback form land in Freshdesk as Feature Request tickets the team can group and revisit.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free