Certification and Training

One of the most common things we work with in CX is the queue. We configure them, route to them, report on them, and talk about them all the time.

But at some point I realized something: a lot of people know that interactions go into a queue, but not always what actually happens next. So here's the simple version.

When a customer interaction (voice, message, email) enters a queue in Genesys Cloud, it does not immediately get handed to the next available person (necessarily).

First, Genesys Cloud ACD looks at the queue's routing method to determine how it should match that interaction with an agent. In other words, the queue is not just a waiting room. It is part of the decision-making process

From there, several things can come into play.

Time
How long has the interaction been waiting?
How long has an agent been idle?

Skills
Does the interaction require a specific language, product knowledge, or certification?

Priority
Should this interaction be treated as more important than others already waiting?

Customer preference and interaction history
Is there a preferred agent? Has this customer spoken with someone before?

Agent utilization
Who is available, and who is in the best position to take the interaction? Genesys Cloud routing can evaluate factors like time, skill, priority, customer preference, interaction history, agent utilization, the queue, and the flow itself when matching interactions to agents

That's why queue routing is more interesting than it looks.

In the most basic setup, standard routing builds a list of available agents and uses time as the main decision driver. The interaction typically goes to the agent who has been idle the longest

But that is only the beginning.

Depending on how the queue is configured, routing can get much smarter:

• Bullseye routing expands the agent pool over time if no one is immediately available with the ideal skills
• Preferred agent routing tries a designated set of preferred agents first, then falls back to a wider group if needed
• Conditional group routing shares groups of agents across queues based on rules like estimated wait time and agent availability
• Predictive routing uses machine learning to rank the available agents in the target pool based on which match is most likely to improve a selected KPI

So when a customer interaction enters a queue, what happens is not just "wait until someone is free."

What really happens is that Genesys Cloud starts evaluating the best possible match based on the routing strategy you have designed.

That is why queue design matters so much. Because the customer experience is not only shaped by the flow they came through. It is also shaped by the logic that decides who gets them, when, and under what conditions.

Do you want to know about Routing in Genesys Cloud, do not forgot to check our courses at Education: Genesys Cloud: Contact Center Administration and Webinar: Genesys Cloud CX: Advanced Routing Methods

Curious to hear how others explain this: when you talk about queues with newer users, what part tends to surprise them most?

One of the most common things we work with in CX is the queue. We configure them, route to them, report on them, and talk about them all the time.

But at some point I realized something: a lot of people know that interactions go into a queue, but not always what actually happens next. So here's the simple version.

When a customer interaction (voice, message, email) enters a queue in Genesys Cloud, it does not immediately get handed to the next available person (necessarily).

First, Genesys Cloud ACD looks at the queue's routing method to determine how it should match that interaction with an agent. In other words, the queue is not just a waiting room. It is part of the decision-making process

From there, several things can come into play.

Time
How long has the interaction been waiting?
How long has an agent been idle?

Skills
Does the interaction require a specific language, product knowledge, or certification?

Priority
Should this interaction be treated as more important than others already waiting?

Customer preference and interaction history
Is there a preferred agent? Has this customer spoken with someone before?

Agent utilization
Who is available, and who is in the best position to take the interaction? Genesys Cloud routing can evaluate factors like time, skill, priority, customer preference, interaction history, agent utilization, the queue, and the flow itself when matching interactions to agents

That's why queue routing is more interesting than it looks.

In the most basic setup, standard routing builds a list of available agents and uses time as the main decision driver. The interaction typically goes to the agent who has been idle the longest

But that is only the beginning.

Depending on how the queue is configured, routing can get much smarter:

• Bullseye routing expands the agent pool over time if no one is immediately available with the ideal skills
• Preferred agent routing tries a designated set of preferred agents first, then falls back to a wider group if needed
• Conditional group routing shares groups of agents across queues based on rules like estimated wait time and agent availability
• Predictive routing uses machine learning to rank the available agents in the target pool based on which match is most likely to improve a selected KPI

So when a customer interaction enters a queue, what happens is not just "wait until someone is free."

What really happens is that Genesys Cloud starts evaluating the best possible match based on the routing strategy you have designed.

That is why queue design matters so much. Because the customer experience is not only shaped by the flow they came through. It is also shaped by the logic that decides who gets them, when, and under what conditions.

Do you want to know about Routing in Genesys Cloud, do not forgot to check our courses at Education: Genesys Cloud: Contact Center Administration and Webinar: Genesys Cloud CX: Advanced Routing Methods

Curious to hear how others explain this: when you talk about queues with newer users, what part tends to surprise them most?

My 2 cents...

Note that when a conversation gets transferred to a queue, the In-Queue flow starts running (always for calls, other media types may not have an In Queue flow).

That In-Queue flow keeps running until the conversation is Connected to an agent. That means if you have functionality in the In-Queue flow (such as a timeout and transfer to a back-up queue) it's a race condition, and can actually "steal" the conversation away from an agent during Alerting (especially confusing if you are not using auto-answer and the conversation alerts for, say, 10 seconds then suddenly disappears from the client).

One of the most common things we work with in CX is the queue. We configure them, route to them, report on them, and talk about them all the time.

But at some point I realized something: a lot of people know that interactions go into a queue, but not always what actually happens next. So here's the simple version.

When a customer interaction (voice, message, email) enters a queue in Genesys Cloud, it does not immediately get handed to the next available person (necessarily).

First, Genesys Cloud ACD looks at the queue's routing method to determine how it should match that interaction with an agent. In other words, the queue is not just a waiting room. It is part of the decision-making process

From there, several things can come into play.

Time
How long has the interaction been waiting?
How long has an agent been idle?

Skills
Does the interaction require a specific language, product knowledge, or certification?

Priority
Should this interaction be treated as more important than others already waiting?

Customer preference and interaction history
Is there a preferred agent? Has this customer spoken with someone before?

Agent utilization
Who is available, and who is in the best position to take the interaction? Genesys Cloud routing can evaluate factors like time, skill, priority, customer preference, interaction history, agent utilization, the queue, and the flow itself when matching interactions to agents

That's why queue routing is more interesting than it looks.

In the most basic setup, standard routing builds a list of available agents and uses time as the main decision driver. The interaction typically goes to the agent who has been idle the longest

But that is only the beginning.

Depending on how the queue is configured, routing can get much smarter:

• Bullseye routing expands the agent pool over time if no one is immediately available with the ideal skills
• Preferred agent routing tries a designated set of preferred agents first, then falls back to a wider group if needed
• Conditional group routing shares groups of agents across queues based on rules like estimated wait time and agent availability
• Predictive routing uses machine learning to rank the available agents in the target pool based on which match is most likely to improve a selected KPI

So when a customer interaction enters a queue, what happens is not just "wait until someone is free."

What really happens is that Genesys Cloud starts evaluating the best possible match based on the routing strategy you have designed.

That is why queue design matters so much. Because the customer experience is not only shaped by the flow they came through. It is also shaped by the logic that decides who gets them, when, and under what conditions.

Do you want to know about Routing in Genesys Cloud, do not forgot to check our courses at Education: Genesys Cloud: Contact Center Administration and Webinar: Genesys Cloud CX: Advanced Routing Methods

Curious to hear how others explain this: when you talk about queues with newer users, what part tends to surprise them most?

One of the most common things we work with in CX is the queue. We configure them, route to them, report on them, and talk about them all the time.

But at some point I realized something: a lot of people know that interactions go into a queue, but not always what actually happens next. So here's the simple version.

When a customer interaction (voice, message, email) enters a queue in Genesys Cloud, it does not immediately get handed to the next available person (necessarily).

First, Genesys Cloud ACD looks at the queue's routing method to determine how it should match that interaction with an agent. In other words, the queue is not just a waiting room. It is part of the decision-making process

From there, several things can come into play.

Time
How long has the interaction been waiting?
How long has an agent been idle?

Skills
Does the interaction require a specific language, product knowledge, or certification?

Priority
Should this interaction be treated as more important than others already waiting?

Customer preference and interaction history
Is there a preferred agent? Has this customer spoken with someone before?

Agent utilization
Who is available, and who is in the best position to take the interaction? Genesys Cloud routing can evaluate factors like time, skill, priority, customer preference, interaction history, agent utilization, the queue, and the flow itself when matching interactions to agents

That's why queue routing is more interesting than it looks.

In the most basic setup, standard routing builds a list of available agents and uses time as the main decision driver. The interaction typically goes to the agent who has been idle the longest

But that is only the beginning.

Depending on how the queue is configured, routing can get much smarter:

• Bullseye routing expands the agent pool over time if no one is immediately available with the ideal skills
• Preferred agent routing tries a designated set of preferred agents first, then falls back to a wider group if needed
• Conditional group routing shares groups of agents across queues based on rules like estimated wait time and agent availability
• Predictive routing uses machine learning to rank the available agents in the target pool based on which match is most likely to improve a selected KPI

So when a customer interaction enters a queue, what happens is not just "wait until someone is free."

What really happens is that Genesys Cloud starts evaluating the best possible match based on the routing strategy you have designed.

That is why queue design matters so much. Because the customer experience is not only shaped by the flow they came through. It is also shaped by the logic that decides who gets them, when, and under what conditions.

Do you want to know about Routing in Genesys Cloud, do not forgot to check our courses at Education: Genesys Cloud: Contact Center Administration and Webinar: Genesys Cloud CX: Advanced Routing Methods

Curious to hear how others explain this: when you talk about queues with newer users, what part tends to surprise them most?

Hi @Rodrigo Soares,

One of the most common things we work with in CX is the queue. We configure them, route to them, report on them, and talk about them all the time.

But at some point I realized something: a lot of people know that interactions go into a queue, but not always what actually happens next. So here's the simple version.

When a customer interaction (voice, message, email) enters a queue in Genesys Cloud, it does not immediately get handed to the next available person (necessarily).

First, Genesys Cloud ACD looks at the queue's routing method to determine how it should match that interaction with an agent. In other words, the queue is not just a waiting room. It is part of the decision-making process

From there, several things can come into play.

Time
How long has the interaction been waiting?
How long has an agent been idle?

Skills
Does the interaction require a specific language, product knowledge, or certification?

Priority
Should this interaction be treated as more important than others already waiting?

Customer preference and interaction history
Is there a preferred agent? Has this customer spoken with someone before?

Agent utilization
Who is available, and who is in the best position to take the interaction? Genesys Cloud routing can evaluate factors like time, skill, priority, customer preference, interaction history, agent utilization, the queue, and the flow itself when matching interactions to agents

That's why queue routing is more interesting than it looks.

In the most basic setup, standard routing builds a list of available agents and uses time as the main decision driver. The interaction typically goes to the agent who has been idle the longest

But that is only the beginning.

Depending on how the queue is configured, routing can get much smarter:

• Bullseye routing expands the agent pool over time if no one is immediately available with the ideal skills
• Preferred agent routing tries a designated set of preferred agents first, then falls back to a wider group if needed
• Conditional group routing shares groups of agents across queues based on rules like estimated wait time and agent availability
• Predictive routing uses machine learning to rank the available agents in the target pool based on which match is most likely to improve a selected KPI

So when a customer interaction enters a queue, what happens is not just "wait until someone is free."

What really happens is that Genesys Cloud starts evaluating the best possible match based on the routing strategy you have designed.

That is why queue design matters so much. Because the customer experience is not only shaped by the flow they came through. It is also shaped by the logic that decides who gets them, when, and under what conditions.

Do you want to know about Routing in Genesys Cloud, do not forgot to check our courses at Education: Genesys Cloud: Contact Center Administration and Webinar: Genesys Cloud CX: Advanced Routing Methods

Curious to hear how others explain this: when you talk about queues with newer users, what part tends to surprise them most?

One of the most common things we work with in CX is the queue. We configure them, route to them, report on them, and talk about them all the time.

But at some point I realized something: a lot of people know that interactions go into a queue, but not always what actually happens next. So here's the simple version.

When a customer interaction (voice, message, email) enters a queue in Genesys Cloud, it does not immediately get handed to the next available person (necessarily).

First, Genesys Cloud ACD looks at the queue's routing method to determine how it should match that interaction with an agent. In other words, the queue is not just a waiting room. It is part of the decision-making process

From there, several things can come into play.

Time
How long has the interaction been waiting?
How long has an agent been idle?

Skills
Does the interaction require a specific language, product knowledge, or certification?

Priority
Should this interaction be treated as more important than others already waiting?

Customer preference and interaction history
Is there a preferred agent? Has this customer spoken with someone before?

Agent utilization
Who is available, and who is in the best position to take the interaction? Genesys Cloud routing can evaluate factors like time, skill, priority, customer preference, interaction history, agent utilization, the queue, and the flow itself when matching interactions to agents

That's why queue routing is more interesting than it looks.

In the most basic setup, standard routing builds a list of available agents and uses time as the main decision driver. The interaction typically goes to the agent who has been idle the longest

But that is only the beginning.

Depending on how the queue is configured, routing can get much smarter:

• Bullseye routing expands the agent pool over time if no one is immediately available with the ideal skills
• Preferred agent routing tries a designated set of preferred agents first, then falls back to a wider group if needed
• Conditional group routing shares groups of agents across queues based on rules like estimated wait time and agent availability
• Predictive routing uses machine learning to rank the available agents in the target pool based on which match is most likely to improve a selected KPI

So when a customer interaction enters a queue, what happens is not just "wait until someone is free."

What really happens is that Genesys Cloud starts evaluating the best possible match based on the routing strategy you have designed.

That is why queue design matters so much. Because the customer experience is not only shaped by the flow they came through. It is also shaped by the logic that decides who gets them, when, and under what conditions.

Do you want to know about Routing in Genesys Cloud, do not forgot to check our courses at Education: Genesys Cloud: Contact Center Administration and Webinar: Genesys Cloud CX: Advanced Routing Methods

Curious to hear how others explain this: when you talk about queues with newer users, what part tends to surprise them most?

One of the most common things we work with in CX is the queue. We configure them, route to them, report on them, and talk about them all the time.

But at some point I realized something: a lot of people know that interactions go into a queue, but not always what actually happens next. So here's the simple version.

When a customer interaction (voice, message, email) enters a queue in Genesys Cloud, it does not immediately get handed to the next available person (necessarily).

First, Genesys Cloud ACD looks at the queue's routing method to determine how it should match that interaction with an agent. In other words, the queue is not just a waiting room. It is part of the decision-making process

From there, several things can come into play.

Time
How long has the interaction been waiting?
How long has an agent been idle?

Skills
Does the interaction require a specific language, product knowledge, or certification?

Priority
Should this interaction be treated as more important than others already waiting?

Customer preference and interaction history
Is there a preferred agent? Has this customer spoken with someone before?

Agent utilization
Who is available, and who is in the best position to take the interaction? Genesys Cloud routing can evaluate factors like time, skill, priority, customer preference, interaction history, agent utilization, the queue, and the flow itself when matching interactions to agents

That's why queue routing is more interesting than it looks.

In the most basic setup, standard routing builds a list of available agents and uses time as the main decision driver. The interaction typically goes to the agent who has been idle the longest

But that is only the beginning.

Depending on how the queue is configured, routing can get much smarter:

• Bullseye routing expands the agent pool over time if no one is immediately available with the ideal skills
• Preferred agent routing tries a designated set of preferred agents first, then falls back to a wider group if needed
• Conditional group routing shares groups of agents across queues based on rules like estimated wait time and agent availability
• Predictive routing uses machine learning to rank the available agents in the target pool based on which match is most likely to improve a selected KPI

So when a customer interaction enters a queue, what happens is not just "wait until someone is free."

What really happens is that Genesys Cloud starts evaluating the best possible match based on the routing strategy you have designed.

That is why queue design matters so much. Because the customer experience is not only shaped by the flow they came through. It is also shaped by the logic that decides who gets them, when, and under what conditions.

Do you want to know about Routing in Genesys Cloud, do not forgot to check our courses at Education: Genesys Cloud: Contact Center Administration and Webinar: Genesys Cloud CX: Advanced Routing Methods

Curious to hear how others explain this: when you talk about queues with newer users, what part tends to surprise them most?