Drop customer feedback into your product channel
Feedback posts to #product as it arrives, with the rating and the comment, so nobody waits for a weekly roundup.
New submission on your "Feedback" form
Send a channel message to #product with the rating, comment and the customer's email
One-directional. A submission triggers the action — nothing is written back into your form.
Feedback that arrives in a monthly summary has already lost the thing that made it useful — the wording, the frustration, and the moment it happened. Sending each response into #product puts the customer's own sentence in front of the people who decide what gets built next, on the day it was written.
Product teams use it to keep a habit rather than a report. Someone reacts, someone else threads a follow-up question, and the responses worth acting on get picked out while the context is still fresh. The channel is internal, so the customer never sees any of it.
Setting it up
- 1
Publish the feedback survey and decide which products it covers. Product Name or Model is what lets one channel carry feedback for several products without anyone losing track.
- 2
In Zapier, set the New Submission trigger to watch that survey and pull a real submission in as the sample, so the rating answers come through with their proper labels.
- 3
Add Slack's Send Channel Message action and select #product — the channel your product managers already read, not a new one nobody has joined yet.
- 4
Lead with Product Name or Model and the "Meets your expectations" rating, so the channel can be skimmed by product and by tone before anyone reads a sentence.
- 5
Map "What features are missing or need improvement?" as the body of the message. That answer is the one a product manager acts on, and it deserves the room.
- 6
Add "What features or aspects do you like most?" underneath, so praise and criticism arrive together instead of as two unrelated messages.
- 7
Include Email Address only if #product is private. It is what makes a follow-up possible, and it does not belong in a channel the whole company can read.
- 8
Agree what a reaction means before you go live — most teams settle on one emoji for "worth a follow-up" — then test with a single submission and 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 | Slack |
|---|---|
| Product Name or Model | First line of the message |
| Meets your expectations | First line, the rating read at a glance |
| Would you recommend this product to a friend or colleague? | Short line beside the rating |
| What features are missing or need improvement? | Body of the message |
| What features or aspects do you like most? | Line below the body |
| Email Address | Final line, mapped only when #product is private |
Variations worth knowing
Run two Zaps with opposite filters. Unhappy responses post with a mention so somebody follows up by email that day, and everything else posts quietly for the weekly read, which keeps the mention meaning something.
Use Zapier paths on Product Name or Model so feedback reaches the channel of the team that owns it. A shared #product channel stops being read once two products' worth of comments are landing in it every day.
If something isn't arriving
Slack shows whatever the answer option is called in the form. Rename the rating choices to the words your team uses — fell short, as expected, better than expected — then reload the sample submission in Zapier so the new labels come through.
A channel that only receives has no rhythm to it. Add Digest by Zapier so submissions arrive as one message each morning, or agree that whoever is on triage that week clears the unreacted messages before standup.
Frequently asked questions
Can a product manager reply to the customer from Slack?
Not through this flow. Nothing typed in Slack goes back to formformform or reaches the customer, so a reply means opening your mail client and using the address in the message. The thread is for the team's own discussion.
Should I map all the ratings into the message?
Map two at most. A message carrying nine rating lines gets skipped, while a product name, one rating and the comment gets read. The full set of answers stays in your responses list for the quarterly pass over everything.
Can the same feedback also go to a private channel?
Add a second Slack action to the same Zap pointing at the private channel, and map Email Address only there. #product carries the comment for everyone to read, and the private copy holds the detail you need to follow up on.
Related automations
- Alert the on-call team when a support ticket arrives
Each new ticket posts to #support with its subject and priority, and @here fires only when the priority justifies interrupting a shift.
- Post event RSVPs to the planning channel
Every RSVP posts to #events with the name, party size and dietary notes, so organisers watch the headcount build in one place.
- Post new job applications to your hiring channel
Applications land in a private #hiring channel with the role and the candidate's skills, and reviewers thread their notes under each one.
- Send each new order as a direct message
New orders arrive as a direct message to whoever packs them, with the product, quantity and address in one place.
- Send new demo requests to your sales channel
A rep sees each inbound demo request in #sales the moment it lands, and claims it with an emoji reaction before anyone else replies.
- Alert the team when a new order comes in
Each new order pings #orders with the product, quantity and buyer details, so fulfilment can start straight away.
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