Service | Customer Service, Contact Center, Fie...

How to identify who rejected or missed a notification for a new call/conversation in Omnichannel

(0) Share

Report

Posted on by Sergio Banguero

Hi - Agents have the option to accept, reject or miss (no action) on incoming conversations notifications.

Routing diagnostics shows this live, but then it has no record as it is just interested in assignment and routing.

Where is this information about conversations rejected/missed/accepted stored?

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

RudyZhang Microsoft Employee on at

Like (0)

Report

Hi,

Your request to see who rejected the conversation is not supported.

Our team has tried to reproduce your actions, including creating a Workstream, creating a chat widget, simulating a customer conversation reject, looking at suspicious tables in the Dataverse (e.g., notifications, etc.), but have not found the appropriate records.

Based on our team's investigation, we propose two possible alternatives
Option 1: Turn on auditing, you can turn on auditing for a specific entity to view the change history of that entity's records. But this method is very time consuming.

Option 2: According to the official documentation, for missed notifications or rejected notifications, administrators can enable the "Agent Missed" and "Agent Rejected" features. When an Agent misses or rejects a notification, the status will be set to "Inactive" and "Do not disturb". Administrators can manually view agents in these two states.

For more information about these two features, please refer to the official documentation in the link below.
https://learn.microsoft.com/en-us/dynamics365/customer-service/oc-notifications#missed-notifications
https://learn.microsoft.com/en-us/dynamics365/customer-service/oc-notifications#agent-reject-notifications

In fact, both of the above solutions have their own drawbacks and can only partially meet your needs, if you think you need this feature is indispensable, you can use the following link to propose your idea.
https://experience.dynamics.com/ideas/

I hope my answer is helpful to you! If you have any other questions, please feel free to contact me.

Best Regards,
Rudy Zhang

Was this reply helpful? Yes No
Sergio Banguero 4 on at

Like (0)

Report

Thanks for the response, unfortunately it does not really answer the question.

We opened a ticket simultaneously and got a very interesting suggestion from MS Support.

Using the PowerBI data model, just create a report that shows a list of conversations/sessions and mark if they are rejected or not

Was this reply helpful? Yes No
Suggested answer

GC-29041623-0 6 on at

Like (0)

Report

I know this is an older thread, but I thought I would answer since there is so little information about Omnichannel reporting. The basic structure of a a conversation in Omnichannel is :

Conversation -> Session -> Session Participants with each being a 1 to many relationship.

In order to get to the information about if a conversation was missed, you have to do it at the session participant level. There is a field called "Left On Reason" in this entity and among the statuses are "AgentTimeout" and "AgentReject." This is where you need to report on those activities. To do this for a specific conversation, you can do an advanced search like below. For overall reporting, where you'd need to connect all the entities, you'd need to do this in PowerBI as Dynamics doesn't have the right relationships built in those entities to properly connect them.

1 people found this reply helpful.

Was this reply helpful? Yes No