Use acceptance windows without letting leads bounce between owners
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A lead offered to an employee is not necessarily a lead that employee has accepted. If every unanswered assignment moves to another person, a queue can look active while nobody is accountable for resolving it.
Separate the pending recipient, accepted owner, and allocation decision-maker. Give each offer an acknowledgement window, limit replacement offers, and specify exactly how a held lead can become eligible for another offer.
This operating design concerns internal acceptance of responsibility, not prospect response deadlines or outreach. All people, records, times, and policy values below are hypothetical. The workflow is a recommendation, not a claim that a product executes it automatically.
1. Separate the offer from accepted ownership
A single owner field often hides two meanings: someone has received an offer, or someone has agreed to own the lead. Reporting both as assigned makes unacknowledged work difficult to distinguish from accepted work.
- Pending acceptance: one named recipient has an open offer but has not accepted responsibility.
- Accepted: the current recipient explicitly accepted the current offer and became the owner.
- Awaiting allocation decision: an offer ended through decline or expiry. No recipient has accepted; a named decision-maker must choose the next step.
- Held for allocation: further routine offers are blocked. A named decision-maker must resolve a documented capacity or eligibility constraint before any permitted exceptional offer.
Keep the allocation decision-maker visible while an offer is pending. That person owns the allocation task; the recipient owns the acknowledgement task. An expired offer is an event, not a new owner. Preserve its recipient, timing, and outcome without displaying that recipient as the accepted owner.
Define an allocation episode as the continuous attempt to establish ownership for one unresolved assignment need. It starts with the initial offer and ends when ownership is accepted or an authorised decision closes the need because allocation is no longer required. A hold does not end the episode.
2. Define the acknowledgement clock
A usable rule explains when the clock starts, what stops it, and what happens at the boundary.
Hypothetical policy: each offer has a 15-minute acknowledgement window during staffed allocation hours, 09:00–17:00 in a recorded local time zone. Only staffed minutes count. An offer issued at 16:55 expires at 09:10 on the next staffed day; an offer issued outside staffed hours starts its clock at the next opening.
- The clock starts when the offer is recorded and made available through the agreed work channel, not when someone opens it.
- Viewing a record, opening a notification, or appearing online does not count as acceptance.
- Acceptance must explicitly identify the current offer and be recorded before its deadline.
- A decline ends the offer immediately and includes a short reason.
- At the deadline, an unanswered offer expires. A reminder does not extend it.
Choose the duration around staffing and normal interruptions. Short windows expose unavailable recipients quickly but can create unnecessary escalations. Longer windows reduce interruptions while leaving ownership unresolved longer. If schedules differ, record the applicable schedule on each offer rather than relying on memory.
3. Bound routine offers and define release from hold
Hypothetical escalation policy: permit an initial offer and one reviewed replacement. Both declines and expiries consume an offer. There is no third routine offer.
- When the initial offer ends without acceptance, clear the pending recipient and move to awaiting allocation decision.
- The allocation decision-maker checks availability, eligibility, missing information, and the failure reason.
- That person authorises the single replacement or places the lead on hold.
- If the replacement fails, hold the lead rather than continuing employee-by-employee rotation.
In this example, Maya Chen makes allocation decisions, with Daniel Reed as backup. Maya has 10 staffed minutes after an offer ends to record a decision. If she misses that deadline, Daniel takes over the decision task. This changes neither the episode nor its offer count.
A hold needs a reason, responsible person, and next review time. A scheduled review alone does not authorise another offer. Release requires all of the following:
- A recorded material change: for example, an eligible employee has become available, or verified information corrects an eligibility restriction. Record what changed and the evidence used.
- A named authoriser: Maya or Daniel must explicitly approve the release and explain why the change addresses the previous failure.
- A history link: reference the existing episode, ended offers, hold decision, and new authorisation.
This policy permits one exceptional offer within the existing episode, not a new episode. It is recorded as offer three, exceptional, with the two routine offers still visible. Passing time, changing recipients, changing decision-makers, or reviewing a hold does not reset the count or justify release.
If the exceptional offer fails, no further offers are permitted in that episode under this policy. Escalate the unresolved staffing or eligibility problem to the named operational manager and keep the hold visible. Do not authorise repeated exceptions. Closing and recreating the same unresolved assignment need to bypass the limit is prohibited; a genuinely new need requires a documented explanation and a link to the prior history.
4. Keep a filled assignment register
The following reusable register is a hypothetical snapshot at 10:50 on a staffed day. A dash means the field is intentionally empty. Every timestamp uses the same recorded local time zone.
Lead | Episode | State | Pending | Accepted owner | Allocation lead | Offers used | Next action L-41 | E-41 | Accepted | — | Priya Shah | Maya Chen | 1 routine | None: accepted 09:06 L-42 | E-42 | Accepted | — | Sofia Patel | Maya Chen | 2 routine | None: accepted 09:31 L-43 | E-43 | Held for allocation | — | — | Maya Chen | 2 routine | Capacity review 11:00
For each episode, retain offer references, recipients, start times, deadlines, end times, outcomes, decline reasons, decision references, hold reasons, and review times. Keep the exceptional-offer allowance separate from the routine count so nobody mistakes it for an unused routine slot.
The snapshot shows current responsibility; the event history explains how it arose. For an accepted lead, Maya remains the historical allocation lead, but Priya or Sofia is now the owner. No acknowledgement clock remains open after acceptance.
The offer count belongs to the episode, not the employee. Neither a blank owner field nor a new recipient makes the history start again.
5. Follow the worked example through reopening
L-41: acceptance closes the episode
- 09:00: offer L-41-A opens for Priya Shah, due at 09:15.
- 09:06: Priya explicitly accepts. Offer and episode E-41 close through acceptance; Priya becomes owner.
A later deadline check must not expire this already accepted offer.
L-42: decline prompts a reviewed replacement
- 09:10: offer L-42-A opens for Ben Ortiz, due at 09:25.
- 09:13: Ben declines because he lacks the required account coverage. Maya's allocation decision is due at 09:23.
- 09:20: Maya records an eligibility review and authorises L-42-B for Sofia Patel, due at 09:35. This consumes the final routine offer.
- 09:31: Sofia accepts. Episode E-42 closes through acceptance.
The decline saves waiting time without bypassing review or erasing the initial offer.
L-43: expiry, hold, and one justified exception
- 10:00: offer L-43-A opens for Noah Kim, due at 10:15.
- 10:15: the unanswered offer expires. Maya's decision is due at 10:25.
- 10:21: Maya authorises a replacement after reviewing the available information.
- 10:22: L-43-B opens for Elena Rossi, due at 10:37.
- 10:37: the replacement expires. E-43 enters held for allocation; Maya's resolution decision is due at 10:47.
- 10:44: Maya records hold H-43: no eligible recipient is confirmed available. She schedules an 11:00 capacity review.
- 11:00: the review confirms no change. Maya keeps H-43 active, records the unresolved constraint, and sets an 11:30 review. No offer is issued merely because a review occurred.
- 11:20: Priya's recorded availability changes after previously allocated work ends. Maya checks that Priya is eligible for L-43.
- 11:24: Maya records release decision D-43-C and authorises the single exceptional offer within E-43.
- 11:25: L-43-C opens for Priya, due at 11:40. Its record shows two routine offers used and the exceptional allowance consumed.
- 11:29: Priya accepts. E-43 closes through accepted ownership.
The filled release record below can be reused as a decision format. Its values are hypothetical.
Lead / episode: L-43 / E-43
Hold reference: H-43, recorded 10:44
Previous offers: L-43-A expired; L-43-B expired
Material change: Priya's availability changed at 11:20;
Maya verified eligibility for this lead
Authoriser: Maya Chen
Decision reference / time: D-43-C / 11:24
Decision: Release hold for one exceptional offer in E-43
New offer: L-43-C to Priya Shah, 11:25–11:40
Count: Routine 2 of 2; exceptional 1 of 1
Failure action: Return to hold; escalate to Daniel Reed
as operational manager; no further offers
Outcome: Accepted 11:29; episode closedHad Priya declined or timed out, E-43 would have returned to hold with its allowance exhausted. Another availability change would not create a fourth offer under this policy.
6. Handle late actions and unreliable records
- Late acceptance: an ended offer cannot establish ownership. Preserve the attempted action and refer the employee to the allocation decision-maker.
- Boundary disputes: use one authoritative recorded time and the published deadline rule, not competing device screenshots.
- Duplicate offers: reconcile them before proceeding. Permit only one active offer and one accepted owner per episode.
- Notification failure: distinguish it from silence. Investigate the unavailable route before sending further offers through it.
- Recipient absence: record the decision ending the offer; do not silently overwrite the name.
- Decision-maker absence: transfer the decision task to the backup without resetting any allowance.
If an outage makes ownership history unreliable, pause replacement offers until the record is reconciled. Preserve original deadlines and record recovery decisions rather than backdating acceptance. Once accepted, a later ownership transfer belongs to a separate documented handoff, not a reopened acknowledgement clock.
7. Verify the workflow before automating it
Start with a controlled register the team can operate manually. If using Alactic CRM, check the current workspace and plan for relevant recording and workflow availability. Do not assume the same capabilities exist in Alactic Communications, ACID business-assistant workflows, or the Android app.
Any automated implementation needs explicit authorisation and tests of state changes, not just notifications. Check that acceptance prevents expiry, decline blocks late acceptance, replacements require decisions, and hold release requires the recorded change and authoriser. Test staffed-hours boundaries, backup decisions, and attempts to reset an exhausted episode.
A useful decision notice includes the lead, episode, ended offer, reason, counts, deadline, and permitted next actions. A message saying only that assignment failed leaves the central decision unresolved.
8. Review ownership gaps, not just timeout totals
For a hypothetical five-staffed-day pilot, track time from initial offer to accepted ownership, including time awaiting decisions and on hold. Separate acceptances, declines, and expiries; review late decisions, overdue holds, exceptional releases, and conflicting ownership records.
Keep unresolved episodes visible rather than excluding them from reporting. Examine whether release records identify real changes, whether the named authoriser made the decision, and whether any supposedly new episode merely disguises the same unresolved need.
Low timeout counts can conceal employees accepting merely to stop the clock. High counts may reveal inaccurate availability rather than an overly short window. The practical test is whether each episode reaches accepted ownership or a documented, actively managed hold without unexplained recipient changes or replenished offer allowances.
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