Help center Core configuration Case management Configure case states Updated Thursday, October 29, 2026 · Marc Staine Case states describe the stage of work and help an agent decide what should happen next. Configure a small, meaningful set with explicit entry and exit rules. Stop SLA timing affects service targets, while Secondary resolution records a resolution milestone without closing the Case. Treat these as deliberate operational choices, not cosmetic labels. Applies to: Supportbench Core. Location: Settings → Cases → States. Access and available controls depend on your role and account capabilities. Before you begin You need Administer case states permission and editing access to this Settings section. A read-only list does not grant permission to save or delete.Agree the meaning of each state, who may use it, when work should enter and leave it, and the applicable service commitment. A name alone does not configure routing, notifications or ownership.Review existing Cases, Views, workflows and reports that use the state before renaming, deactivating or deleting it. Configuration changes do not automatically move existing Cases to another state.Use controlled test Cases and intended/excluded roles to verify visibility and timing. Keep SLA and resolution-milestone decisions with the people responsible for the service agreement. Create a Case state and verify its saved settings Open Settings → Cases → States. Check the existing list first so you do not create another label for the same operational stage.Choose New State. Confirm the detail heading is Add Case State. To edit an existing choice, open its row and check Edit Case State instead.Enter Name and a useful Description. State when an agent should choose it and what must happen before the Case leaves it.Review Divisions when that selector is available. New forms can preselect your accessible profile Division, or the sole available Division. Do not assume a blank selection. Leave it blank for global scope only if your role permits global configuration.Choose Display order and an optional Display color. Keep Active state enabled when the state should be available for new selections. The configured label must carry meaning without relying only on color.Set Stop SLA timing only when the service policy permits that pause. Set Secondary resolution only for a real resolution milestone; leave it off for an ordinary waiting state. Some accounts do not show these optional controls.Choose Save Changes and read any validation result. The save applies configuration immediately; there is no draft/publication step on this form. Cancel leaves unsaved form edits unapplied.Reopen the state and confirm the fields. Then check the standard Case state picker with an intended agent and, where relevant, an excluded Division/role.Use the controlled transition tests below before relying on the state for SLA or resolution reporting. Saving the form is not a test of a real Case transition. Separate state configuration from changing a Case This Settings page defines the choices agents can use. Selecting a state on a particular Case is a separate operation in Case View. Editing a state’s name, visibility or active flag does not bulk-transition Cases already using it. A state label also does not assign a specialist or send an update unless a separately configured, tested workflow performs that action.Before changing a widely used state, identify its consumers: operational Views, workflow conditions, service rules and reporting interpretation. Explain any revised meaning to the team. A rename that hides a changed meaning can make older history difficult to interpret. Use the Case View procedure for the actual Case operation.Distinguish waiting, resolution and closure DecisionAppropriate interpretationWhat to verifyWaiting on CustomerA recommended example name for a stage where a specific requested customer response is needed. It is not a universal built-in default.Record the question and next update/checkpoint. Decide separately whether the service agreement permits an SLA pause.Stop SLA timingControls SLA handling for the selected state when the capability is available.Current targets can become blank while stopped and are recalculated on exit. Verify the real rules, calendars and resulting dates.Secondary resolutionRecords a resolution milestone and elapsed resolution measure.The Case can remain open. Check the resulting resolution fields and relevant reporting; do not equate the flag with closure.Close the CaseA separate supported Case operation with its own permissions and required fields.Follow the closure procedure. A descriptive state name or Secondary resolution alone is not proof of closure.A waiting state should not fabricate a resolutionIf the team still needs evidence or a customer reply before it knows the outcome, leave Secondary resolution off. Setting it for ordinary waiting can create a resolution timestamp even though the Case has not reached the milestone your reports intend to measure.Maintain or remove an existing state deliberately Open the state row to edit it. Review Edit Case State, change only the intended fields and choose Save Changes. Reopen the row to verify.To stop offering it for new selections, clear Active state when permitted and save. Confirm it disappears from the standard picker while existing Case values remain intact.If deletion is appropriate after reviewing references, use Delete on the list row. Read the irreversible-action confirmation and cancel if deactivation is the better choice.Default/protected states cannot be deleted. Delete removes a normal state from active availability without rewriting existing Case references; the page does not offer a restore action. Do not describe this as a way to move or close existing Cases.After any change, check affected Views, workflow selections and intended agents. Retain an operating record explaining the decision and follow-up checks.Test the two transitions and the intended audience Controlled checkWhat a correct result establishesNew/edit save and reopenThe state fields actually persisted; validation success alone does not test a Case.Intended versus excluded Division/roleThe choice is offered only through the intended scope. Ask the administrator about access rather than making it global just to force visibility.Active versus inactiveDeactivation affects new standard selections; existing Case state values are not silently replaced.Enter a Stop SLA timing stateThe Case’s SLA handling/targets reflect the configured stop behavior. Check the overall SLA target/trigger and closure dates; distinguish the separate first-response fields.Leave for a normal stateTargets are recalculated under the real SLA rules and calendar. Do not expect every earlier displayed date to return unchanged.Enter a Secondary resolution stateThe resolution timestamp and elapsed measure are recorded while closure remains a separate operation. Use a suitable test Case to avoid distorting real performance data.Default state restrictionsProtected Active/Divisions controls and deletion restrictions are respected. Do not attempt to work around them.Customer updateA separate outgoing activity is present if an update was intended. A state change alone is not evidence that the customer received a message. Settings reference Details and availabilitySettingWhat it controlsHow to chooseNameRequired agent-facing state label; up to 50 characters.Use a distinct work stage, not a promised SLA or an owner’s name.DescriptionOptional administrative explanation; up to 250 characters.Describe entry, next action and exit criteria so agents make the same decision.Display orderInteger from 0 to 25. Lower values appear first; ties sort by name. New states start at 0.Group meaningful stages without implying that the display position creates a transition workflow.Active stateNew states start active. Inactive states remain saved but are excluded from standard selection lists. Existing Cases are not rewritten.Deactivate an obsolete choice when you need to preserve its definition/history. A protected default state’s active value cannot be changed here.DivisionsWhere available, restricts selection to permitted active Divisions. Blank means global only for a role allowed to save globally.Review preselection. Scoped administrators must choose at least one permitted Division. Protected default states preserve their existing scope.Display colorOptional visual indicator; new states start without a color.Use a consistent palette, with a clear text label for accessibility and unambiguous interpretation.Stop SLA timingWhere available, entering the state marks the Case SLA stopped and clears the current overall SLA target/trigger and closure target fields. This branch does not clear the separate first-response SLA fields. Leaving for a non-stop state recalculates the applicable SLA under the account’s rules. New states default off.Use only where the agreed service commitment permits the pause. It does not pause every timer, task or customer communication. Test entry and exit.Secondary resolutionWhere available, entering the flagged state records the Case resolution timestamp and elapsed resolution minutes. This flag does not itself close the Case. New states default off.Reserve it for a genuine resolution milestone. Do not use it merely to mark waiting, assignment or a customer update. Behavior to knowNew states start with Active state on, Display order 0, blank color, Stop SLA timing off and Secondary resolution off. Division selection follows the accessible profile/single-choice rules described above.Some accounts hide optional Division, SLA-stop or secondary-resolution controls. Use the visible supported controls and ask the administrator about account availability.A protected default state preserves its Active and Division values; the disabled controls are intentional.Save Changes applies the configuration immediately. Existing Case transitions, notification delivery and reporting outcomes must be verified separately. Recommended use Use a few states that correspond to real operational decisions. A new label is useful when it changes what the team should do next, not merely to make the list longer.Write entry and exit rules and distinguish state from ownership, priority and escalation. Maintain those separate controls through their supported workflows.Review service-timing and resolution flags with the people responsible for customer commitments and measurement. Do not change flags only to improve a reported number.Preserve understandable history. Prefer deactivation to deletion when a retired choice still needs to be interpreted, and check all consumers before either action. Worked example: define Waiting on Customer without losing ownership Agree the entry rule: the agent has sent a specific question or request that is necessary to continue. Record who owns the next customer update and when the team will check again.Create or edit Waiting on Customer, describe that rule and select the intended Division scope. Keep Secondary resolution off because asking a question does not establish a resolution.Decide whether the service agreement permits stopping SLA timing while waiting. If it does, set Stop SLA timing; otherwise leave it off and manage the continuing commitment.Save Changes, then use a controlled Case to enter the state after recording the test request. Verify the expected target behavior and that a state change did not itself send a message.When the test customer reply arrives and work resumes, change to the agreed normal working state. Verify SLA recalculation, next action and ownership. Do not assume the reply automatically performs this transition unless your separately tested workflow does it.Review the Case history and relevant reports. The waiting period should not be mistaken for a secondary-resolution milestone. Troubleshooting ProblemWhat to checkNew State or Save Changes is unavailableCheck Administer case states permission and editing availability for the section. Read-only visibility is insufficient.A blank Divisions selection is rejectedYour role may require at least one permitted Division. Global scope is not available to every administrator.Active state or Divisions is disabledA protected default state preserves those values. This is not a reason to create a misleading duplicate.The state is absent from a Case pickerCheck Active state, Division scope and the consuming Case context. Reopen the form after configuration changes.SLA target dates disappearedIf the Case entered a Stop SLA timing state, current targets can be cleared. Verify the intended policy and test recalculation when leaving it.A Case has resolution data but is still openSecondary resolution records a milestone; it does not itself close the Case. Check whether that flag matches your reporting meaning.Deactivation did not change older CasesExpected. Availability and actual Case state changes are separate operations.Delete is unavailable or you need to restore a deleted stateDefault states cannot be deleted, and this page has no restore operation. Review the intended lifecycle with the administrator.A customer received no update after a state changeCheck the actual outgoing activity or configured notification workflow. The state name alone does not send a message. Related configuration Configuration → Configure workflows and automationCases → Configure case forms and chat customer details with policiesCases → Configure data views, filters and columnsChange and work a Case in its workspaceUnderstand response and closure SLA commitmentsDesign and test workflow conditions and actions Was this article helpful? Yes No Thank you for your feedback.