Dynamics 365 Customer Service – New timeout rules logic for Representative Non-Response time and open state conversation

We are announcing new timeout rules logic for Representative Non-Response Time and open state conversations in Dynamics 365 Customer Service. This feature will reach general availability on November 3, 2025. How does this affect me? We are updating the logic for the Representative Non-Response Time event to encompass a more holistic approach. The following describes the new logic for the Representative Non-Response Time trigger event: On initial contact between the service representative and the customer, if the customer has sent a message and started the chat, the system will calculate the time that the customer has been waiting after the representative is actively on the conversation: Once Representative Notification accepted, auto-assign Notification timeout, or Force Assign via Supervisor occurs, then: Representative Non-Response Time = Current Time – Representative assignment time Once there is rapport (back and forth messages), the Representative Mid-conversation Logic will be used: Representative Non-Response Time = Current Time – Last customer message The Last customer message is determined by the duration the service representative has not responded to the customer’s most recent message. What action do I need to take? This message is for awareness, and no action is required. Message ID: MC1165529

The post Dynamics 365 Customer Service – New timeout rules logic for Representative Non-Response time and open state conversation appeared first on M365 Admin.