Skip to content
Help Center
Submit a request Sign in

Design and brand your customer portal: a complete preview, publishing and recovery guide

A useful B2B support portal helps a customer recognize the right product, find a verified answer and follow up on work with your support team. Branding makes that experience familiar; good page design makes the next action clear. This guide takes you from an operational brief through Core’s branding controls, design preview, AI-assisted changes and publication. It also explains which actions can affect visitors immediately, so a visual refresh does not accidentally become an unplanned portal launch.

At a glance

For: support operations leads, portal administrators and authorized designers. Applies to: Supportbench Core.

Start here: Settings → Self-Service → Customer portal → select the portal → Branding or Design

Start with customer tasks and an operational brief  ·  Prepare access and a recoverable starting point  ·  Understand what saves immediately and what stays in draft  ·  Set a recognizable brand without replacing the design  ·  Explore the design with sample customer journeys  ·  Make a focused change with Design with AI  ·  Use reference images and placed images deliberately  ·  Edit page code while preserving working customer actions  ·  Apply a theme or duplicate an existing portal deliberately  ·  Publish and verify the real customer experience  ·  Recover an unwanted change or a conflicting edit  ·  Worked example: refresh an equipment-support portal

Start with customer tasks and an operational brief

A portal is a customer-facing website, not the agent workspace. Its theme supplies the design; individual page templates determine how supported information and controls appear. A draft is an unpublished design source. Portal settings, such as colors and contact information, have a different save boundary from page drafts.

Before editing, write down who will use the portal, the product or service they need help with, and the three actions they should find quickly. For an equipment supplier, those actions might be “Find installation guidance,” “Ask about a fault,” and “Review my requests.” A customer with several contacts may need different case visibility from an individual user; configure that access separately and test it with the intended customer identity.

Decide before editingExample operational decision
Audience and productThis portal supports the industrial pump product; a separate portal serves the software service.
Primary tasksFind a troubleshooting article, submit a complete fault report, and find an existing request.
Language and wordingUse customer product names and explain technical terms; avoid internal queue names.
Brand assetsUse the approved logo, browser icon and color values supplied by the brand owner.
Content ownershipThe knowledge lead maintains article links; the support lead owns contact details and the launch checks.
Success checksA new customer can find the relevant guide, sign in, submit a request and return to it on a small screen.

These are planning recommendations. A theme does not automatically implement new product behavior, create missing articles, grant Company-wide case access or guarantee higher search rankings. Measure the tasks your customers can actually complete, then use feedback to improve confusing labels and paths.

Prepare access and a recoverable starting point

  1. Confirm that your role can edit Customer portal. If the editor is read-only or actions are unavailable, ask the portal administrator to check your configuration permissions and portal-content access.
  2. Open Settings → Self-Service → Customer portal, then select the exact portal. Record its name and customer address, especially when your account has several portals.
  3. Open the existing portal and record the pages and customer journeys that currently work. Capture the existing brand values and any custom source that the design owner needs to restore. Use sanitized test examples.
  4. Coordinate with other portal editors. Avoid replacing designs while another administrator has unpublished work. Identify who will review and publish the change.
  5. Prepare a public-reader test and an authorized customer test. A designer’s sample preview does not establish actual case or knowledge permissions.
  6. Read the action table below before choosing a save or replacement action. If you only need a new header label or color, use Branding; a complete theme replacement is unnecessary.

A favicon is the small browser-tab icon. HTML describes page structure, CSS controls appearance, JavaScript supplies browser behavior, and Liquid renders supported portal data and conditional content. You can use the branding controls without writing these languages; code-level changes need someone who understands the existing template.

Understand what saves immediately and what stays in draft

ActionWhat it doesOperational consequence
Save ChangesSaves page and design edits as drafts and saves portal settings. Custom JavaScript stays in the editor session until Publish.Settings take effect immediately. Keep the editor open if you still have session JavaScript to publish.
PublishSaves and publishes the reviewed design, including session JavaScript, and also saves portal settings. A confirmation explains that visitors see published changes immediately.Review all changed sources and settings first. You do not need to choose Save Changes beforehand.
Revert draftDiscards unpublished design drafts and session JavaScript, returning to the published design. The current settings form is also submitted.It is not a general undo for settings. Previously saved settings remain, and current unsaved settings can be saved by this action; review the form before confirming.
Apply themeReplaces existing page drafts. Theme settings, artwork, CSS, JavaScript and content without draft support update immediately.The live portal may change before page publication. Treat this as a planned replacement, not a harmless theme preview.
Duplicate pagesReplaces destination page drafts with source portal content, preferring source drafts; copies selected design and Chat settings. CSS and JavaScript update immediately.Review the source’s drafts and destination settings first. This is not a complete clone of every portal setting.
Design with AIA successful design change is saved to drafts and shown in the sample preview; custom JavaScript retains its separate publication boundary.Inspect the result and Review changes. Do not assume an extra Apply button is required for every successful AI turn.

Use the right recovery action

Changing a logo, applying a theme and editing a page can affect different saved values. Revert draft does not restore every prior setting or reverse all replacement side effects. Record the starting values and review the specific recovery steps later in this guide.

Set a recognizable brand without replacing the design

  1. Choose Branding in the selected portal. Use Upload logo and Upload favicon for the approved artwork. Verify the preview and the actual portal after saving.
  2. Enter the customer-facing Contact message, Contact phone and Contact email where relevant. Use a monitored support destination and describe real service availability; do not promise around-the-clock coverage unless your operation provides it.
  3. Set Primary, Secondary, Background, Text and Surface under Brand colors. Record the previous values. These are the current labels; custom and older themes can use the underlying color slots differently.
  4. Review Header links. Give each used slot a clear label and a verified customer-facing destination. Leave unnecessary slots empty. Follow the linked header procedure for exact field limits and removal steps.
  5. Choose Save Changes. Reopen the settings to confirm they persisted, then open the actual portal and check logo proportions, readability, contact details and links.
  6. Check a phone-width layout and both public and signed-in pages. If a setting is saved but not rendered, ask the design owner whether the active template uses it.

A useful color palette must make body text, links and controls readable. A brand color that works on a marketing banner may be unsuitable for small text. In the Premiere theme, the fifth color is Surface; do not assume it always controls header text. The theme can adjust some colors for contrast. The header links and brand colors procedure explains these mappings in detail.

Do not assume changing this portal’s logo or colors restyles every case email, Chat transcript or survey in your account. Those experiences have their own applicable templates and settings. Likewise, do not paste old generic variables such as a supposed universal logo token into every template: use the supported Liquid reference for the specific rendering context.

Explore the design with sample customer journeys

  1. Open Design. Select the relevant Page and Language. Start with the landing page, then include knowledge, search, request and sign-in pages used by your customers.
  2. Choose Desktop or Mobile to inspect the layout at the supported preview widths. Use Expand when you need a larger working preview.
  3. Open Preview options and choose Sample data: Signed out, Signed in, Populated lists or Empty lists. Empty states should explain the next useful action rather than leaving a blank page.
  4. Use Refresh to update the sample preview after a change. Check text wrapping, navigation, images, form labels and the space available for longer product names.
  5. Treat Interactive sample, when available, as a sample-behavior aid. The preview uses sample content and does not change real customer records.
  6. Record any broken control or confusing page before publishing. Later, repeat the key journey in the real portal with the intended audience.

Signed-in sample data demonstrates a layout variant; it is not a real Contact’s authorization test. A request form that looks complete in the preview may still depend on actual case-policy fields, portal access, customer roles or product settings. Keep appearance review and operational acceptance as separate checks.

Make a focused change with Design with AI

  1. In Design, select the Page and Language you want to inspect, then open Design with AI.
  2. Choose a Design scope: Decide together, Whole portal or Preview page only. Whole portal can involve shared sources, so use it deliberately.
  3. Enter a clear request in Describe your change. Explain the customer task, the desired presentation and what must continue working. If you want advice first, explicitly ask for suggestions without changes.
  4. Choose Send or use the displayed Ctrl/⌘ + Enter shortcut. Read the reply and any clarification. A successful edit is saved to drafts and previewed; you still need to review it.
  5. Choose Review changes. Inspect every affected page or shared source, not just the currently visible page. Check that navigation, form hooks, access conditions and translations remain appropriate.
  6. Use Undo if the last design change is unwanted. A successful AI turn is one undo step, and Undo writes the reversal to drafts. Recheck the preview.
  7. Continue with another small request or proceed to the publication checks. Keep the editor open while it holds session JavaScript or the conversation you need.

Example: a clear request for a B2B support homepage

“On this portal’s homepage, make the three customer tasks Find troubleshooting guidance, Ask for help and Review my requests easier to scan. Keep the existing destinations, sign-in rules and forms working. Use our current brand colors, keep the knowledge search prominent, and make the layout usable on mobile. First explain the changes you recommend; do not edit yet.”

The request defines an operational outcome without asking the designer to invent backend capabilities. When you approve a visual direction, ask for one bounded change and review its actual diff. An attractive preview does not prove a generated link, instruction or promise is accurate.

Under Chat options, New conversation starts a fresh design discussion. Replace manually edited translations in this proposal is a consequential choice: leave manual translations protected unless the language owner has agreed to replacement. Review every affected language before publication.

Use reference images and placed images deliberately

A design reference tells the AI what an arrangement or visual style should resemble. An image to place is an asset intended to appear in the portal. Choose the appropriate purpose instead of assuming that attaching a picture will publish it.

  1. Open Choose image in the design conversation. Choose Design references or Images to place under Use images as.
  2. Select an existing image or choose Upload image. Reference images accept PNG, JPEG or WebP up to 2 MB. Images to place allow up to 5 MB, including GIF and SVG.
  3. Describe how the image should be used: for example, use the reference’s spacing but retain your own logo, or place an approved equipment illustration beside the installation-guidance link.
  4. Review the selected image chips and remove unintended material before sending. Attached references are sent to your configured AI provider; use approved sanitized material without customer cases, credentials or private identifiers.
  5. Check the resulting crop, text contrast, dimensions and mobile behavior. Verify useful alternative text in the page source when the image conveys information. If upload fails, read the error and use Retry upload when offered after correcting the cause.

Avoid putting essential instructions only inside artwork. Customers should still understand the task when images fail to load or when they use assistive technology. A decorative product photograph should not push search and request actions below the useful part of a small screen.

Edit page code while preserving working customer actions

Use Edit code in Pages from the preview, or open Pages, when you need direct control over a supported source. Select the page or shared source in the list before editing. The editor shows the selected source and its draft state.

  1. Identify whether the change belongs to one page or a shared header, footer, stylesheet or script. A shared source can affect several pages.
  2. Copy the relevant existing source for your review record and make a small, targeted edit. Keep required form fields, names, IDs, actions and script hooks intact.
  3. Use the current Liquid objects, tags and filters for that page. Preserve output escaping, language behavior and existing visibility branches. A visual condition is not a substitute for server authorization.
  4. Return to Design and check the affected pages, sample scenarios, languages and widths. Check actual customer functions after publishing.
  5. Save page/design work as drafts with Save Changes when appropriate. Remember that portal settings save immediately and custom JavaScript stays in the session until Publish.

The Supportbench Liquid guide links to the supported objects and focused examples. Do not copy a generic web template that removes Supportbench controls and assume case submission, search or sign-in will continue working. Custom tracking or third-party scripts also require your organization’s privacy and security review; this guide does not recommend adding them as a default branding step.

Apply a theme or duplicate an existing portal deliberately

These are replacement operations. Choose them when you need a new starting design, not to try a single color. Resolve unsaved destination settings, design changes and session JavaScript first; the editor blocks replacement when those changes are still present.

  1. For a theme, open Branding, browse Portal theme and select one. Selection alone is not a saved setting. Choose Apply theme and read Apply portal theme carefully.
  2. Confirm only when you intend to replace the existing page drafts. Theme settings, artwork, CSS, JavaScript and content without draft support update immediately and may change the live portal before publishing pages.
  3. For reuse, choose the source under Duplicate pages from and use Duplicate pages. Confirm both the source and destination. Source drafts take precedence over its published page content.
  4. Review the duplicated destination: the backend copies selected branding, artwork and Chat settings as well as design content. It does not clone every portal setting, so separately inspect customer access, identity, contact information and other configuration.
  5. Open Design and Pages to review the resulting drafts. Inspect the live portal for immediate shared-style/script effects, then complete the full publication checks before publishing page drafts.

For two product portals, copying a design can preserve familiar navigation while the content and access remain product-specific. Check every copied product name, destination, Chat selection and language. A copied “Contact product A support” link is a real operational error in product B’s portal, even if its layout looks polished.

Publish and verify the real customer experience

  1. Open Review changes and inspect all unpublished sources. Confirm the correct portal, Page, Language and shared-source effects. Review any portal settings still in the form.
  2. Run the sample checks for desktop/mobile, signed-out/signed-in and populated/empty states. Resolve missing labels, broken layouts and incorrect destinations.
  3. Agree the publication window and test owner. Keep the previous settings and source review record available for recovery.
  4. Choose Publish, read the confirmation and confirm when ready. This also saves portal settings; a separate Save Changes step is unnecessary. Wait for the result before leaving or trying again.
  5. Use Open portal and test the actual customer address. First check public knowledge and sign-in behavior anonymously, then use an authorized test Contact to check the intended knowledge and case scope.
  6. Follow the operational journey: search for a known guide, open it, submit a permitted test request if appropriate, and find the request afterward. Check labels, required fields and confirmation behavior.
  7. Repeat critical paths on a small screen and in each supported language changed by the design. Confirm excluded content remains inaccessible. Record the tested portal, date, result and any correction.

A successful save message proves a narrower result than a complete customer journey. If a design save succeeds but a subsequent settings save fails, inspect the saved design and settings independently before repeating the operation. Do not assume the entire action rolled back, and do not blindly retry a timed-out publication.

Recover an unwanted change or a conflicting edit

SituationSpecific recovery
The last AI design change is wrongUse Undo, then inspect the resulting drafts and sample preview. Verify which change was reversed before continuing.
You want to discard all unpublished design workReview current settings first, then use Revert draft and its confirmation. It discards design drafts/session JavaScript but is not a settings rollback; current form settings can be submitted.
You need an earlier version of one pageUse Restore previous page version from Review changes when the relevant version is available. Inspect the restored draft and publish only after review.
Another edit changed the saved baselineRead the conflict result. Load current content to refresh the saved baseline while retaining the kept proposal for comparison. Compare both before choosing how to proceed.
Changes contains a kept proposalApply kept changes to drafts is a recovery action, with confirmation, that replaces the named current drafts with that proposal. It does not publish. Review the affected sources first.
A saved color, logo or contact value is wrongRestore the recorded setting and save it; Revert draft does not undo already-saved settings. Verify the actual portal.
A theme or duplicate action changed the live appearanceReview the replaced settings and shared sources with the design owner. Restore the intended values/source deliberately; do not promise that page Revert restores every copied value.
The editor reports a failure after you clicked Save or PublishKeep the editor open, record the visible error, and inspect current saved content before retrying. One part of the multi-step save may have succeeded.
Custom JavaScript seems missing after reopeningUnpublished JavaScript was session work. Check the last published source and retained review copy; Save Changes alone is not its publication step.
A customer cannot access content despite a good previewCheck portal, Division, customer role, knowledge and case visibility. Fix the actual access configuration with its owner; do not remove security conditions from the design.

If the problem persists, provide the portal name, affected customer-facing URL, action, time and visible error, along with sanitized before/after examples. Explain whether settings, page markup or custom JavaScript changed. This gives the support team a much more useful starting point than “the portal is broken.”

Worked example: refresh an equipment-support portal

A pump manufacturer’s customers can find the logo but not the troubleshooting content. Several contacts at the same customer organization use the portal to follow equipment issues. The support lead wants a clearer home page without changing their access.

  1. Record the current homepage, brand values, public knowledge entry point and signed-in request destination. Verify which requests the sample Contact is allowed to see.
  2. Use Branding to update the monitored contact address and a misleading navigation label. Save Changes and check these immediate settings in the actual portal.
  3. In Design, inspect the homepage on Mobile and with Empty lists. Ask Design with AI to propose a clearer three-task layout without changing destinations or permissions.
  4. After agreeing on the direction, request a bounded homepage edit. Review the resulting draft, all affected shared sources and each relevant language. Use approved equipment artwork only when it helps identify the product.
  5. Publish after review. Test a real question such as “Where is the installation checklist?”, then test sign-in and the existing request journey using the authorized Contact.
  6. Record issues found during the test and assign an owner. Review customer feedback after launch; improve wording or content where customers still hesitate.

The B2B value is continuity: customers recognize the product, find reusable guidance, and reach the appropriate ongoing support work. Branding, knowledge quality and customer visibility need to work together. A visual refresh alone cannot compensate for missing procedures or an incorrectly scoped customer account.

Was this article helpful?