Accept or reject a lead
Respond to Round Robin and Broadcast offers without leaving a lead in limbo.
Make a fast, explicit ownership decision while the opportunity is still available and help the routing path continue without manual intervention.
Why it matters
Accept and Reject are operational signals, not simple buttons. Acceptance gives one teammate ownership and unlocks the working record; rejection frees the route to try another eligible recipient. Clear decisions can reduce lead response time and prevent paid enquiries from waiting in an informal handoff.
See it in HoneyFalcon
Step 1 of 3: pending offer, timer context, Accept lead, and Reject actions.
Step 2 of 3: owned state after acceptance.
Step 3 of 3: expired or rejected offer represented as non-actionable history.
Make the right decision quickly
Accept when you can own the next contact
Accept claims the lead for your account and moves it into active work. In Broadcast, the first valid acceptance wins and the offer stops being available to the other recipients. In Round robin, acceptance closes that pending offer.
Reject when another teammate should receive the chance
Reject records your decision and allows the configured route to continue. The rejecting member is not offered the same lead again in that Broadcast cycle, leaving the opportunity available to the remaining eligible recipients.
Understand Round robin expiry
A non-buffer Round robin offer can expire according to the configured in-hours or out-of-hours window. Reallocation is processed asynchronously, so the next offer can appear after the scheduled routing task runs rather than at the exact second displayed by the timer.
Know how Broadcast ownership is established
Broadcast can make the opportunity visible to multiple eligible teammates. The first valid acceptance becomes the owner, which means a later click may correctly return a conflict because the lead is no longer available.
Terminal rescue protects the final opportunity
When the normal route is exhausted, HoneyFalcon offers the lead to the active designated buffer. If no eligible buffer exists, the deterministic firm-admin fallback is used. Rescue offers do not expire.
A practical response scenario
A specialist receives an offer during a busy call. If the specialist can follow up, Accept creates clear ownership immediately. If not, Reject gives the remaining eligible team the chance to respond instead of waiting for a private message or the timer.
That explicit choice is what makes round robin and broadcast lead routing work as a team process rather than a shared inbox.
If Accept or Reject returns a conflict, refresh the lead before trying again. Another recipient may already own it, or the visible offer may no longer be current.
The decision flow is healthy when
- Accept moves the offer into the winning agent's active work with the available details unlocked.
- Reject records the decision and allows the route to continue without leaving the offer actionable for that user.
- An expired offer no longer appears valid while asynchronous reallocation completes.
- A stale Broadcast click cannot create a second owner.