Help center Core configuration Knowledge base Maintain reusable article variables Updated Thursday, October 29, 2026 · Marc Staine Article variables store reusable wording, such as support hours or a shared contact statement. Confirm that the saved article resolves a variable correctly in both the agent and portal readers before depending on it; inserting a token alone does not establish that the customer will see its value. Applies to: Supportbench Core. Location: Settings → Knowledge Base → Variables. Access and available controls depend on your role and account capabilities. Before you begin Confirm you have the relevant knowledge-base administration permission.Identify the intended article audience and affected existing articles before changing shared configuration. Configure and verify Open Settings → Knowledge Base → Variables. Choose New Variable or open the intended existing variable.For a new variable, enter a stable Name and an administrative Description. The name is locked after saving; this editor has no Division, parent-hierarchy or article-audience controls.Enter the approved reusable wording in Content and review Active. Inspect the generated Token and Copy control; tokens use double underscores, such as __support_hours__, rather than Liquid braces.Use the settings toolbar Save Changes action. Resolve the displayed validation message, then reopen the variable and check its actual saved wording and availability.Use the article editor’s variable-insertion control in a controlled draft. Save the draft and inspect the output in the saved agent reader and a suitable portal test context. Do not treat insertion or Copy as proof of expansion.If the token remains literal, replace it with approved explicit wording before customer publication and record every article using the temporary copy. Later changes to the variable will not update that copied text. Recheck both readers after any change. Verify variable expansionCheck saved output before customer useThe current insertion and reading paths can leave the variable token visible instead of its value. If a saved article still shows a token such as __support_hours__, replace it with the approved explicit wording before publishing customer instructions. Record every article using that temporary copy: later variable changes will not update copied text. Settings reference Settings and actionsSettingWhat it controlsHow to chooseNameVariable identity, up to 50 characters; locked after save.Choose a stable descriptive name.Token / CopyGenerated token such as __support_hours__.Use the editor’s variable control, then check the saved result in both readers. Copying or inserting a token does not guarantee expansion.DescriptionAdministrative explanation, up to 250 characters.Explain where and why the variable is used.ContentReusable replacement content.Keep it accurate and suitable for every article using the variable.ActiveControls availability of the variable.Review usage before deactivation.DeleteRemoves the variable through the offered action.Check articles that depend on it before removal. Behavior to knowThe token uses double underscores, not curly braces. Verify replacement in the deployed article reader before using a variable in customer-facing content.The article reader’s replacement content supports HTML line breaks. Do not assume an inserted token has expanded until the intended reading surface displays its value. Recommended use Use clear, consistent names and keep the number of shared choices manageable.Review the effect on existing articles, templates and workflows before changing shared configuration. Worked example: maintain support-hours wording while checking the actual reader output An account team has approved support hours for its equipment service. Create support_hours with a description explaining which service the wording covers. Use the actual approved hours and time zone; do not present illustrative hours as a contractual commitment.Save Content and Active, then insert the variable through the editor in one controlled support article. The expected result is the approved hours in the reader, not the visible token __support_hours__.Save the draft and inspect the intended agent and portal reading surfaces. If the token remains literal, use approved explicit wording before publication and record that article as a manual-copy dependency. A token that looks correct in the editor is not enough.When the service hours change, update the variable and recheck actual rendered articles. Update any temporary copied wording separately, and confirm the wording still applies to each service audience.Before deactivating or deleting a variable, inspect dependent articles. Do not assume removing the variable also removes or safely replaces every occurrence of its token. Troubleshooting ProblemWhat to checkThe item is missing from a picker.Check that the variable is Active and that your role allows the relevant authoring action. Reopen the editor after saving the variable.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.The saved article shows __support_hours__ instead of its valueVerify the actual saved agent and portal reader. Use approved explicit wording before customer publication if expansion fails; track those manual copies for future updates.Name cannot be changedThe variable name is locked after save. Review dependent tokens and plan any replacement deliberately rather than assuming a renamed token updates every article. Related configuration Knowledge Base → Organize knowledge-base topics and accessKnowledge Base → Configure article templates and AI authoring guidanceKnowledge Base → Manage knowledge-base tags and audiencesKnowledge Base → Configure shared article styles and callouts Was this article helpful? Yes No Thank you for your feedback.