Well the first question is are you using unified routing? It works totally different that traditional routing is is KIND of how you are supposed to handle most routing these days but if you don't have channels, etc. set up it won't work.
If you’re using Omnichannel/Unified Routing, the clean approach is: set up an advanced “After Hours” queue, configure operating hours, and use overflow/after-hours handling so items arriving when the center is closed are routed appropriately. That's all OOTB.
Let me know if that's making sense - I might write up a blog post about unified routing but here's the learn documentation gon settin gup hours and applying them to a queue:
if you ARE NOT using unified routing, then you might need an interim approach (i.d recommending moving to unified routing if you are dealing with a real-life customer service scenario that consists of more than one-off cases handled during business hours. Do you have a call center? do they use D365 or something else, etc.)
if you do need something in the meantime use power automate:
Create an “After Hours” basic queue.
Trigger a Power Automate flow on case create.
Determine if “after hours"
If outside hours, call Dataverse API AddToQueue action to move/add the case to the “After Hours” queue. AddToQueue is an official Dataverse Web API action designed for moving records between queues.
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Share
Report
All responses (
Answers (
24
