The Conversation SLA workflow trigger helps teams automate actions based on conversation response-time targets. It starts workflows when an SLA becomes Due Soon, Overdue, or is manually dismissed. Use this trigger to notify team members, escalate overdue conversations, and automate follow-up actions without manually monitoring SLA timers.
TABLE OF CONTENTS
- What Is the Conversation SLA Workflow Trigger?
- Key Benefits
- How to Set Up the Conversation SLA Trigger
- Available Trigger Filters
- Avoid Repeated Triggers
- Common Use Cases
- Related Articles
What Is the Conversation SLA Workflow Trigger?
The Conversation SLA trigger starts a workflow when a conversation reaches a selected SLA event. You can configure workflows to respond to three events:
| SLA Event | Description |
|---|---|
| Due Soon | Runs the workflow when a conversation's SLA approaches its deadline. |
| Overdue | Runs the workflow when a conversation's SLA exceeds its deadline. |
| SLA dismissed | Runs the workflow when a user manually dismisses an SLA. |
Key Benefits
Proactive SLA monitoring: Automatically respond when conversations approach or exceed SLA deadlines.
Automated escalation: Notify users or reassign contacts when SLA events occur.
Reduced manual monitoring: Run workflows based on SLA events instead of manually checking timers.
Repeated-trigger prevention: Limit workflow execution to once per conversation within a 24-hour period.
Dismissal-based automation: Start workflows when users manually dismiss SLAs.
How to Set Up the Conversation SLA Trigger
Go to Automation → Workflows.
Create a new workflow.
Add a trigger and select Conversation SLA.

Choose the SLA event:
Due Soon
Overdue
SLA dismissed

Optionally, add filters to narrow when the workflow runs.
Add the workflow actions you want to perform.
Publish the workflow.
The workflow runs when the selected SLA event occurs and the configured conditions are met.
Available Trigger Filters
You can add optional filters to control when the Conversation SLA workflow runs. Supported filter categories include:
Message channel
Tags
Owner
Custom fields
Use filters to limit workflow execution to conversations that meet your selected criteria.
Avoid Repeated Triggers
The Avoid Repeated Triggers option helps prevent excessive workflow execution when multiple messages generate additional SLA events. When enabled, the workflow runs only once per conversation within a 24-hour period, even if multiple messages from the same contact cause additional SLA events. This option is useful for workflows that send notifications or perform escalation actions.
Common Use Cases
Notify a User When an SLA Becomes Overdue
Use the Overdue event to start a workflow when a conversation exceeds its SLA deadline. Configure a notification action to alert the appropriate user.
Escalate Conversations Approaching Their SLA Deadline
Use the Due Soon event to initiate an escalation before the SLA becomes overdue. For example, configure an action to reassign the contact for escalation.
Automate Actions After Manual SLA Dismissal
Use the SLA dismissed event to start a workflow when an authorized user manually dismisses an SLA.
Related Articles
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article