What evidence would help you distinguish a feature request from a broken promise?
A public request can describe a missing capability, a confusing interface or behavior that contradicts documentation. Decide which owner should investigate it first. Research the expected task and stated product boundary, rather than classifying every dissatisfied comment as a new feature opportunity or assuming that a confident user diagnosis establishes the technical cause of a failure.
Classify these public requests by documented promise, discoverability and observed failure, preserving uncertain causes and questions for the responsible product owner.Define the observation and counting unit
Define the requested action and the version or mode involved. Include public accounts explaining expected and observed behavior. Exclude unsupported assumptions about private accounts. Record the relevant documented promise, keeping absent documentation distinct from an explicit exclusion. A user asking for something does not establish whether it is already supported, newly desired or unavailable under their current plan.
Trace the concrete task evidence
Map each account to the step where expectation diverges from behavior. Preserve error messages without secrets and distinguish a discoverability problem from failed execution. A missing button may reflect permissions, version or scope. Do not infer the cause from the symptom alone, and do not recommend changing access or installing another tool before the responsible owner confirms the actual contract.
Challenge attribution and coverage
Compare similar reports and counterexamples under matching conditions. A successful account can identify a variable without disproving another person's experience. Keep duplicate retellings linked, and avoid estimating prevalence from an accessible thread. If the promised behavior is unclear, route the issue as a contract question rather than forcing it into a bug or roadmap category merely to complete a feedback spreadsheet.
Hand off a bounded interpretation
Return a triage brief with expected behavior, observed deviation, candidate classification and unresolved evidence. Keep implementation and account actions with the owner. If no supported path exists, acknowledge the request without promising delivery. The output should direct investigation, not claim a fixed defect, a measured demand level or a root cause that has not been reproduced through an actual authorized check.
Keep the boundaries clear.
- For feedback request or bug, reviewed public responses are not a representative customer sample.
- The feedback request or bug badges describe context, not guaranteed access or verified campaign reach.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.