エージェントの仕事量を平準化するキャパシティルールの作成



image avatar

Jacquelyn Brewer

Zendesk Documentation Team

編集日時:2025年3月19日


0

0

56件のコメント

0


Hi everyone!

I have a question regarding Messaging. Does anyone know if it's possible to enable the Accept button when a messaging chat transitions from an Inactive session state back to Active?

Currently, we have a trigger that unassigns the messaging ticket and reassigns it to a group. However, when the session becomes Active again, we'd like to notify messaging agents—preferably via the Accept button, Conversation button, or an alert—so that any available agent can accept and continue the chat.

Has anyone found a way to accomplish this? Appreciate any insights! TIA. 

0


Hi 1263082080589 , thanks for the update today.  If you or 1263082108669 could refer to me to the post discussing the feature to “stagger” OCR related ticket assignments over time, that would be great!

0


We need more roles to have permissions to edit settings. This is a feature for team leaders, and not everyone needs to be an administrator.

1


Hi 1263082080589 ,

My recent concern was specific to agent status toggling, of which there is no documentation regarding if they will default to “Online”, “Offline”, if a default can be set for agents in a particular capacity rule, etc.  I know we are meeting on Monday, so may be best to clear this all up early next week.  Thanks.

0


Hi 1263169422950 

Sorry for the confusion: the agents with zero capacity can still be assigned support tickets manually either self assiginging from views or being manually assigned tickets from supervisors. Its the routing engine that will not assign them tickets

0


Hi 1263082080589 ,

 

I think there is a misunderstanding here.  The ~200 agents not using OCR will still NEED to be assigned tickets, just not in an OCR capacity, if that makes sense.  The tickets would get assigned manually to them or via transfer of ticket to their ticket group.  In that respect, I'd want them to not have to worry about agent status and receive tickets manually as they always had.  I have only 8 agents or so that I want to test OCR with, and dealing with the other 200 agents is proving problematic.  I'd love to speak with someone close to this feature to find a way to get this implemented, as I've had so many stops and starts.

0


HI 1263169422950 

Those agents with zero max capacity will not be assigned tickets, independent of what their agent status is set to. So those agents can just ignore their agent status

 

Barry

0


Hi 1263082080589 , for the rule with the 300+ agents with 0 capacity, would those agents have to adjust to having to set an agent status when navigating to the agent interface?  Since they are not going to be active for OCR at this time, I would want to ensure they don't have to adhere to a workflow that is irrelevant to them, and could prevent them from receiving tickets.

0


Hi 1263082080589, regarding your comment reply to D. Fitz on Nov 5. Are there any plans in the future to implement some improvements to cater for this scenario? It would be nice to have some configuration on these tickets that were already replied to that were there before agent signed in (to automatically move to On-Hold so they can receive the more time pressing tickets) or another method. 

 

Currently we are experiencing a similar problem and we've set up some automations to unassign tickets after being held for some time and changing priorities when the SLA is about to breached, though it is more of a workaround for now.  Increasing the capacity isn't really the best solution since:

- If people sign on too early, they get all the nearly SLA breached tickets. Even though who sign on a few minutes afterwards may not get some of that workload and they would need to wait for a team leader to sign on to reassign tickets manually.

- Or people who sign on a little later may not receive any tickets since everyone has higher capacity. They need a team leader to reassign tickets to them manually. 

 

Thanks.

1


サインインしてコメントを残してください。