Routing & orchestration
ACD, skills-based & bullseye routing
The right agent, as quickly as possible. Queues, skills and routing strategies for Genesys Cloud CX, designed, tested and tuned by a certified QVCCS squad around your customers and people.
Genesys Cloud skills-based routing makes sure every call, message, email and workitem reaches the agent best placed to handle it. QVCCS designs ACD routing that balances speed and expertise: queues, skills and proficiency, language skills, evaluation methods, bullseye rings, preferred and last agent routing, conditional group activation and utilisation across every channel. Our certified team analyses your demand, document the routing design, configure it and prove it under realistic load, so customers reach the right person quickly and agents receive work that matches their abilities.
- Solution Architect
- Senior Business Consultant / Business Analyst
- Senior Developer
- Systems Integration Tester
- User Acceptance Test Lead
- Senior Platform Practice Lead (Genesys Cloud CX)
- Skills that mean somethingSkills, proficiency and language skills modelled on real expertise, with the right evaluation method chosen for each queue.
- Widen the net graduallyBullseye rings start with the best-matched agents and relax skill requirements ring by ring, balancing expertise against waiting.
- Relationships that continuePreferred agent routing and, for threaded email and messages, last agent routing reconnect customers with people who know them.
- Capacity across queues and channelsUtilisation limits concurrent work per channel, and conditional group activation shares agents only while other queues stay healthy.
- SkillsProficiency and evaluation
- LanguagesLanguage skills
- Bullseye ringsRelax skills over time
- Group activationShare agents by EWT
- Preferred agentAgent scores, six rings
- Last agentThreaded email, messages
- UtilisationCapacity per channel
Each queue combines a routing method, an evaluation method and capacity rules to choose the best available agent.
01
Why Genesys Cloud skills-based routing matters
Routing is the moment the contact centre keeps or breaks its promise. Send a customer to an agent without the right knowledge and the conversation ends in a transfer, a callback or a repeat contact. Hold out too long for the perfect agent and the customer waits while capable people sit idle. Genesys Cloud skills-based routing resolves that tension by matching each interaction's requirements – product, issue, language, priority, customer value – to the agents best able to handle it, and by defining exactly how far to compromise as time passes.
The benefits reach beyond service levels. Agents receive work they are trained for, which improves confidence and reduces burnout. New starters can be given simpler work while they build proficiency, and specialists can be protected for the contacts that need them. Supervisors gain a clear model they can adjust when demand shifts. QVCCS begins every routing engagement with discovery: contact-reason, volume and handle-time analysis, interviews with team leaders and a configuration audit of any existing org. The routing model that follows reflects how your contact centre wants to work, not a generic template.
02
How Genesys Cloud ACD and bullseye routing work
On Genesys Cloud CX, interactions arrive in queues, usually after an Architect flow has identified the customer and set the skills, language and priority they need. Each queue has a routing method – standard, bullseye, preferred agent, conditional group routing or predictive routing – and, for skills-based methods, an evaluation method. Best Available Skills favours the highest average proficiency among the longest-idle agents; All Skills Matching takes the longest-idle agent with every required skill; Disregard Skills, Next Agent ignores skills. Skill expression filters set in Architect can refine the pool further, and a scoring method decides how priority and waiting time rank interactions when agents are scarce.
Bullseye routing targets a sub-queue of agents with the exact skills, then relaxes requirements ring by ring as time passes. Preferred agent routing offers work first to named agents, using agent scores and up to six expansion rings. Last agent routing returns threaded emails and messages to the agent who handled them before; it does not apply to voice, and it is disabled on queues using preferred agent, conditional group or direct routing. Conditional group activation evaluates queue health, such as estimated wait time, and opens agent groups from other queues only while their own targets remain healthy. Utilisation, set at organisation or agent level, controls concurrent interactions per channel and which channels interrupt others.
Genesys describes bullseye routing as a set of concentric rings, like the rings on a target, each a fallback for the one inside it and each, in effect, a sub-queue of agents. Evaluation starts with the innermost ring. If no agent there becomes available within that ring's timeout, the pool widens to include the next ring, up to six in all, and agents in inner rings keep their priority if they free up first. There are two ways to build the rings: add groups of agents who hold the same skill at lower proficiency, or remove named skills from the requirement ring by ring so that more agents qualify.
Each approach suits different work. Adding groups with the same skill keeps the queue's skills and planning groups intact, which Genesys notes suits workforce management forecasting and scheduling. Removing skills suits queues using the All skills matching or Best available skills evaluation methods, where strict matching would otherwise leave interactions waiting. We set ring timeouts from your service levels, decide which skills can safely be relaxed and which never can, and test every ring with real agent states, so bullseye routing widens the net before the customer pays for the wait.
Interactive explainer: with JavaScript on, try a conditional group routing simulator showing which agent groups each ordered rule activates.
Great routing is a series of deliberate compromises: wait a little for the best agent, then widen the net before the customer pays for it.
03
Designing skills, queues and fallbacks
Skill sprawl is the classic routing mistake. Hundreds of narrowly defined skills, each held by a handful of agents, fragment the workforce and create queues that can never be staffed reliably. QVCCS designs skill models that are coarse enough to staff and fine enough to matter, using proficiency to express depth of expertise and choosing the evaluation method that suits each queue. We agree who owns skill assignment, how new starters progress and how changes are governed, and record it all in the low-level design, so the model stays accurate as people join, train and move teams.
Queue design follows the same principle. We decide when separate queues are justified – for distinct service levels, reporting or business ownership – and when skills within a shared queue work better. For every queue we define timed fallbacks: how quickly bullseye or preferred agent rings expand, which groups conditional group activation may borrow and at what thresholds, and how priority is scored. Genesys has said conditional group routing will not be enhanced further and recommends moving to conditional group activation, so we plan that migration for existing orgs. Every interaction has a defined path to a person, even on the busiest day.
Digital channels change the maths. An agent can hold several messaging conversations while only ever taking one call, and an email may wait in the background while a call interrupts it. Utilisation design, including utilisation labels where categories of work need their own limits, determines how channels and workitems coexist without overwhelming agents or leaving capacity unused. Our architects model blended working with your operations and workforce planning teams, align utilisation with service levels and forecasts, and document the reasoning in a design decision log, so supervisors understand why the ACD behaves as it does when they review performance.
04
Who designs your routing, and what we prove
Routing sits between operations, workforce planning, Architect flows and reporting, so we muster a multidisciplinary squad from our own bench around those four interests. A Senior Business Consultant / Business Analyst draws out the unwritten rules team leaders apply today and writes them as Given/When/Then criteria, such as which agents should receive a billing call in Welsh after thirty seconds. A Solution Architect owns queues, skills, methods, rings, activation thresholds and utilisation, and a Senior Developer scripts bulk skill and queue changes so the model can be maintained. The distinctive test work is timing: our Systems Integration Tester makes agents unavailable on purpose to prove rings expand and groups activate when the design says, and supervisors confirm in UAT that the behaviour matches how they manage the floor.
Priority is the setting most often misused. When every team argues its contacts are urgent, priority values creep upwards until they stop meaning anything, and low-priority work such as email can wait far longer than anyone intended. We agree a small, documented set of priority levels with a clear business reason for each, and model how the scoring method will rank interactions on a busy day before it goes live. We also design for the edges: what happens when no agent holds a required skill, when a queue is closed but interactions remain, and when a new starter has a skill at low proficiency. Each answer is written into the low-level design, so the people who maintain routing later understand why the edge cases behave as they do.
05
Tuning routing as your contact centre changes
Routing is never set and forgotten. New products, seasonal peaks, recruitment and changes to opening hours all alter the balance between speed and expertise, and skill assignments drift as people move teams. We review performance views by queue for wait times, transfers, abandonment and repeat contact, and look for the tell-tale signs of a model under strain: rings that expand on almost every interaction, activation rules that fire all day, or skills held by too few agents to staff. Changes are proposed through change control, and release impact assessments check whether Genesys has altered routing behaviour. Support follows your Genesys Cloud CX support model, alongside your provider or under a direct SLA. When your data is ready, we help you assess whether AI predictive routing could improve a chosen outcome.
What you get from QVCCS
- Contact reason and demand analysis to ground the routing model
- Skill, proficiency and language model with clear ownership
- Queue design with evaluation methods, rings and activation rules
- Preferred and last agent strategies where continuity matters
- Utilisation and blended working model across channels
- SIT and volume test evidence traced to requirements
- Supervisor guides, routing reviews and support aligned to your support model
Genesys documentation references
- Routing and evaluation methodshelp.genesys.cloud
- Advanced routing overviewhelp.genesys.cloud
- Last agent routing overviewhelp.genesys.cloud
- Conditional group routing overviewhelp.genesys.cloud
- Conditional Group Activation overviewhelp.genesys.cloud
- Configure utilisation at the org levelhelp.genesys.cloud
- Bullseye routing overviewhelp.mypurecloud.com
Methods & templates
ACD, skills-based & bullseye routing: quality gates, stage by stage
Every QVCCS engagement follows our seven-stage delivery lifecycle, each stage closed by a quality gate. For ACD, skills-based & bullseye routing, the work concentrates in Discover, Define, Design, Prove and Run & evolve, and these are the techniques and standard templates we lean on there, each one traceable from requirement to design, build, test and support.
- 01DiscoverDiscovery sign-off
- 02DefineRequirements baseline
- 03DesignDesign authority review
- 04BuildBuild complete
- 05ProveGo / no-go readiness
- 06TransitionOperational acceptance
- 07Run & evolveService reviews
Contact-reason, volume and handle-time analysis
Grounds the skill model and queue structure in real demand, so routing reflects the work customers actually bring rather than assumptions.
User stories and Given/When/Then acceptance criteria
Turns unwritten routing rules into testable statements about which agents should receive which interactions, and when fallbacks apply.
Design decision log
Records why each queue uses its routing method, evaluation method, ring timings, activation thresholds and utilisation settings.
SIT test pack
Proves each queue, ring expansion, fallback and channel blend against the requirements matrix before supervisors depend on it.
Performance and volume testing
Exercises routing with simulated peak volumes to confirm service levels hold and agents are not overloaded across channels.
Optimisation reviews against KPIs
Uses wait, transfer, abandonment and repeat-contact data to tune skills, rings and activation rules through controlled change.
How we deliver
ACD, skills-based & bullseye routing: your engagement at a glance
- 01Analyse demandStudy contact reasons, volumes, handle times and team structures, and capture today's unwritten routing rules as requirements.
- 02Design routingQueues, skills, routing and evaluation methods, fallbacks and utilisation documented in the HLD and LLD for design authority review.
- 03ConfigureCertified developers configure queues and upstream Architect flows to the LLD, automating bulk changes and peer reviewing every one.
- 04Prove realisticallySIT, volume and failover scenarios traced to requirements, then UAT with supervisors and planners before go-live.
- 05Review & tuneHypercare, support alongside your provider or direct from us, and optimisation reviews of waits, transfers and resolution, with changes under change control.
- Solution Architect
- Senior Business Consultant / Business Analyst
- Senior Developer
- Systems Integration Tester
- User Acceptance Test Lead
- Senior Platform Practice Lead (Genesys Cloud CX)
Every engagement follows our seven-stage method, with design authority, engineering standards and four-eyes peer review behind it. How we deliver →
In practice
Where we have delivered this, and related work
A major US resort and casino: Genesys Cloud CX beside its hotel PBX, with secure payments
How QVCCS put 125 agents of a major US resort and casino on Genesys Cloud CX beside its Avaya PBX, with secure card payments in the call path.
- Agents
- 125 concurrent
- Licence
- Genesys Cloud CX 3
A global industrial technology group: two always-open internal desks from NiCE CXone
How QVCCS moved a global technology group's always-open IT service desk and physical security desk from NiCE CXone to Genesys Cloud CX in a managed service.
- Users
- About 65
- Licence
- Genesys Cloud CX 3
A digital banking technology provider: its own Genesys Cloud CX after separation
How QVCCS gave a digital banking technology provider its own Genesys Cloud CX contact centre when it separated from its parent, inside a wide IT transformation.
- Agents
- 60
- Licence
- Genesys Cloud CX 1
Further reading
From QVCCS Innovation
- Borrowing agents safely: conditional group routing vs Conditional Group ActivationGenesys Cloud conditional group routing (CGR) vs conditional group activation (CGA): how rules work, EWT and idle agent conditions, bullseye, and migrating.07 July 2023
- Genesys Cloud workitems and task routing: a practical guide to Work AutomationA practical guide to Genesys Cloud Work Automation: worktypes, statuses, workbins, workitem routing, flows and triggers, and how QVCCS designs and delivers it.23 June 2023
- Auto answer in Genesys Cloud: voice, messaging and email, designed with careHow Genesys Cloud auto answer works for calls, messaging and email: where each is set, what agents see, how utilisation and reports behave, and when to use it.20 June 2023
Questions
ACD, skills-based & bullseye routing: common questions
What is bullseye routing in Genesys Cloud?
Bullseye routing widens the pool of agents for an interaction in stages, like the rings on a target. Genesys Cloud first looks for an agent in the innermost ring and, if none is available within that ring's timeout, expands to the next. Each ring either adds further groups of agents with the same skills, often at lower proficiency, or removes named skills from the requirement so that more agents qualify, balancing the best-suited agent against waiting time.
What is the difference between conditional group routing and conditional group activation?
Both let a queue borrow agent groups from other queues when it is under pressure, without harming their targets. Conditional group routing is a routing method that evaluates rules per interaction. Conditional group activation runs alongside standard, bullseye, preferred agent or predictive routing and periodically checks queue health. Genesys recommends migrating to activation, and we plan that move for you.
Does last agent routing work for voice calls?
No. In Genesys Cloud, last agent routing applies to threaded emails and messages, returning them to the agent who previously handled the conversation if they are on queue. It is disabled on queues that use preferred agent, conditional group or direct routing. For voice continuity we design preferred agent routing with agent scores instead.
How do utilisation settings work in Genesys Cloud?
Utilisation sets how many concurrent interactions of each type an agent can handle, for example one call but several messages, and which types can interrupt others. It is set at organisation level and can be overridden per agent, with utilisation labels for finer control.
Last reviewed