Collections

Work distribution

Accounts reach a collector by assignment. A supervisor assigns them in bulk from the collections list, or an administrator runs the distribution tool, which spreads a run's accounts across collectors by current workload.

Written for: Collections supervisors · Administrators · Evaluators

Assigning accounts in bulk

Sidebar → Patient AR → Collections

  1. Open Patient AR → Collections for the whole account list. (A queue's own screen has no bulk assign.)
  2. Filter to the accounts you want, then select them.
  3. Choose the bulk assign action and pick the collector.

Expected result: any current assignment on those accounts is released and a new one is created for the chosen collector. The accounts then appear in that collector's Get Next Account on any queue that contains them. Assignments made this way do not expire; they last until released or reassigned. No notification is sent to the collector.

The Queue Distribution screen

Sidebar → Management → Queue Distribution

Distribute assigns a queue's unassigned accounts to active users with the Agent role; Rebalance redistributes an existing queue. Accounts go out highest priority first (priority 1 = High), oldest first within a priority. Each account goes to the collector with the fewest open assignments at that moment, counting the ones they already held and the ones given to them earlier in the same run, so a run spreads evenly across collectors. When collectors tie, they take turns in a fixed order. No collector is given more than the run's Max Accounts Per Agent (50 by default) in total; once every collector is at that cap, the remaining accounts stay unassigned and the screen says how many. The screen offers two strategies. What each one does in this release:

Field or controlWhat it means
Round robinEach account to the collector with the fewest open assignments; tied collectors take turns. Same behaviour as Balanced workload.
Balanced workloadEach account to the collector with the fewest open assignments; tied collectors take turns.

What is not implemented

There are no saved auto-assignment rules, no assignment schedule and no stored maximum workload per collector (Distribute takes a per-run Max Accounts Per Agent, 50 by default; Rebalance always uses 50), no value-weighted or skill-based routing and no notification to a collector on assignment. Earlier versions of this page described those as settings; they were never built. Time-zone-aware assignment is also absent - see contact strategies for what that means for calling hours.

Related documentation