Help center Core configuration Case management Configure reusable case task scenarios Updated Friday, October 30, 2026 · Marcel Gravelle Scenarios apply a predefined list of tasks to a case. Use them for repeatable processes such as onboarding or escalation so important steps are not left to memory. Applies to: Supportbench Core. Location: Settings → Cases → Scenarios. Editing the scenario configuration requires Administer all scenarios. Before you begin Editing requires Administer all scenarios. A list that you can view may still be read-only.Identify the repeatable process, intended personal/team/global audience and who owns each task. A checklist should make the next action clear without copying a previous customer’s private details.Verify the saved configuration and then a controlled example in the consuming workflow. A successful settings save alone does not prove the operational result. Configure and verify Open Settings → Cases → Scenarios. Choose New Scenario or open the scenario you intend to maintain.Enter Name and Description; review Scope, Team, Division and Active. A new scenario starts Personal and Active with all Divisions and no tasks.In the task list, choose Add Task. Enter Subject and Instructions, choose the supported Owner/Team, Due value and its Minutes, Hours or Days unit, and review Approval and Active.Repeat Add Task for each required step. Drag task rows to reorder them into the intended operating sequence. Review copied tasks before saving.Choose Save Changes and reopen the scenario. Confirm the saved task order, ownership, timing and scope.Apply it to a controlled Case using the normal Case task workflow. Inspect every created task and its deadline/assignment. Editing the reusable scenario does not rewrite tasks already created on Cases. Settings reference ScenarioSettingWhat it controlsHow to chooseName / DescriptionName up to 250 and description up to 1,000 characters.Identify the process and when it should be used.Scope / Team / DivisionPersonal, Team or Global scope with the supported team and division selection.Share only with the teams that own this process.ActiveMakes the scenario available for normal selection.Activate after reviewing every task. Ordered tasksSettingWhat it controlsHow to chooseSubject / InstructionsTask subject up to 500 and body up to 4,000 characters.Describe a clear action and completion criteria.Due / UnitNonnegative interval in minutes, hours or days.Use a realistic relative deadline.Owner / TeamSelect a specific agent Owner or a Team as alternative assignments.Choose Team only when the task is not assigned to a specific Owner.Approval / ActiveWhether approval is required and the task is enabled.Use approvals only where the process calls for a decision.Duplicate / Delete / OrderMaintains the scenario’s task list.Review copied tasks and the final order before saving. Behavior to knowA new scenario is Personal, Active, uses all divisions and has no tasks. A new task starts Active with a zero-minute interval and approval off.A reusable scenario and tasks already applied to cases are separate records; inspect existing case tasks before assuming a template edit changed them.Due values are relative to scenario application, not a business-hours SLA. Approval is required before that task can be completed; it is not approval of the entire Case or of scenario application. Recommended use Use terminology that agents and customers already understand. Explain the intended meaning in the description.Keep the initial configuration small enough for people to choose consistently. Add options when they represent a real operational difference.Review existing references before renaming, changing scope, or deleting. Where supported, deactivate an obsolete option before considering permanent deletion. Worked example: prepare an equipment-account onboarding checklist Create an illustrative Equipment account onboarding scenario for the actual team responsible for the process. Choose its intended Scope, Team and Division. The following 1-, 3- and 5-day intervals are teaching examples, not service commitments or verified account defaults.Add Task with Subject Confirm account contacts and installation site. In Instructions, require verification of the primary Contact, installation site and any missing information. Choose the actual responsible Team with Owner unassigned, set Due to 1 with Days, and keep Active on.Add Verify controller setup. Choose either the specific technical Owner or the responsible Team, not both. Set the illustrative Due to 3 Days. Instructions should require recording the approved non-secret connection check and observed result; do not copy passwords or a real customer’s private checklist into the reusable scenario.Add Approve go-live handoff with the actual accountable Owner or Team and an illustrative Due of 5 Days. In Instructions, describe the evidence to review, such as verified setup results and the agreed support handover. Turn on Approval only when the process requires approval before this task can be completed.Order the three tasks, choose Save Changes and reopen the scenario. Apply it once to a controlled Case through the normal task workflow. Verify the three task subjects, Instructions, Owner or Team, due times and Approval state. Due intervals are relative to scenario application; they are not business-hours SLA targets.Confirm that the approved handoff task cannot be completed without its required approval. Approval is for that task; it does not approve the whole Case or block the initial application of the scenario. Arrange customer communication explicitly instead of assuming that creating tasks sends it.If an assignment or due time is wrong, correct the reusable scenario and test a new controlled application. Review tasks already created on existing Cases separately: changing the scenario does not rewrite those records. Do not reapply it to a live Case merely to try to update existing tasks. Define what the agent must verify, when the task is due, and whether completion needs approval. This demonstration leaves assignment empty; choose an accountable Owner or Team, or verify the intended assignment workflow, before operational use.Troubleshooting ProblemWhat to checkThe scenario is missing from normal useCheck Active, personal/team/global scope, the selected Team/Division and the current agent’s access.I cannot maintain the scenarioCheck Administer all scenarios and configuration editing availability.A task was not createdCheck that the task is Active and that the scenario was actually applied to the intended Case.Tasks appear in the wrong sequenceDrag the rows into order, save, reopen and test a new application; existing Case tasks are separate records.A due date or owner is unexpectedReview the task interval, unit and supported owner/team assignment, then inspect the actual created task.An existing Case checklist did not changeExpected. Scenario configuration and previously applied Case tasks are separate. Related configuration Cases → Configure case templates and chat shortcutsOrganization → Configure teams and SLA availabilityPlan and complete case work in Task CenterCreate repeatable onboarding or service cases from a source-case template Was this article helpful? Yes No Thank you for your feedback.