A productive feedback loop starts with structured collection. This article walks through how to set up Harvestr for three common team workflows: Sales, Customer success and support, and Product. By the end, each team submits feedback from the tool it already uses, every piece of feedback arrives in Harvestr labeled and routed to the right person, and the product team can triage it efficiently.
Choose the right channel per team
Each team should submit feedback from the tool that's already part of its workflow. Friction kills feedback loops.
Sales: the Salesforce widget or the HubSpot widget on account, contact and deal records. The customer is attached automatically, so the feedback arrives linked to the right account. If your reps record their calls, the call recorder integrations (Gong, Aircall, Claap, Modjo, Praiz) bring the feedback from those calls too.
Product team (PMs, POs, designers): the Chrome extension for feedback spotted on any web page, or the new feedback button inside Harvestr, great for user interview notes.
Anyone, occasionally: the
/harvestrcommand or a message action in Slack, Microsoft Teams, or forwarding an email to your Harvestr address.
Contributors are free and unlimited, and most of these channels don't even need a Harvestr account: your Sales and Support teams can send feedback without taking a seat.
Set up product labels for routing
Labels are how you route incoming feedback to the right product person. The pattern that works well: one label per product line, module or theme, applied when the feedback is submitted.
Examples we see in production:
Mobile, Web, Integrations (small product surface)
Product A - Module 1, Product A - Module 2, Product B (multi-product portfolio)
Pricing, Onboarding, Performance (jobs-to-be-done framing)
How labels get applied depends on the channel:
Salesforce widget: turn on Require labels in the Sending from Salesforce card of the Salesforce settings.
HubSpot widget, Chrome extension and Slack: in the channel's feedback template, show Labels and make it Required.
Zendesk, Intercom and Freshdesk: the tags of the ticket or conversation are imported as Harvestr labels.
Choose which labels each channel offers in Settings > Feedback labels, in the Visible in column. See Build your feedback taxonomy with labels.
Build a feedback template per channel
Templates make sure whoever submits feedback gives you the context you need. Without one, you get one-liners. With one, you get the problem, the possible solutions and the impact.
A solid baseline:
What is the problem the customer or prospect is expressing?
What are the potential solutions?
How important is it? Is this a deal blocker? How much revenue is at stake?
Adapt it per channel. The HubSpot and Slack templates can ask for the deal stage as a select question; the Chrome extension template can ask which customer segment the feedback comes from. Chrome, Slack and the HubSpot widget use question-based templates, while the Salesforce widget uses a classic title-and-content template. See Collect structured feedback with templates.
Route incoming feedback with Custom Inboxes
Once labels are flowing in, set up a Custom Inbox per product line or per teammate (Scale plan and above). A Custom Inbox is a saved set of filters on your inbox, accessible from the Inbox sidebar.
For each Custom Inbox:
Filter on the label or labels it should cover.
Optionally narrow it by source (Salesforce only, Zendesk only) or other criteria.
Save it so it appears in your Inbox sidebar.
Automate labels and assignment with Feedback automations
On the Elite plan, Feedback automations take it further. Two kinds:
Rule-based: when feedback carries certain labels, assign it to a teammate or add another label.
AI automations: write a smart rule in plain language (for example, "This feedback mentions slow loading times"), and Harvestr applies a label or an assignee whenever new feedback matches.
AI automations are especially useful to catch feedback that wasn't labeled at submission. See Automate labeling and triage with Feedback automations.
End-to-end example
Here's how a piece of feedback flows through this setup:
An account executive opens an account in Salesforce, clicks New Feedback in the Harvestr widget, and sends feedback with the label "Product A - Mobile" and a templated description.
The feedback arrives in Harvestr already labeled "Product A - Mobile" and linked to the customer account.
A Feedback automation assigns it to the PM responsible for Product A's mobile experience.
The PM sees it in their Custom Inbox ("Product A - Mobile") and links it to an existing discovery, or accepts HAI's suggestion.
When the discovery moves to Planned or Shipped, the account executive is notified, and the Customer Roadmap tab of the Salesforce widget shows the new status on the account.
To set up those notifications, see Close the loop with feedback loop notifications.