We are trying to decide between standard queuing and bullseye routing for our technical support queue.
Our current data shows that standard queuing evenly distributes calls, but agents with specialized certifications (like network or security) receive the same volume as generalists. We want to prioritize routing to specialists first. Does bullseye actually improve first-call resolution, or just increase wait times for the customer?
Think of bullseye routing like throwing a dart at a target.
The innermost ring is your best match - the agent with the exact skill the customer needs. If nobody in that ring is available after your configured timeout (say, 15 seconds), the system expands to the next ring, which includes agents who are ‘good enough’. It keeps expanding until it reaches the outermost ring, which is basically anyone with a pulse and a headset.
The key is setting the right ring timeout. Too short and you waste your specialists. Too long and the customer abandons.
We ran an A/B test over 90 days comparing standard queuing to bullseye routing on our Tier 2 support queue.
| Metric | Standard Queue | Bullseye (15s rings) |
|---|---|---|
| FCR Rate | 62% | 78% |
| Avg Wait Time | 28s | 34s |
| CSAT Score | 3.8 | 4.3 |
| Transfer Rate | 22% | 9% |
Bullseye increased wait time by 6 seconds but dramatically improved FCR and reduced transfers. The math works.
From an Architect perspective, be careful with the ring expansion timeout when using bullseye inside a common module.
If your common module is called from multiple parent flows, each parent may set different participant data values that influence which ring the agent lands in. I maintain 50+ flows and have seen cases where a misconfigured parent flow sends every call to the outermost ring, completely bypassing the specialization logic.
Does the choice between standard and bullseye routing affect our real-time adherence numbers?
If bullseye keeps our specialists idle for longer periods waiting for their specific call type, WFM will flag them as ‘idle but on queue’ which might look bad on the adherence report even though they are technically available.
In CIC (PureConnect), we had a concept called ‘ACD Skill Utilization’ that was distinct from agent availability.
Genesys Cloud doesn’t separate these concepts as cleanly. The WFM adherence model treats ‘On Queue’ as ‘Available’, regardless of which bullseye ring the agent occupies. You’ll need to build a custom report if you want to prove that specialists are being properly utilized.