Choose when owners should pull leads instead of receiving assignments
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A shared lead pool lets employees claim work when they have room. It can also let attractive leads disappear while difficult ones remain unowned. Direct assignment reverses the trade-off: a dispatcher selects someone, but that person may not be available.
Use push when allocation needs central coordination, controlled pull when employees can judge immediate capacity, and hybrid when flexibility needs a firm waiting limit. Choose the method whose failures your team can detect and resolve, not whichever empties the visible pool fastest.
1. Agree what counts as accepted ownership
The following is this article's proposed accountability convention, not a universal definition of assignment or a claim about software behaviour:
- Pull claim: An eligible employee checks qualification, availability, and intake capacity before claiming. The claim establishes operational ownership immediately; it is not a reservation.
- Push proposal: The dispatcher selects a recipient and remains responsible for resolving ownership until the recipient explicitly accepts.
- Transfer: The current owner remains accountable until another eligible employee acknowledges the handover. Requesting release does not complete a transfer.
A workspace might update its owner field as soon as someone assigns a record. Under this convention, that field alone does not demonstrate operational acceptance. Record acceptance separately if necessary, without assuming the workspace provides a dedicated control.
The baseline has no post-claim confirmation stage. Repeating the same checks after every claim adds administration without establishing ownership again. Investigate specific errors when they occur instead. These rules concern ownership intake, not subsequent follow-up priorities or shared-inbox handling.
2. Compare the failure each model exposes
Push assignment fits work requiring central coordination or a single qualified recipient. Employees need not monitor a pool. Its weakness is stale capacity information: proposals can accumulate against unavailable people. An acceptance deadline makes that failure visible.
Controlled pull fits reserved intake sessions where qualified employees choose work as capacity becomes available. It requires objective ordering, visible intake counts, and a custodian for exceptions. Its weaknesses are cherry-picking and claiming more work than employees can begin handling.
Hybrid assignment starts with a bounded pull opportunity, then switches unresolved leads to dispatcher-led allocation. Its weakness is a vague boundary: everyone may assume someone else will act. Specify both the fallback time and the subsequent acceptance deadline.
A controlled-pull session does not become hybrid merely because unresolved work is escalated for a coverage decision. It becomes hybrid if the operating rule routinely converts unclaimed records into push proposals. Keep that distinction explicit.
No model creates capacity. If every qualified employee is full, a manager must address workload or coverage rather than treating assignment as proof the work can be handled.
3. Filled decision table: choose by pool
Hypothetical reusable artifact: This table and the rule sheet below describe a fictional six-person enquiry team. All example counts, times, deadlines, and outcomes are hypothetical operating choices, not Alactic customer results or universal standards. Copy the structure and replace its entries with your decisions.
| Pool or condition | Model and reason | Unresolved-work rule | Reconsider when |
|---|---|---|---|
| General enquiries during coverage | Hybrid: several employees qualify, but immediate availability varies. | Duty dispatcher makes a push proposal after twenty staffed minutes, or escalates insufficient capacity. | Available employees consistently wait for push allocation. |
| Specialist enquiries with one qualified employee on duty | Push: there is no meaningful choice of claimant. | Dispatcher checks capacity and obtains acceptance. | Several specialists share coverage. |
| Reserved pool-clearing session, 14:00–14:30 | Controlled pull: qualified employees reserve time for intake. | At session end, unresolved records enter a manager-reviewed exception list, not automatic push allocation. | Exceptions repeatedly survive the reserved session. |
| Arrivals outside staffed coverage | Push at opening: nobody is staffed to accept overnight. | Opening dispatcher proposes recipients against actual capacity, without a new pull window. | Overnight waiting calls coverage into question. |
Assign the model by pool or coverage condition in advance. Letting employees choose it lead by lead undermines ordering and makes deadlines difficult to interpret.
4. Filled rule sheet: eligibility, order, and capacity
The following entries apply to both pull models. Qualification and capacity checks also apply before accepting push proposals or transfers.
- Roles: The roster names a duty dispatcher and backup. The manager maintains qualification criteria and approves capacity exceptions.
- Eligibility: Claim only categories covered by the employee's recorded qualification. The dispatcher classifies unclear records before they become claimable.
- Availability: The employee must be on duty and able to begin intake. Being signed in or below a numerical ceiling is insufficient.
- Claim order: Take the oldest eligible unowned lead, one at a time.
- Permitted skips: Record an eligibility mismatch, suspected duplicate, or missing classification information and notify the dispatcher.
- Prohibited skips: Apparent deal size, preferred source, familiarity, or the expectation that newer work is easier.
- Intake ceiling: An employee may hold no more than four owned leads awaiting substantive first handling, including work accepted through push.
- Slot release: Record a contact attempt and its outcome, or a completed qualification check with a substantive finding. Opening a record, changing status, or creating a task does not release a slot.
First handling releases an intake slot, not ownership. Existing callbacks and other obligations can still make an employee unavailable. Stop taking new work before leaving coverage and arrange any necessary transfers explicitly.
The dispatcher reviews skipped records alongside claims. Otherwise, an orderly claim log can conceal unwanted work. Preserve original arrival times through transfers and classification changes; moving a record must not make its waiting age disappear.
Hypothetical capacity exception: A manager raises an employee's ceiling from four to five until noon only after a colleague acknowledges taking over existing callbacks. The log records the work removed, current intake count, temporary ceiling, approver, and expiry. A helper taking a related task alone does not establish additional capacity. Exceptions never waive qualification or availability.
5. Filled rule sheet: separate escalation paths
Use the following clocks for their named pools only. Staffed time counts covered working periods; elapsed time preserves the full wait, including overnight gaps.
- General-enquiry hybrid check: After ten staffed minutes unclaimed, the dispatcher checks classification, eligibility, and coverage.
- General-enquiry hybrid fallback: At twenty staffed minutes, the pull opportunity ends. The dispatcher records a push proposal immediately or records that no eligible recipient has capacity and escalates to the manager.
- Controlled-pull session review: At 14:25, the session dispatcher lists remaining records and blockers so the session can close deliberately.
- Controlled-pull session end: At 14:30, stop new claims. The manager reviews every unresolved record, records its blocker, and names a custodian and next review time. In this hypothetical sheet, the next review is 14:45. There is no twenty-minute fallback or automatic push proposal.
- Controlled-pull next action: The manager may arrange further staffed pull capacity, resolve classification, or explicitly change the pool's model. Any exceptional push decision is logged as a model change, not presented as ordinary controlled pull.
The exception custodian is accountable for keeping the unresolved case visible, not for pretending a lead owner exists. If the manager is unavailable, the dispatcher retains custody, contacts the named backup, and records the outstanding decision.
Acceptance rules across models: A valid pull claim is immediate acceptance. Every push proposal, including an explicitly authorised exception, requires acceptance within five staffed minutes. A decline triggers immediate reassessment. Overdue acceptance goes to the manager, with unresolved status reviewed every five staffed minutes. Transfers require the receiving employee's acknowledgement; until then, the current owner remains accountable.
At shift handover, the incoming dispatcher acknowledges unresolved cases. Coverage ending does not erase missed deadlines. If an accepted claim later proves ineligible or unsupported by capacity, stop further claims and arrange an acknowledged transfer rather than silently returning it to the pool.
6. Worked example: calculate capacity and waiting
In this hypothetical morning, coverage opens at 09:00. Lead A arrived at 08:40. The dispatcher proposes Maya at 09:00; she accepts at 09:03. Arrival-to-ownership time is twenty-three elapsed minutes but three staffed minutes.
Jon already owns two leads awaiting substantive first handling. After checking qualification and availability, he claims B at 09:02 and C at 09:03. His intake count is two plus two, or four. He cannot claim another lead. There is no later confirmation task.
At 09:12, Jon records a contact attempt and outcome for B. His intake count falls to three. He may claim one more eligible lead only if his wider workload still permits it.
General-enquiry lead E arrives at 09:00 and remains unclaimed. Its hybrid window expires at 09:20. The dispatcher proposes Priya at that moment. She does not accept by 09:25, so the dispatcher escalates and withdraws the unanswered proposal before proposing an alternative. The alternative accepts at 09:29.
| Measure | Result | Meaning |
|---|---|---|
| Pull expiry | 09:20 | Planned hybrid fallback used. |
| Fallback delay | Zero staffed minutes | Dispatcher acted on time. |
| Initial acceptance deadline | 09:25, missed | The first proposal remained unanswered. |
| Eventual ownership | 09:29 | Twenty-nine staffed minutes unowned; resolution came four minutes after the initial deadline. |
Those final four minutes are not necessarily the alternative employee's acceptance delay. Measure each proposal against its own timestamp. If the dispatcher had first acted at 09:23, that would also create a separate three-minute fallback delay.
During the afternoon controlled-pull session, lead F remains unclaimed because its category is unclear. At 14:30, the manager names the dispatcher as classification custodian with a 14:45 review. F remains visibly unowned. No hybrid fallback clock applies.
7. Reusable filled operating-log entry
A useful log separates decisions from completed ownership. This filled hypothetical entry supports the session-end rule without adding a confirmation stage:
| Record and original arrival | F; 13:50 |
|---|---|
| Pool and model | 14:00–14:30 reserved session; controlled pull |
| Ownership state | Unowned; no claim or accepted proposal |
| Blocker | Category unclear; qualification cannot yet be established |
| Session-end action | 14:30 manager review completed; classification assigned to duty dispatcher |
| Custodian and next review | Duty dispatcher; 14:45 |
| Decision needed | Classify, then arrange staffed pull capacity or explicitly approve a model change |
| Resolution evidence | Pending; record eventual claim or proposal and acceptance timestamps |
For hybrid records, add pull expiry and actual fallback time. For push records, record each proposal, decline or withdrawal, and acceptance. Do not substitute a status change for those events.
8. Pilot the rules and inspect exceptions
Run a hypothetical five-staffed-day pilot on one pool. Publish qualifications, name dispatcher coverage, and rehearse an unanswered proposal and an unresolved session ending. Review arrival-to-ownership waiting, intake counts, skips, transfers, and exceptions.
Measure hybrid fallback use separately from late fallback. Frequent timely fallback may suggest push would be simpler; late fallback suggests a coverage or responsibility problem. Repeated controlled-pull carryovers suggest the session lacks time, skills, or capacity. Repeated invalid claims point to unclear eligibility checks.
These are recommended practices, not verified Alactic controls. Check availability in the workspace and current plan before relying on any control. A shared operating log can support the pilot without assuming automatic execution.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications