Queue intake and priority

A queue begins with a source record, a number, a name and an arrival date. The organization identifies whose work it is; priority and SLA due date help the Queue Manager decide what needs attention. Individual tasks sit under that queue, so an operator can see the work that makes up the request rather than treating its title as the whole job. Queue Operations Overview gives an at-a-glance reading of status mix, SLA exposure, handler load and queues needing attention.

A higher priority does not by itself change ownership. The queue still needs its assignment rule and named owner. Keep the source record ID stable when the originating system changes its display label. That way a delayed task or correction stays tied to the same operational case.

The Queue Manager reviews new arrivals, then the Queue Operator works the assigned tasks.

• Arrival context. Record when the work arrived and which organization it belongs to.
• Attention order. Compare priority with SLA due date and open task count before choosing the next queue.
• One working parent. Keep each task under its queue, with sequence and source reference when supplied.

Agree how source records become queues, how priority is set and which business date determines the SLA due date. Decide whether the same source record can produce a new queue or should update the current one. Choose who can change priority and how the Queue Manager explains a change to the owner. Set the time zone for each organization before interpreting a due date during a daily review.

Walk through a sample queue with several tasks. Confirm which task is first, how a task outcome is recorded, and when open task count is refreshed. The queue’s status should tell the team where the work stands; a task’s outcome answers what happened to that task.

A client request arrives this morning with an SLA due tomorrow. The Queue Manager sees it beside older lower-priority work in Queued work by priority. They inspect its task descriptions, source reference and organization before choosing the applicable assignment rule. The assigned operator finds the queue and its named owner in Queues in progress. If a task cannot be completed, its pending outcome remains visible and the manager sees the queue among work in progress. A completed queue can still be inspected with its arrival and completion dates to explain the elapsed time.

The practical check is whether both people reach the same queue from the overview and the task list, and whether the owner knows which task remains open. No one should treat a new priority number as proof that assignment or execution already occurred.

• Queued work by priority — Arrived work ordered for attention with status, owner and SLA date.
• Queue status board — The same queues grouped by their working status.
• Queue Operations Overview — Live queue mix, SLA exposure and handler load.

Queue assignment shows how an arrived queue gains an owner and a review decision. Set up the first cycle covers the source and date choices.