> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firmhouse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Support template

> Customize the Customer Portal support message and contact links with support.liquid.

Open **Customer portal → Templates → Support** to edit `support.liquid`. Save a version, preview it, and publish when ready. Existing support URLs continue to work.

The Support page always renders `support.liquid`. Until you publish a Support template, it uses the default template. Saving or previewing a draft does not change the live page. Review the layout and contact details before publishing.

The template contains the message and contact cards as ordinary Liquid and HTML, like the Orders template. Edit their layout directly. Add localized messages through `support.message`, which defaults to empty. Email and phone default to the localized **Support email** and **Support phone number** in Customer portal settings, which remain editable after publication. The `support.email` and `support.phone` translations override those settings for their locale. Empty values hide their contact links. Resetting a published Support template uses the Firmhouse default, without a merchant-specific body or translations. Saved versions remain available to republish. Publishing **Firmhouse default** (version 0) also adopts this shared default directly.

Default contacts follow settings without copying their values into the template:

```liquid theme={null}
{% capture support_email %}{{ 'support.email' | t: default: '' }}{% endcapture %}
{% capture support_phone %}{{ 'support.phone' | t: default: '' }}{% endcapture %}
{% assign support_email = support_email | default: project.support_email %}
{% assign support_phone = support_phone | default: project.support_phone %}
```

Existing saved templates retain their content. To use these defaults in an older template, update its contact fallbacks and clear copied `support.email` and `support.phone` translation overrides, then preview before publishing. To hide a contact regardless of its setting, remove its link from the template or assign an empty value.

The message uses the existing `t` filter, which preserves permitted HTML and removes unsafe HTML, followed by `newline_to_br` to preserve line breaks:

```liquid theme={null}
{% capture support_message %}{{ 'support.message' | t: default: '' }}{% endcapture %}
{% if support_message != blank %}
  <div>{{ support_message | newline_to_br }}</div>
{% endif %}
```

Phone and email values are escaped in their text and `tel:` / `mailto:` links. The renderer supplies existing phone and email SVG assets as `support_icons.phone` and `support_icons.email`. Authors can also write static content directly in Liquid; template authors remain responsible for escaping dynamic values outside the translated content flow.

The **Show Support in navigation** setting controls the standard Support link before and after publication. Email, phone and visibility remain editable in Customer portal settings. Custom hardcoded navigation links and explicit `legacy_navbar` arguments remain controlled by your templates. Hiding a link does not restrict direct access.

The default layout places contact links before the message on mobile and beside it on larger screens. When no message is configured, the contact card is centered. It uses `{% legacy_navbar %}` for navigation, matching the other default portal pages. Replace this tag with `{% navbar %}` to use a custom Navigation template.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.