IMPLEMENTATION GUIDE
Count accounts as well as requests
One account can submit the same request through several users or channels. Retain the original feedback, but also count distinct customer accounts when comparing segments. Company enrichment supplies segmentation fields; your feedback system provides the request text, product area, and context about the underlying need.
Use firmographics alongside product evidence
Industry and employee count help describe who requested something. Combine those attributes with your own adoption data, affected workflow, and customer interviews before prioritizing a feature. Headcount does not establish a feature’s value, the number of active seats, or the severity of a usability problem.
Keep analysis reproducible
Document industry mappings and company-size bands, preserve an unknown segment, and record when a profile was enriched. For historical comparisons, snapshot the segment used in a report so later profile updates do not silently change past results. Your team owns feature classification and roadmap decisions.
Connect the workflow
Use the API overview for request and task handling, or the Loop guide for webhook delivery.
Company enrichmentSee the company-size and industry fields used for segmentation.Common questions
Does EnrichLoops classify feature requests?
No. Your feedback system or analysis workflow groups and classifies requests. EnrichLoops adds company attributes that you can use to compare those groups.
Can I equate employee count with active product users?
No. Employee count describes the company. Use your product’s own account and usage records for seats, active users, and adoption.