Customer service management may require different type of attentions and monitoring depending on parameters such as the different types of customer, priority, different products or services, different subscription levels (regular, premium customers), various activity categories, different geography etc.
Defining Queues is helpful to organize, monitor and prioritize the work by having a centralized list of pending work that needs attention and sorting tasks by type or by the people assigned to complete them
A queue is created by default for each and every user in D365 customer service, we can define additional queues based on our requirements as mentioned above. Let us define a queue and check further details. we have to define paramers for the queue
- Name: Name of the queue
- Type – Private or Public : Private queue is having access to limited members and we have to add the members to it. Where as public queues are accessible at organization level
- Incoming email address : All the messages sent to queue are send to this email Id
- We can select which emails can be converted to activities
Once we create the queue, the mailbox is auto created.
Few important things to be noted for queue based on my experience
- Queues are not included in solution, hence deployment can not be done with solution deployment. We did recreate the queues manually. There might be better ways to do it, I am yet to check
- Once the queue is enabled for any entity, it can not be disabled
- The items added to the queue are called as Queue items
- Any queue item, which is actually a record , can be added to only one at any point of time
- When two agents simultaneously add cases to the queue, then the system creates two queue items instead of a single queue item
- If we have created workflows or used custom API to assign cases to agents and if a same case is assigned to two agents at the same time, then the system creates two queue items instead of a single queue item
- From a queue, when an agent picks a case created by another agent and releases it, then the case gets assigned to the queue owner and not the agent who created the case
- If we have to delete any queue, it must be removed from routing rules and shall contain no queue items, otherwise queue can not be deleted
- When user releases or picks up the queue item, there is option to remove the item in queue or retain. By default it is retained. If we chose Yes to remove, the item will be removed from the queue
- Actual entity record and queue item are different, when we remove any item from queue, record will not be deleted
Creating queues in below easy steps
Go to Settings- Service Management- Queues
Enter all the details based on the requirement as explained above, with various options.
Once the queue is created, we can define the rule(s) to auto assign the items to the queue as shown below
In the rule we can define the filter criteria, which is similar to advanced find to match the records and if the record matches that criteria, it would be routed to the selected queue or user or team. Here we are discussing about queue, hence queue created in above step is selected
We have seen how to create queues and routing rules in this post Let us see continue to understand how to use the queues and how the routing rules work in next post
5 thoughts on “Queues in Case Management: Part 1”
Reblogged this on Nishant Rana's Weblog.
LikeLiked by 1 person
Thanks Vrushali for listing down the key points for quick reference.
LikeLiked by 1 person