Decide where the work belongs
Reconcile reach across sources
Identify duplicate customers, accounts, workflows, and time windows before counting reach. Keep a source breakdown so a support-heavy signal is not mistaken for independent demand. Mark whether channel identity is complete or partially unavailable.
Separate urgency from frequency
Use escalation timing, blocked outcomes, workaround cost, and recurrence as distinct evidence. A single operational escalation may justify rapid investigation while a broad preference remains scheduled; state why the dimensions lead to that difference.
Choose a source-balanced position
Set the queue position, owner, and review trigger with a rationale that names normalized reach and strongest evidence. Keep each channel linked so later reviewers can test whether the ranking depended on one source's reporting habits.
What to carry forward
The output is a ranked request with reconciled reach, channel-specific context, severity, urgency, and evidence limits. Stop when the queue rationale cannot be changed merely by adding duplicate messages; define the signal that would move the request if a new independent segment appears.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow