Email forwarding
One forwarding rule from support@yourcompany.com to your project address at in.usero.io. Each email lands as a feedback item with the sender attributed, clusters with reports from every other channel, and can open a pull request you review and merge.
The richest product feedback you get arrives as email. A customer writes three paragraphs about the broken export, someone replies "thanks, passing this along", and the email is archived. Passed along to nowhere.
Support email is where customers put in the most effort and get the least product impact. They write full sentences, describe what they were doing, and include their own address, everything a good report needs. Then the email dies in the inbox. Turning it into product signal means a human copying quotes into a tracker, and that habit survives about a week. So the requests that arrive by email never get counted against the same theme arriving through your widget or your Slack, and the theme looks half as common as it is. Meanwhile helpdesk tools will tag and route the conversation, but tagging is filing. The email still has to become a tracked, counted, deduplicated report next to the rest of your feedback before it can change what you build.
How it works
Full disclosure, this is my product. Your project gets its own inbound address, something like acme-x7k2@in.usero.io, shown on the integrations page. You add one forwarding rule in Gmail, Google Workspace, or Outlook from the address customers already write to, and setup is done. From then on each forwarded email becomes a feedback item: subject and body become the report, the sender address is parsed from the From header and attributed, and delivery retries or double-forwards are deduped by Message-Id so one email is one item. Emailed reports run through the same AI clustering as widget, Slack, Discord, and form feedback, so the complaint that arrives by email and the same complaint from the widget collapse into one counted theme. Then the wedge runs: with a GitHub repo connected you open the cluster, click Create PR, and Usero writes a first pass at the fix on a branch and opens the pull request. It drafts the code, the merge is always your call.
No API key, no OAuth, no code. You copy your project address from the integrations page and add a forward in the mail client your support inbox already lives in. Gmail wants you to confirm the forward with a code, and that confirmation email lands in your Usero inbox like any other, so the code is one click away.
The From header is parsed down to a bare address and stored as the reporting user. When the fix ships you know exactly who asked, and reports from the same customer across email and other channels connect instead of looking like strangers.
Provider retries and doubled forwarding rules produce one feedback item, keyed on the email Message-Id. Separate emails describing the same problem stay separate items but cluster into one theme with a count, which is the number that decides what gets built.
This is the step a helpdesk does not do. A clustered email complaint becomes a GitHub pull request with a first pass at the fix, quoting the feedback behind it. The customer wrote three paragraphs; the least you can do is let them end as code you review.
The honest objection
Keep the helpdesk. Usero does not thread conversations, assign agents, or send replies, and it should not be where you answer customers. The forward exists so the product signal inside those emails gets counted: forward the whole inbox, or better, use a filter so only product-relevant mail goes across. Two honest v1 limits to know before you set it up: attachments are dropped, so a screenshot in the email does not come through, and each email is its own feedback item, so a customer follow-up lands as a new report rather than extending the first. If most of your product signal includes attached screenshots, the Chrome extension or widget captures those better.
FAQ
Point a forwarding rule from your support inbox at your Usero project address (shown on the integrations page, shaped like acme-x7k2@in.usero.io). Each forwarded email becomes a feedback item with the sender attributed, and it clusters with feedback from your widget, Slack, and forms.
No. Usero ingests the email as a feedback item and stops. Replies to customers stay in your support inbox or helpdesk. Usero is where the product signal in those emails gets counted, clustered, and turned into a pull request.
You get one feedback item. Dedup is keyed on the email Message-Id header, so provider retries and overlapping forwarding rules do not create duplicates. A customer sending a follow-up email is a new Message-Id and lands as a new item.
Not in v1. The subject and plain-text body are ingested; attached files and images are dropped. If your reports usually hinge on screenshots, capture those through the widget or the Chrome extension, which store them.
In your Usero feedback inbox. Gmail sends its confirmation to the forwarding address, which is your Usero inbound address, so the verification email arrives as a feedback item. Open it, copy the code, and paste it back into Gmail to activate the rule.
Free tier. No credit card. Two-minute install. The AI opens the PR, you merge it.
Keep reading