View membership
A Zendesk view lists tickets according to conditions, columns and ordering. It does not change ownership. Shared view access is separate from ticket permissions.
For an original workload list, require Billing and an unsolved status in All. Put High or Urgent in Any. Requiring both priority values in All creates an impossible intersection. Putting Billing among loose alternatives can admit a Technical ticket. Check the member IDs, not just the count, and exclude archived records.
Queue and agent eligibility
Omnichannel queue documentation distinguishes standard routing from custom queues. Standard email routing uses the assigned group and routing tag. Custom queues have their own ordered matching and group configuration; do not copy standard rules indiscriminately.
After a ticket qualifies, an agent must still meet configured availability, capacity, group and skill requirements. An away agent with spare capacity is not equivalent to an online eligible agent. Ticket order and agent selection are separate decisions.
Practice case
Give a Billing source to three fictional agents: one qualified online agent, one with the wrong skill and one away. Route once, inspect the saved assignee and explain both exclusions. The local course models deterministic selection, not concurrent production allocation. Use SLA evidence to discuss urgency without claiming that a view itself enforces a target.