Skip to content
Help Center
Submit a request Sign in

Configure case forms and chat customer details with policies

Case policies control which fields appear on case forms, which inputs are required and how the form is arranged. Different policies can support creation, closure, agent viewing and customer portal work without forcing every audience into one layout.

Applies to: Supportbench Core. Location: Settings → Cases → Policy. Access and available controls depend on your role and account capabilities.

Before you begin

  • You need permission to edit this configuration. Ask an administrator if the page is available but its editing controls are not.
  • Review the current configuration and where it is used before making a change. Available choices depend on your account, enabled modules, division access and role.
  • Use a test record or a controlled test account for behavior checks. Do not change production routing or send customer messages just to try an example.

Configure and verify

  1. Open Settings → Cases → Policy.
  2. Find the item in the list and open it, or choose the page’s new-item action.
  3. Enter a clear name and description. Set the fields below, including any scope, hierarchy, visibility or availability controls.
  4. Save the item and resolve any validation message. Reopen it to confirm the saved values.
  5. Check the relevant selection list or form using a user with the intended access. Repeat for an excluded user or division when scope is restricted.

Settings reference

Summary and applicability

SettingWhat it controlsHow to choose
Name / DescriptionPolicy name up to 50 and description up to 250 characters.Describe the form and audience.
TypeCase Open, Closure, Case View, Portal Open or Portal View.Choose the exact form you intend to customize.
Division / IssueNarrows applicability; issue choices depend on the division.Test a matching and nonmatching case.
Customer roles / CommunitiesSupported audience and portal restrictions.Choose only the intended customer audience.
Order / ActiveOrder from 1–25 and whether the policy is available.Review overlapping policies before activation.

Fields and layout

SettingWhat it controlsHow to choose
Fields to ShowSupported standard and custom fields for the selected form.Include what users need to complete the task.
Required fieldsSupported fields that must be completed.Require only information the form’s audience can supply.
Summary fieldsFields included in the supported case summary presentation.Choose useful context rather than duplicating every field.
Field orderOrders the available fields.Group related inputs and put frequent ones first.

Type-specific options

SettingWhat it controlsHow to choose
Default activity / Priority / Link typeDefaults offered for the selected policy type.Choose sensible starting values and check the actual form.
Require activity type selectionRequires an activity type to be selected before saving a Case View activity.Use when the agent must deliberately classify the activity.
Time spent / Show time / BillableSupported time-entry options for Case Open and Case View.Match your time-recording process.
TimerSupported Case Open timer behavior.Explain automatic timing to agents.
Activity summaryCase View summary behavior.Keep the display useful for the team.
No closure modal / Article requiredClosure-specific behavior.Test closure with and without the required knowledge context.
Disable automatic time spentTurns off automatic time-spent behavior for the supported form. This is an inverse switch.Enable this switch when automatic timing should be disabled, then test the actual form.

Built-in fields by policy type

Required Fields is available for Case Open, Closure and Portal Open. Summary Fields is Case View only; Closure has no Field Order tab. Listed capabilities remain conditional on the enabled account features.

SettingWhat it controlsHow to choose
CustomerCase Open and Portal Open. Customer selection has a required switch without a separate visibility switch.Require customer identity where the form needs it.
Subject / Summary / Priority / Issue / TagsCase Open, Case View, Portal Open and Portal View. Controls the corresponding case title, summary, classification or tags.Show the information the audience can understand and supply.
NoteCase Open, Closure and Case View.Keep internal intake/closure context useful to the next agent.
AssetCase Open, Case View, Portal Open and Portal View when Assets is available.Show only when the supported item matters to the task.
Time spentClosure field; Case Open and Case View use their separate time options.Match the team’s time-recording process.
Due dateCase Open and Case View.Use when agents need a specific case deadline.
Completion due on / Expected time to completeCase Open and Case View, conditional on Projects.Distinguish a deadline from estimated effort.
Project / Project versionCase Open, Case View, Portal Open and Portal View, conditional on Projects.Use the project and version relevant to the case.
Outcome / DivisionClosure outcome and division selection; required behavior is offered where applicable.Require only information that can be known at closure.
CCPortal Open visibility only.Expose when customers should add recipients at intake.
Case custom fieldsAccount-specific fields whose applicability refreshes with division. Hiding a field clears its required flag.Recheck custom fields after changing scope or visibility.

Case View summary choices

SettingWhat it controlsHow to choose
Company Name / Contact Name / Secondary Contacts / WatchersCustomer identity and additional case participants.Include the relationships agents need before replying.
Support Level / SLA (When to respond) / Closure SLA (When to close)Service entitlement and response/closure deadlines.Keep response and closure commitments distinct.
Owner / Created On / Closed On / Time SpentOwnership and case timing context; Closed On appears when closed.Choose useful operational context.
Outcome / Visibility / Customer NotesClosure outcome when closed, audience visibility and company/contact alerts.Retain critical customer alerts and audience context.
Linked Cases / Linked Articles / Company ParentRelated work, knowledge and company hierarchy.Show when these relationships guide support decisions.
Company AM / TAM / CSM and Contact AM / TAM / CSMAccount, technical and customer success managers at the respective customer location.Use the correct company or contact relationship.
Contact Phone / Contact MobileContact communication details.Expose according to the team’s operational need.
Case / Company / Contact custom fieldsAuthorized custom-field choices for each entity in the summary.Select the correct location and arrange the summary deliberately.

Behavior to know

  • A new policy starts as active Case Open with order 1 and the permitted starting scope. Existing policies retain their saved values.
  • Available fields and options depend on type, enabled modules and custom-field configuration. Test each affected form separately.

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

  1. Create a Case Open policy for a defined division.
  2. Show the identity, issue, priority and custom fields needed for triage.
  3. Require only information available at intake, then arrange the fields.
  4. Save and test creation with matching and nonmatching scope.
  5. Repeat separately for Portal Open if customers need a different form.

Show Assets on a case

Enable Assets under Settings → Account → Feature Modules (Feature Modules configuration). In the applicable Case View policy, make the Asset row visible under Fields to Show. The Asset selector appears in Case Details in the configured field order. Set its Required Fields selection separately when agents must choose an asset; agents also need permission to edit the case to change it.

The initial choices include assets linked to the case's contact or company. Type in the selector to search the available asset catalog. If no assets are linked to that customer, the initial list can be empty. Selecting a customer license preserves its link and support level. Use the adjacent View asset link to open the asset and its customer relationships.

Case Opened, Case Closed and portal policies control their own forms. Changing the Case View policy does not automatically change those other policies.

Troubleshooting

ProblemWhat to check
The item is missing from a picker.Check Active, division access, parent hierarchy, enabled modules, and the user’s role. Reopen the consuming form after saving.
The form rejects a save.Read the displayed validation message. Check required values, text limits and permitted scope; do not change unrelated settings to bypass validation.
An existing record still shows an old value.A configuration change and a record change are different operations. Inspect the record and relevant references before assuming the save failed.
  • Account → Configure account policies
  • Configuration → Configure custom fields and dropdown choices
  • Self-Service → Configure a customer portal
  • Customers → Configure company and contact field policies

Configure the customer details agents see in Chat

A Chat policy is the account-wide layout for read-only Company and Contact information in Chat Console. Use it when agents need customer context, such as a license number, support level or business contact details, while writing a response. Each account has one Chat policy. It applies across divisions, issues and chat widgets; it does not route conversations or change case forms.

Before you start

You need the Manage Chat policy role permission. The built-in Administrator role receives it by default when this feature is provisioned; other roles must be granted it explicitly. Permission to edit case policies alone does not allow Chat policy changes. See Delegate Chat policy administration through agent roles. Agents need access to the conversation. Their existing Company and Contact field visibility still applies: selecting a field in Chat policy does not grant permission to read it. A custom field is an extra field your organization defines on a particular record type. Create a Company or Contact custom field and populate it on the relevant record before expecting a value here. An Asset is a separate linked record; linked Asset lists are not included in this policy.

Create the single Chat policy

  1. Open Settings → Cases → Policy, then select Chat policy. If you can manage only Chat policy, it opens directly; the Case policies tab requires its own permission.
  2. Leave the Show customer details in Chat Console toggle on if agents should see the configured details automatically when they open a conversation.
  3. Under Company fields, turn on the toggles for the standard and custom fields your team needs. Repeat under Contact fields. Use Tab to focus a toggle and Space to change it. The initial selections match the existing Chat detail fields; additional fields start hidden.
  4. Use each row’s Move up or Move down button, or drag the row, to arrange fields within its group. Standard and custom fields can be mixed. Moving a Company field does not move it into Contact fields. Hidden fields retain their place for later use.
  5. Select Create chat policy. After it is saved, the action becomes Save changes; there is no second policy to create for another division or widget.
  6. Open a conversation linked to a Company and Contact you can read. Check the displayed labels, values and order in the customer details area. Open another conversation to confirm the layout applies account-wide.

Worked example: put a customer license number near the top

Suppose Acme Manufacturing has a Company custom field named License number with the saved value ACME-2026-0042. Turn on Name, License number and Support level under Company fields. Move License number directly below Name. Under Contact fields, turn on Name, Email and Phone. Save the policy, then open Acme’s linked conversation. An authorized agent sees the company name, ACME-2026-0042 and the support level in that order, followed by the separate Contact group. The value comes from the Company record; it is not copied onto the conversation.

If your organization stores the license number on the Contact instead, choose that Contact custom field under Contact fields. A similarly named Company field is a different field. To correct the value, open the corresponding record and use its normal authorized editor; Chat policy changes the layout, not customer data.

Hide details without losing the layout

  1. Open the Chat policy tab.
  2. Turn off an individual field toggle to hide only that detail, or turn off Show customer details in Chat Console to hide the configured customer details.
  3. Select Save changes.
  4. Reopen a conversation and verify the result. The selections and ordering remain saved, and existing conversation and case history stays accessible.

Company and Contact remain separate collapsible groups. An unset displayed value appears as an em dash (—). Zero and false values remain meaningful values rather than disappearing. Empty selections do not introduce default fields. Accounts without a saved Chat policy keep the existing Chat details behavior.

Review who changed the Chat policy

The saved policy includes an Audit history section. It records who saved the policy, when it was saved, and the creation or update. Additional entries identify changes to the customer-details visibility, individual Company or Contact field visibility and field order. These entries describe the layout; they do not contain customer field values such as the license number itself.

  1. Open Settings → Cases → Policy → Chat policy using a role with Manage Chat policy.
  2. Expand Audit history below the field groups. Read the newest save and its associated change entries.
  3. Select Load more to inspect older changes. Field entries identify Company or Contact, the field identifier and name, and its old and new positions. Positions count all configured rows, including hidden rows; zero means the field was absent from that layout.
  4. Compare the entries with the current toggles and ordering. For example, moving License number from the third row to the second produces an order entry; hiding it produces a hidden entry. Reopen the linked chat to verify the agent-visible result for a representative agent.

A save and its audit entries are recorded together. A rejected conflict, denied save or rolled-back save does not create a successful-change entry. After an uncertain connection result, use Reload saved policy and review the history before retrying. If history cannot load, close and reopen it; that read failure does not discard your unsaved layout. Older changes made before this logging was introduced are not reconstructed. The same Settings changed events are available in the account Audit Log to users with its separate reporting permission.

Recover from missing fields or save problems

  • Field is not offered: confirm it is an active Company or Contact custom field in this account. Case, Asset and other record types are not part of this catalog.
  • Unavailable saved field: a retired field remains identified in the editor so the layout is not silently rewritten, but it is omitted from chat output. Review its definition and select an available replacement when needed.
  • Field selected but not shown to an agent: check that agent’s effective Customer Policy and record access. Do not broaden permissions merely to make the Chat layout match another agent’s screen.
  • Value is —: verify the conversation’s linked Company or Contact and the saved value on that exact record. Changing the policy does not fill missing data.
  • Another administrator changed the policy: the save is rejected and your unsaved changes remain. Note the changes you want to keep, select Reload saved policy, confirm discarding your local draft, then review the latest layout and reapply the intended changes.
  • Save result is uncertain after a connection failure: reload the saved policy to verify what was accepted before saving again. Do not assume the failed browser response means nothing was saved.
  • Configuration is unavailable: ask your role administrator to check Manage Chat policy, then confirm that the Chat feature and its matching account update are available. A renamed or custom role is not granted this permission merely because its name contains “admin”. Conversation messaging remains available.

Keep the visible list short enough to scan during a live conversation. Put time-sensitive support identifiers first and less frequently used details lower in each group. See Run effective B2B support conversations in Chat for the agent workflow.

Was this article helpful?