Article content
In briefShow moreShow lessTimeout rules support more messaging channels; voice remains unsupported.
- Timeout rules support more messaging channels; voice remains unsupported.
- Idle conversations can move to a waiting state, while release back to a queue remains a planned capability.
- Field Service simplifies sharing board tabs and reading short bookings in dense schedules.
On 25 November, Microsoft described further improvements to timeout rules in Dynamics 365 Customer Service. The rules became generally available in April and have since expanded. Earlier in November, the Field Service team presented improvements already live in its schedule board. Both announcements address clearer handoffs in everyday service operations.
More conversations can receive automatic follow-up
Timeout rules now support channels including Teams, SMS, WhatsApp and chat. Voice remains unsupported. A rule can send a reminder, close an idle conversation or move it to a waiting state on asynchronous channels. Microsoft distinguishes the wait for an initial response from time since the customer's most recent message during an ongoing conversation.
In our assessment, these differences need to be reflected in service procedures. A customer waiting for a representative's reply is in a different situation from one who has stopped responding. Applying a common time limit without considering who needs to act next can produce inappropriate follow-up.
Sharing work schedules becomes easier
In Field Service, dispatchers can share a schedule-board tab directly with colleagues. Microsoft also describes clearer presentation of short bookings, satellite maps and entering an organisational unit's address without manually supplying coordinates. Individually these are small changes, but they address practical problems in daily dispatching.
They follow October's launch of one-way synchronisation of work-order bookings into Outlook and Teams. The calendar gives more employees visibility of the plan, while Field Service remains the place where the booking is changed. In our assessment, board sharing and calendar access should be accompanied by agreed procedures for holiday cover, urgent jobs and changes requiring customer notification.
Announced features are not delivered functionality
Releasing conversations back to a queue and allowing representatives to override timeout rules were still described as forthcoming in Microsoft's November announcement. Businesses assessing their applications therefore need to treat them as planned capabilities.
The news concerns more systematic handling of the small interruptions between tasks. We consider it more useful to monitor repeat contacts, incorrectly closed conversations and rescheduling than simply count automatic actions. A tidier queue or board represents an improvement when customers still receive appropriate follow-up and employees understand who is responsible. These measures also help managers distinguish reduced administration from work that has merely moved to another colleague.
Sources
Microsoft: expanded timeout rules in customer service (November 25, 2025)
Microsoft: Field Service scheduling upgrades (November 13, 2025)
Microsoft: calendar integration for Field Service (October 13, 2025)
Join the discussion
How do you determine whether a new solution actually helps customers? Share the measures you use.









