When two callers request the same employee, availability must be reserved centrally. A prompt telling the assistant to check whether someone is free cannot prevent two sessions from making the same decision simultaneously.
Staff availability is shared state
Simultaneous-caller management assigns limited receiving capacity across independent conversations. Represent the staff member’s usable capacity explicitly, including active calls, temporary reservations, and any manual unavailable state.
A proposed queue service atomically claims one capacity slot before starting the staff offer. The reservation has an identifier, an expiry, and an owning interaction. Acceptance converts the reservation into an active assignment. Rejection or caller abandonment releases it through an idempotent transition.
Presence alone is insufficient. “Online” may mean the employee’s application is connected, not that the employee can accept another conversation. State the operational meaning of available and make it visible to staff.
Walk through a fictional collision
At the same moment, callers A and B ask for Morgan. Morgan has capacity for one call. The queue gives A a temporary reservation and keeps B waiting with a clear choice of alternatives. If A abandons during ringing, that event releases the reservation; B can then receive an offer.
A delayed acceptance from A’s expired offer must not steal Morgan’s assignment after B has been connected. Match staff acceptance to the reservation identifier, then check that the reservation remains current before bridging audio.
| Concurrent event | Expected invariant |
|---|---|
| Two sessions request one slot | At most one current reservation |
| Worker restarts during offer | Reservation expires or is reconciled |
| Caller leaves the queue | No later unsolicited connection |
| Staff switches to unavailable | No new reservation is granted |
Test with controlled simultaneous requests rather than making two calls approximately together and hoping they overlap. Inspect the queue ledger and staff audio for the same interaction references.
Choose fairness rules deliberately
First-in-first-out is easy to explain, but a business may need separate queues for urgent work or existing appointments. Explicit priorities are easier to audit than allowing each agent to claim its caller is most important. Protect ordinary callers from indefinite starvation when higher-priority traffic continues.
Reservations add coordination work and can temporarily reduce utilisation when a caller disappears without a clean event. Short expiries help, but overly short expiries can create competing offers. Measure staff answer time before choosing values.
This is a proposed coordination design. The voice integration portfolio gives relevant background, and staffing-based transfer timeouts explains the related timing decision.
Simultaneous caller FAQ
Can each voice session maintain its own queue?
It can track its caller locally, but shared receiving capacity requires a common authority.
Should callers hear their exact queue position?
Only if the position is reliable and the priority rules make it meaningful. Otherwise explain the available options.
What if the employee answers outside the application?
The capacity model needs that signal or a conservative fallback. Missing external activity limits how accurately availability can be represented.