Help center Core configuration Customers & support levels Configure customer support levels Updated Wednesday, October 28, 2026 · Marc Staine Support levels identify the support tier assigned to companies and contacts. A clear default and priority order make tier selection consistent and give routing or SLA workflows a dependable classification. Applies to: Supportbench Core. Location: Settings → Customers → Support levels. Editing requires Administer support levels on your Agent role. Before you begin Agree which contract or service entitlement each level represents. A support-level label does not by itself set response deadlines or route a Case.Review the current Default Level and the workflows that use support level before changing the baseline. Configure and verify Open Settings → Customers → Support levels. Choose New Support Level or open an existing tier.Enter Name and Description, including eligibility and the person responsible for maintaining assignments.Set Priority from 1 to 25 and Display color. Lower Priority values sort first; this order is not a Case priority or an SLA target.Choose Default Level only for the intended baseline used when a Company or Contact has no assigned level. Review Active.Choose Save Changes and reopen the level to verify it.Separately assign the appropriate level in the Company or Contact record and save that record. Verify any workflow or SLA rule that depends on the level with a controlled Case. Settings reference Details and availabilitySettingWhat it controlsHow to chooseNameThe support-tier label, up to 50 characters.Use a recognizable service tier such as Standard or Premium.DescriptionAdministrative guidance, up to 250 characters.Explain eligibility and how the tier is assigned.PriorityAn integer from 1 through 25; lower values sort first.Choose an order consistent with your team’s tier model.Display colorThe visual indicator used when displaying the option.Use a consistent palette and meaningful labels; color alone should not carry meaning.Default LevelUsed for companies or contacts without an assigned support level.Set the normal baseline; do not make an exceptional tier the default accidentally.ActiveMakes the level available for selection.Retain existing references when retiring an old tier. Recommended use Use stable contractual categories rather than a new level for every customer. Separate entitlement from the priority of one incident.Audit unassigned customer records before changing the default; those records rely on the baseline. Worked example Use Standard as the baseline if that matches the support agreement. Create Premium for customers with an explicitly agreed enhanced service.Describe who qualifies for Premium and how the operations team verifies entitlement.Assign Premium to a controlled Company through its customer record, then review a Case for that Company.Confirm the intended routing and deadlines through their own rules. Do not assume that naming the level Premium created those commitments. Troubleshooting ProblemWhat to checkNew Support Level is unavailableCheck Administer support levels.A customer still shows the old levelVerify and save the Company or Contact assignment separately from the level definition.A level is not selectableCheck Active and reload the customer editor.Deadlines did not changeThe label alone is not an SLA. Inspect the applicable service commitment and workflow conditions/actions.The wrong tier appears for an unassigned customerReview Default Level and whether a level is explicitly assigned to the customer. Related configuration Customers → Manage companies and customer organization detailsCustomers → Manage contacts and customer portal accessConfiguration → Configure workflows and automationManage companies and contacts with the full support relationship in viewManage SLA response and closure commitments across B2B support Was this article helpful? Yes No Thank you for your feedback.