It sounds like you’ve been quite thorough in testing Dynamics 365 Customer Service, and I can understand how crucial it is to get the call handling flow right during your POC phase. Let’s address some of your concerns:
Queue Overflow - Average Wait Time Trigger:
You’re correct that the average wait time calculation relies on a certain volume of calls to be accurate. In a trial environment, especially with lower call volumes, this condition might not work as intended. As a workaround, you could try setting up more predictable overflow triggers like time-based rules or using manual triggers during testing.
Queue Overflow - Work Item Limit:
If the first call is still stuck on hold, it might indicate that the overflow settings aren’t prioritizing existing calls. Check if your overflow rule is applied only to new calls entering the queue. Additionally, ensuring proper routing rules and escalation policies for calls already in the queue might help.
Omnichannel Configuration Adjustments:
Changing the agent status to inactive after missed notifications or rejects is a good step, but this alone may not redirect the stuck call. Ensure that you’ve configured escalation paths for calls left in the queue when no agents are available. This could involve routing these calls to another queue or directly to the fallback number.
Additional Suggestions:
I hope this helps! Keep us updated, and good luck with your POC. OneBloodRewards
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156