Help center Core configuration Automation, fields & notifications Workflow field reference: actions, exclusions and safe operating choices Updated Wednesday, October 28, 2026 · Marc Staine A workflow exclusion protects a defined exception from a rule; an action changes a record or causes a supported side effect after the rule matches. This reference helps you choose those fields deliberately. In B2B support, an apparently small action can change who owns a customer commitment, which deadline applies or what a customer can read. Start with a clearly defined operating policy, then use the scope-and-event matrix below to check that the selected workflow can express it. At a glanceFor: support operations administrators and process owners configuring automated routing, updates and notifications. Applies to: Supportbench Core.Start here: Settings → Configuration → Workflows → select a workflow Before you choose an action · Read the matrix without overextending it · Understand what an exclusion protects · Review actions that change commitments or visibility · Exclusions · Actions · Retained read-only values · Custom fields · Worked test: a customer-specific escalation handoff · Troubleshoot the definition and its outcome · Keep the rule understandable as customers and processes change Before you choose an action You need permission to manage system workflows and write access to the Workflows configuration section. Read the main workflow guide for the full creation procedure. Review existing rules for the same scope and event before changing a live definition; the editor does not provide a general harmless simulation of all actions.Write the policy in plain language: when this event occurs, for these records, except these cases, take this action. Identify the process owner and an example that must not be affected.Open Settings → Configuration → Workflows. Select the intended workflow, or create an inactive draft for a new rule. New workflows start Active; turn it off while preparing an untested rule.Check Trigger first. Scope and event determine which fields are available. Changing either can clear incompatible choices after confirmation, so recheck Requirements, Conditionals, exclusions and Actions afterward.Select the smallest supported action set that implements the policy. Review Details, ordering and Stop When Hit with competing workflows before choosing Save changes.Reopen the saved definition and compare it with the intended policy. Validate real outcomes in an isolated test account or an explicitly approved controlled live test before wider activation. Read the matrix without overextending it Reference detailHow to use itFieldThe stored setting label. The editor may group settings under a friendlier action such as Update status, Set activity visibility or Reset the SLA. Account terminology and localization can change displayed record names.Purpose and inputWhether the setting expects a choice, multiple choices, text, a number or an on/off value. Select actual current account values; example labels are not default business policy.Available scope and eventsThe combinations supported by that setting. “All available events” means the supported events in the stated scope, not every event in the product.Repeated labelsRead the surrounding action group. For example, an Owner assignment and an Owner notification recipient answer different questions even though both mention the owner.Retained read-only valuesHistorical settings preserved for compatibility. Their presence in old data is not permission to recreate or modify them as current actions.Text and multi-selection settings may have storage-length limits. A limit on the serialized value is a character limit, not a guaranteed number of selected customers, recipients or tags. Keep definitions understandable; if saving fails, use the validation message and review the actual field instead of assuming that a fixed number of choices is always supported. Understand what an exclusion protects All configured Requirements must match. When Conditionals are supplied, at least one must match. A matching exclusion vetoes the workflow even when those positive criteria match. An exclusion is not another optional alternative, and a narrow rule name does not narrow its actual scope.Example: protect a demonstration customerA specialist routing rule is intended for named service customers. Use the supported Company criteria to define that group and Company Not (Any) to exclude the demonstration Company where offered. If a named Contact must also be excluded, use the corresponding Contact exclusion. Check the Company and Contact actually associated with the case: a person’s affiliation in a different system does not prove which relationship this event is evaluating.Validate one intended customer, another customer, the excluded customer and a case with missing customer relationships. If an excluded case still changes, inspect other applicable workflows and later events before blaming this exclusion. Another rule can independently make the same change. Review actions that change commitments or visibility Action choiceOperational decisionEvidence to inspectStatus and Status Close InIs closure justified, and should it happen without delay or after a stated number of minutes? A closure delay is not a substitute for customer agreement or a follow-up task.The saved case status, actual closure time and remaining work after the intended event.Reset SLADoes the service policy authorize restarting the applicable clocks? Which customer commitment should the team continue communicating?The resulting response/closure deadlines on the saved case and any applicable business-hours rules.Case Public and Activity PublicShould the case and this specific activity be available to the customer under the existing access rules? These are separate choices.A representative intended reader’s access and the content of the activity, including inserted variables.Save as an activity and message recipientsShould the notification be recorded on the case, who should receive it and what should that record expose?The saved activity, its audience and the actual message destination. A stored activity does not establish delivery.Assignment and external actionsWho accepts ownership after the change, and what evidence confirms any external side effect?The final owner/queue, team access and the integration destination when applicable.Review action combinations and subsequent events. Stop When Hit controls the current workflow evaluation pass; it does not prevent all later changes. Avoid a design that depends on repeatedly resetting a deadline or on one rule silently correcting another. Exclusions FieldPurpose and inputAvailable scope and eventsOwner NotThis workflow will not run when Owner Not matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Owners Not (Any)This workflow will not run when Owners Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Team Not (Any)This workflow will not run when Team Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Queue NotThis workflow will not run when Queue Not matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Queue Not (Any)This workflow will not run when Queue Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Last Queue NotThis workflow will not run when Last Queue Not matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.State NotThis workflow will not run when State Not matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.State Not (Any)This workflow will not run when State Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Company Not (Any)This workflow will not run when Company Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Contact Not (Any)This workflow will not run when Contact Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Category Not (Any)This workflow will not run when Category Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Asset Category Not (Any)This workflow will not run when Asset Category Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Severity NotThis workflow will not run when Severity Not matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Severity Not (Any)This workflow will not run when Severity Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Issue NotThis workflow will not run when Issue Not matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Issue Not (Any)This workflow will not run when Issue Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Outcome NotThis workflow will not run when Outcome Not matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Outcome Not (Any)This workflow will not run when Outcome Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Community Not (Any)This workflow will not run when Community Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Tags excludeThis workflow will not run when Tags exclude matches the selected value. Input: Tag or value list. Maximum 2000 characters. Spaces separate values.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Tags do not containThis workflow will not run when Tags do not contain matches the selected value. Input: Tag or value list. Maximum 2000 characters. Spaces separate values.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Activity Types Not (Any)This workflow will not run when Activity Types Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Activity Subject NotThis workflow will not run when Activity Subject Not matches the selected value. Input: Tag or value list. Maximum 4000 characters. Spaces are permitted inside a value.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Activity Subject Not (Any)This workflow will not run when Activity Subject Not (Any) matches the selected value. Input: Tag or value list. Maximum 4000 characters. Spaces separate values.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Both Activity Text NotThis workflow will not run when Both Activity Text Not matches the selected value. Input: Tag or value list. Maximum 4000 characters. Spaces are permitted inside a value.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Activity Text NotThis workflow will not run when Activity Text Not matches the selected value. Input: Tag or value list. Maximum 4000 characters. Spaces are permitted inside a value.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Activity Text Not (Any)This workflow will not run when Activity Text Not (Any) matches the selected value. Input: Tag or value list. Maximum 4000 characters. Spaces are permitted inside a value.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.NPS Score Not (Any)This workflow will not run when NPS Score Not (Any) matches the selected value. Input: Multiple selections. Choices: Detractor; Passive; Promoter.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Customer Roles Not (Any)This workflow will not run when Customer Roles Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Assets Not (Any)This workflow will not run when Assets Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Escalation Type Not (Any)This workflow will not run when Escalation Type Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Company Type NotThis workflow will not run when Company Type Not matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Company Type Not (Any)This workflow will not run when Company Type Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Company Status NotThis workflow will not run when Company Status Not matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Company Status Not (Any)This workflow will not run when Company Status Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Contact Type NotThis workflow will not run when Contact Type Not matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Contact Type Not (Any)This workflow will not run when Contact Type Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Contact Status NotThis workflow will not run when Contact Status Not matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Contact Status Not (Any)This workflow will not run when Contact Status Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Is Holiday NotThis workflow will not run when Is Holiday Not matches the selected value. Input: On/off.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Is Holiday Not (Any)This workflow will not run when Is Holiday Not (Any) matches the selected value. Input: On/off.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Support Level Not (Any)This workflow will not run when Support Level Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.To Not (Any)This workflow will not run when To Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Forum Not (Any)This workflow will not run when Forum Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Modified Last Not (Any)This workflow will not run when Modified Last Not (Any) matches the selected value. Input: One selection. Choices: 1 hour ago; 2 hours ago; 4 hours ago; 6 hours ago; 8 hours ago; 10 hours ago; 12 hours ago; 16 hours ago; 1 day ago; 2 days ago; 3 days ago; 4 days ago; 5 days ago; 6 days ago; 7 days ago; 8 days ago; 9 days ago; 10 days ago; 11 days ago; 12 days ago; 13 days ago; 14 days ago; 15 days ago; 16 days ago; 17 days ago; 18 days ago; 19 days ago; 20 days ago; 21 days ago; 22 days ago; 23 days ago; 24 days ago; 25 days ago; 26 days ago; 27 days ago; 28 days ago; 29 days ago; 30 days ago; 40 days ago; 50 days ago; 60 days ago; 70 days ago; 80 days ago; 90 days ago.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Created Last Not (Any)This workflow will not run when Created Last Not (Any) matches the selected value. Input: One selection. Choices: 1 hour ago; 2 hours ago; 4 hours ago; 6 hours ago; 8 hours ago; 10 hours ago; 12 hours ago; 16 hours ago; 1 day ago; 2 days ago; 3 days ago; 4 days ago; 5 days ago; 6 days ago; 7 days ago; 8 days ago; 9 days ago; 10 days ago; 11 days ago; 12 days ago; 13 days ago; 14 days ago; 15 days ago; 16 days ago; 17 days ago; 18 days ago; 19 days ago; 20 days ago; 21 days ago; 22 days ago; 23 days ago; 24 days ago; 25 days ago; 26 days ago; 27 days ago; 28 days ago; 29 days ago; 30 days ago; 40 days ago; 50 days ago; 60 days ago; 70 days ago; 80 days ago; 90 days ago.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Escalated Last Not (Any)This workflow will not run when Escalated Last Not (Any) matches the selected value. Input: One selection. Choices: 1 hour ago; 2 hours ago; 4 hours ago; 6 hours ago; 8 hours ago; 10 hours ago; 12 hours ago; 16 hours ago; 24 hours ago; 2 days ago; 3 days ago; 4 days ago; 5 days ago; 6 days ago; 7 days ago; 14 days ago; 21 days ago; 30 days ago; 40 days ago; 50 days ago; 60 days ago; 70 days ago; 80 days ago; 90 days ago.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.Last Activity Type ID Not (Any)This workflow will not run when Last Activity Type ID Not (Any) matches the selected value. Input: Multiple selections.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.From Domains NotThis workflow will not run when From Domains Not matches the selected value. Input: Tag or value list. Maximum 4000 characters. Spaces are permitted inside a value.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.From Emails NotThis workflow will not run when From Emails Not matches the selected value. Input: Tag or value list. Maximum 4000 characters. Spaces are permitted inside a value.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record.From Emails Not (Any)This workflow will not run when From Emails Not (Any) matches the selected value. Input: Tag or value list. Spaces are permitted inside a value.Case: all available events. Use the editor’s available choices and test a matching and nonmatching record. Actions FieldPurpose and inputAvailable scope and eventsIssueAfter this workflow matches, Supportbench applies Issue. Input: One selection.Case: Created, Updated, Reopened, Escalated, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.OutcomeAfter this workflow matches, Supportbench applies Outcome. Input: One selection.Case: Created, Updated, Reopened, Escalated, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.StatusChoose the status to apply after a match. Treat closure as an operational decision: verify the resolution, remaining work and customer communication before automating it. When a closing status is selected, Status Close In sets the closure timing; read its account-dependent finalization behavior below before assuming that a case stays open during the interval. Input: One selection.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events. Use the editor’s available choices and test a matching and nonmatching record.Status Close InThe number of minutes added to the closure time when the Status action closes a case. Use a nonnegative number; zero means no added interval. A positive value sets a future closure time, but deferred finalization requires the account to support that behavior: do not assume the case remains pending or open throughout the interval. This does not create a reminder or promise a customer update. Verify the saved case status and closure time through the actual event path before activating a closure rule. Input: Number.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.SeverityAfter this workflow matches, Supportbench applies Severity. Input: One selection.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.DivisionAfter this workflow matches, Supportbench applies Division. Input: One selection.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.OwnerAfter this workflow matches, Supportbench applies Owner. Input: One selection.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events. Use the editor’s available choices and test a matching and nonmatching record.QueueAfter this workflow matches, Supportbench applies Queue. Input: One selection.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events. Use the editor’s available choices and test a matching and nonmatching record.Activity TypeAfter this workflow matches, Supportbench applies Activity Type. Input: One selection.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.TagsAfter this workflow matches, Supportbench applies Tags. Input: Tag or value list. Maximum 2000 characters. Spaces separate values.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events. Use the editor’s available choices and test a matching and nonmatching record.Tags RemoveAfter this workflow matches, Supportbench applies Tags Remove. Input: Tag or value list. Maximum 2000 characters. Spaces separate values.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events. Use the editor’s available choices and test a matching and nonmatching record.Add watchersAdd the selected agents as case watchers. Agents already watching are left unchanged. This does not send a notification or start watcher-change workflows. Input: Multiple selections.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Requires the corresponding released account capability. Use the editor’s available choices and test a matching and nonmatching record.Remove watchersRemove only the selected agents from this case's watchers. Other watchers are kept. This does not start watcher-change workflows. Input: Multiple selections.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Requires the corresponding released account capability. Use the editor’s available choices and test a matching and nonmatching record.Change case subjectReplace the case subject with this exact text, up to 250 characters. Applied after templates and before workflow notifications. Remove this action to leave the subject unchanged. Input: Text. Maximum 250 characters.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Requires the corresponding released account capability. Use the editor’s available choices and test a matching and nonmatching record.OwnerSend this notification to the assigned owner. Input: On/off.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events. Use the editor’s available choices and test a matching and nonmatching record.Owner's managerAlso send this notification to the assigned owner's manager. Input: On/off.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events. Use the editor’s available choices and test a matching and nonmatching record.Account managerSend this notification to the account manager associated with the company or contact. Input: On/off.Company: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.CreatorSend this notification to the person who created the record. Input: On/off.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events; Company: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.Secondary contactsAlso notify secondary contacts associated with the case. Input: On/off.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.Additional email addressesSend this notification to the configured copied recipients. Input: Tag or value list. Maximum 2000 characters. Use valid email addresses.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events; Company: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.SubjectWrite the subject recipients will see. Input: Multiline text. Maximum 2000 characters.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events; Company: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.MessageCompose the notification message and insert supported merge fields. Input: Multiline text. Supports rich text and the offered merge fields.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events; Company: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.AgentsSend this notification to the selected Supportbench users. Input: Multiple selections.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events; Company: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.TeamsSend this notification to members of the selected teams. Input: Multiple selections.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events; Company: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.Case PublicAfter this workflow matches, Supportbench applies Case Public. Input: On/off.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.Activity PublicChoose customer visibility for the activity affected by this supported workflow path. This is separate from Case Public and from whether a notification is saved as an activity. Review actual activity content and audience, including templates and inserted variables, before enabling public output. Input: On/off.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.Slack channelsChoose the Slack channels that receive this notification. Input: Tag or value list. Maximum 250 characters. Spaces separate values.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events; Company: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.Slack messageWrite the Slack-specific message content. Input: Multiline text.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events; Company: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.Include standard contentInclude the standard Supportbench context in the Slack message. Input: On/off.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events. Use the editor’s available choices and test a matching and nonmatching record.Include priorityInclude the current priority in the Slack message. Input: Text. Maximum 50 characters.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events. Use the editor’s available choices and test a matching and nonmatching record.Send to the case contactSend the SMS notification to the case contact when a mobile number is available. Input: On/off.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.Additional mobile numbersAdd any additional mobile numbers that should receive the SMS. Input: Tag or value list. Maximum 2000 characters. Spaces separate values.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events; Company: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.SMS messageWrite the short message sent to SMS recipients. Input: Multiline text.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events; Company: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.TemplateAfter this workflow matches, Supportbench applies Template. Input: One selection.Case: Created, Updated, Reopened, Escalated, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.AssetAfter this workflow matches, Supportbench applies Asset. Input: One selection.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.Reset SLARestart the applicable SLA clocks for the matched case. This action is applied during the final workflow mutation, so verify the resulting deadlines on the saved case rather than inferring them from the action list alone. Reset only when your service policy authorizes a new clock; do not use it to conceal a missed commitment. Input: On/off.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.DevOps CreateAfter this workflow matches, Supportbench applies DevOps Create. Input: Multiline text.Case: Created, Updated, Reopened, Escalated, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.ScenarioAfter this workflow matches, Supportbench applies Scenario. Input: One selection.Case: Created, Updated, Scheduled. Use the editor’s available choices and test a matching and nonmatching record.CompanyAfter this workflow matches, Supportbench applies Company. Input: One selection.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.ContactAfter this workflow matches, Supportbench applies Contact. Input: One selection.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out. Use the editor’s available choices and test a matching and nonmatching record.Save as an activitySave the supported notification as an activity on the matched record. Saving a record of a notification is separate from choosing its visibility and from proving message delivery. Review Activity Public where available and verify the saved activity, its audience and the actual destination independently. Input: On/off.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events. Use the editor’s available choices and test a matching and nonmatching record.Sender / Case contact (Chat timed out)Send a copy to the sender associated with the triggering activity. For Chat timed out: Send the timeout confirmation to the primary contact on the case. A valid contact email address is required. Input: On/off.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.From / reply addressChoose the reply address used for the outgoing notification. Input: One selection.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events; Company: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.WebhookAfter this workflow matches, Supportbench applies Webhook. Input: Number.Case: Created, Updated, Reopened, Escalated, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Company: all available events; Contact: all available events; Asset: all available events. Use the editor’s available choices and test a matching and nonmatching record.Webhook EventAfter this workflow matches, Supportbench applies Webhook Event. Input: Text. Maximum 50 characters.Case: Created, Updated, Reopened, Escalated, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Company: all available events; Contact: all available events; Asset: all available events. Use the editor’s available choices and test a matching and nonmatching record.Published StateAfter this workflow matches, Supportbench applies Published State. Input: One selection. Choices: Internal; External.Article: all available events. Use the editor’s available choices and test a matching and nonmatching record.Notify record watchersAlso notify agents who already watch this record or supported related records, such as its company, contact or queue. Uses their watchlist notification preferences; does not add watchers. Selected notification recipients are notified separately. Input: On/off.Case: Created, Updated, Reopened, Escalated, Scheduled, De-escalated, Closed, Hashtag added, Before ownership transfer, Status changed, Manual, After ownership transfer, First assignment, Survey received, Case merged from, Case merged into, Watcher added, Watcher removed, Chat timed out; Article: all available events; Company: all available events; Contact: all available events. Use the editor’s available choices and test a matching and nonmatching record.Template EscalationAfter this workflow matches, Supportbench applies Template Escalation. Input: Multiline text.Case: Escalated, De-escalated. Use the editor’s available choices and test a matching and nonmatching record. Retained read-only values FieldPurpose and inputAvailable scope and eventsTemplateRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: One selection.Review retained values without treating them as working automation.Email FormRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: One selection.Review retained values without treating them as working automation.Email Form (Any)Retained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Multiple selections.Review retained values without treating them as working automation.Email Form Not (Any)Retained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Multiple selections.Review retained values without treating them as working automation.Owner CountRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Number.Review retained values without treating them as working automation.Owner Count (Any)Retained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Multiline text. Maximum 2000 characters.Review retained values without treating them as working automation.Article Thumbs Up Count (Any)Retained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Multiline text. Maximum 2000 characters.Review retained values without treating them as working automation.Article Thumbs Down CountRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Number.Review retained values without treating them as working automation.Article Thumbs Down Count (Any)Retained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Multiline text. Maximum 2000 characters.Review retained values without treating them as working automation.HashtagRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: One selection.Review retained values without treating them as working automation.Support LevelRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: One selection.Review retained values without treating them as working automation.SMS senderRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Text. Maximum 50 characters.Review retained values without treating them as working automation.Jira CreateRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Multiline text.Review retained values without treating them as working automation.Vendor CompanyRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Text. Maximum 30 characters.Review retained values without treating them as working automation.Target Resolution TimeRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Number.Review retained values without treating them as working automation.Target Resolution ClockRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Number.Review retained values without treating them as working automation.Escalated Not (Any)Retained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: On/off.Review retained values without treating them as working automation.Historical stop dateRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Date and time.Review retained values without treating them as working automation.Historical stop timeRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Time of day.Review retained values without treating them as working automation.ViewRetained historical or retired value. The editor preserves existing data but does not offer this as a new active setting. Input: Number.Review retained values without treating them as working automation. Custom fields Choose the field’s Case, Company or Contact location deliberately. Requirements must all match, Conditionals provide alternatives, and Exclusions veto a match. The editor supplies the appropriate single or multiple selection, checkbox, date, text or tag control. There is no universal comparison-operator menu. New custom-field actions are Case actions; existing historical values are preserved according to the editor’s supported behavior. Worked test: a customer-specific escalation handoff Suppose a manufacturer’s support team routes escalated equipment cases for contracted service customers to a specialist queue, while excluding its demonstration Company. The value is a consistent handoff with customer context; assigning the queue alone does not prove that a specialist accepted responsibility.Confirm the receiving queue, case access, coverage and the person responsible for the next customer update. Select the supported Case Escalated event for a rule intended to run on escalation.Use available Requirements to identify the intended service scope. Add the supported Company exclusion for the demonstration record. Avoid broad text matching when maintained customer or classification fields express the policy.Choose the supported queue assignment action. Add no unrelated closure, public-activity or SLA-reset action merely because it is available.Save and reopen the inactive definition. Prepare an approved positive case, an excluded demonstration case and a similar case outside the intended scope.Enable and trigger the rule only in the approved test context. Verify the final queue, case history, reader access and customer communication owner. The excluded and out-of-scope records should not receive this rule’s action.Check competing rules and repeat-event behavior. Record the observed case IDs and outcomes, then activate only the reviewed scope. Monitor initial operational results and pause the rule if exceptions are not handled correctly. Troubleshoot the definition and its outcome ProblemLikely cause and corrective stepA field is missing from the editorConfirm scope and event, then the availability column. A retained historical value is not necessarily editable in a new rule.The rule runs for too many recordsReview empty Requirements, overly broad alternatives, missing exclusions and actual customer associations. Deactivate the rule while investigating consequential unintended effects.A selected value will not saveCheck field validation, compatible selections and serialized length. Reopen the definition to distinguish an unsaved edit from a stored value.A status or deadline differs from the intended resultCheck the chosen status, closure delay in minutes, Reset SLA and later workflow events. Inspect the final saved case rather than only the editor action list.An internal note became customer-visibleInspect the relevant activity’s actual visibility, the workflow action and the template/variable content. Case visibility and activity visibility must be reviewed separately.A notification exists as an activity but was not receivedReview recipients and the actual sending/delivery evidence. Save as an activity is a recordkeeping option, not proof of delivery.Deactivation did not restore earlier valuesDeactivation affects future executions. Review already changed records and correct them deliberately; it does not undo delivered messages or external effects. Keep the rule understandable as customers and processes change Keep the workflow name, Description and operating instructions aligned with the real policy. Recheck customer selections when account relationships change; review recipients when staff leave; and retest after changes to scope, event, visibility, service policy or a connected system. Record a specific owner and a useful review trigger rather than assuming a saved rule remains correct indefinitely. Continue learning Design, test and maintain workflows for dependable B2B supportConfigure workflow settingsReference workflow triggers and conditionsManage escalation and de-escalationManage SLA response and closure commitmentsChoose and operate the appropriate webhook Was this article helpful? Yes No Thank you for your feedback.