Route feedback to the right team and label it
Feedback reaches the alias that owns it, labelled and laid out so a triage pass takes seconds.
New feedback form submission
Gmail sends a labelled email to the appropriate team alias
One-directional. A submission triggers the action — nothing is written back into your form.
Feedback that lands in one shared inbox gets read once and then buried. Splitting it by score fixes most of that: a low rating needs an answer today, while a glowing one is a testimonial nobody has thought to ask for yet.
This flow sends each submission to the alias that owns the response and labels it on the way, so product@ can open a single label and read a week of comments in order. Product teams without a dedicated feedback tool often run this as their entire triage process.
Setting it up
- 1
Publish the feedback form and decide the split before building anything — for example nines and tens to a testimonials alias, six and below to support, the rest to product.
- 2
Start the Zap with the formformform New Submission trigger on the feedback form.
- 3
Add a Zapier path on How likely are you to recommend us to a friend or colleague? and give each branch its own Gmail Send Email action.
- 4
Set To on each branch to that branch's alias — product@, support@ — and keep the subject format identical apart from the score, so one filter covers all branches.
- 5
Put Overall Satisfaction at the top of the body, then What did you like most? and What could we improve? under their own headings.
- 6
Apply the label: either add Gmail's label action using the message id the send step returns, or set a Gmail filter matching the subject prefix. The label is what makes the archive searchable later.
- 7
Map Email Address into Reply-To, so whoever picks the message up can thank the person without copying an address out of the body.
- 8
Run one test submission through each branch, check the alias and the label are both right, then turn the Zap on.
What maps where
Using the Customer Feedback Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Gmail |
|---|---|
| How likely are you to recommend us to a friend or colleague? | The Zapier path condition that chooses the team alias |
| Overall Satisfaction | Subject prefix and the first line of the body |
| Name | Subject line, after the score |
| What did you like most? | Body, under a "what worked" heading |
| What could we improve? | Body, under a "what to fix" heading |
| Email Address | Gmail Reply-To, so a thank-you takes one click |
Variations worth knowing
Swap the path condition for a text search across What could we improve? — pricing, docs, speed — and apply a label per theme. Useful once the volume is high enough that score alone stops telling you who should read it.
On the detractor branch, CC the account owner by name instead of relying on the shared alias. A six or below then has one named owner, rather than sitting in a queue everyone assumes another person is watching.
If something isn't arriving
Zapier paths are evaluated in order and a broad rule placed first swallows the rest. Narrow the top condition, and check whether the score arrives as text rather than a number — a numeric comparison against text silently fails.
Labelling by Gmail filter matches on the subject, so two forms sharing a prefix collide. Give each form its own prefix, or label from the send step's message id, which points at exactly one message.
Frequently asked questions
Does the person who left feedback know where it went?
No. The routing happens inside Zapier and is invisible to them. If you want them to hear something back, add a second Gmail action addressed to Email Address that simply confirms the feedback arrived.
How do I route on a question people leave blank?
Optional fields arrive empty and will not match a condition. Either add a Zapier filter that checks the field exists before the paths run, or make the question required in the form so every submission carries a routable value.
Does replying in Gmail mark the feedback as handled?
Not in the form. Nothing is written back into a response, because the integration only runs submission-to-Gmail. Teams usually track triage with a second Gmail label — done, waiting — and leave the response list untouched.
Related automations
- Confirm every RSVP with the joining details
Registrants get a confirmation carrying the joining details, and the organiser mailbox is BCC'd on every one.
- Email an order confirmation to every buyer
Every order form submission sends the buyer a confirmation listing what they ordered and how it will reach them.
- Email every support request to your shared inbox
Each support request arrives as an internal email, CC'd to the on-call rep, with the customer set as Reply-To.
- Send an instant reply to every new lead
Every quote request gets a personalised reply from your Gmail account within seconds of the form being submitted.
- Stage each application as a draft for the hiring manager
Each new application lands as a Gmail draft addressed to the hiring manager, filled in and waiting for a human to press send.
- Add every event signup to your Outlook contacts
Everyone who registers is written into your Outlook address book with their phone, employer and job title already filled in.
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