This release improves several important areas related to email-based support, including inbound email reply matching, first-response SLA timing for reopened cases, permanent outbound email failure handling, and activity-level SLA response visibility.
Email remains one of the most important support channels for many teams, so accuracy is critical. Replies need to stay connected to the right case, SLA timing needs to reflect what actually happened, and failed outbound messages need to be visible and properly recorded.
This release includes improvements and fixes for:
Inbound email replies now stay on the correct case more reliably. First-response SLA timing behaves more accurately when a closed or resolved case is reopened by email. Permanent outbound email failures now stop retrying properly and create the correct audit trail.
Email support depends heavily on clean conversation history. When a customer replies to a case, that reply needs to attach to the right record. If replies are matched incorrectly, agents may lose context, customers may need to repeat themselves, and case history becomes harder to trust.
SLA timing is just as important. Managers and administrators rely on SLA data to understand team performance, response quality, and service commitments. When a case is reopened by inbound email, first-response timing needs to reflect the real workflow. Otherwise, reporting can become misleading.
Permanent outbound email failures are also important from an operational standpoint. If an email cannot be delivered, the system should not continue retrying indefinitely. It should stop, record what happened, and give teams a clear audit trail so they can investigate or follow up through another channel.
Activity-level SLA response time visibility adds another layer of detail. Instead of only reviewing response performance at a broader case level, teams can now see response timing tied to specific activities, which makes it easier to understand where delays happen and how work is progressing.
These improvements help teams maintain cleaner case histories, more accurate SLA reporting, and better visibility into email delivery issues.
The practical impact is stronger trust in email-based workflows. Agents can rely on case history being more accurate. Managers can rely on SLA data being cleaner. Administrators can better understand outbound email failures through the audit trail.
For support teams that handle a high volume of email, this is one of the most important operational improvements in the release.
Was this article helpful?
Thank you for your feedback!
You are related to multiple companies. Please select the company you wish to login as.