Plan access: Support Suite requires Scale or Enterprise, an active trial, or access explicitly enabled for your workspace.
A support workflow is evaluated from top to bottom.
Triggers
A trigger starts the workflow when the configured support event occurs. Choose the narrowest event that matches the use case.Conditions
Conditions decide whether the run should continue. Use them to check thread, channel, label, tier, or other available data.Waits
A wait pauses the run before later steps. Account for the fact that the thread can change while waiting.Actions
Actions update support data or perform the configured communication. Place customer-facing actions after all required conditions.Test a workflow with a controlled thread before publishing it. Use workflow runs to find the first condition or action that did not behave as expected.