Wijzigingslogboeken
Blijf op de hoogte van de laatste wijzigingen en verbeteringen.
Blijf op de hoogte van de laatste wijzigingen en verbeteringen.

24. Jun 2026
Delen
Overview:
Until now teams had to manually watch for conversations that were about to breach or had already missed their SLA targets. With this release, SLAs become actionable. You can now automate workflows when conversation SLAs are due soon, overdue, or manually dismissed, helping teams proactively manage response times instead of reacting after issues occur. We've also added more control over manual SLA removal, giving admins the ability to decide who can dismiss SLAs and ensuring every action is auditable.
👀 What's New?
You can now build workflows that automatically run when a conversation's SLA becomes due soon, overdue, or is manually dismissed. Instead of relying on users or managers to monitor SLA timers, you can define exactly what should happen when these events occur. For example, you can: Notify a user when a conversation becomes overdue or Reassign contacts for escalation. To help prevent excessive notifications, we've also added an Avoid Repeated Triggers option. When enabled, the workflow will only run once per conversation within a 24-hour period, even if multiple messages from same contact cause additional SLA events.
We've also introduced better controls around manual SLA removal. For conversations where no response is required - such as "Thank you", "Got it", or "Not interested" messages, users can manually dismiss the SLA without replying. Admins can choose whether this action is available to all users or restricted to admins only.
How to Use
Building Conversations SLA Workflows


Configure Manual SLA Removal Permissions


