Zendesk Branding for the Help Centre
Zendesk branding matters because a help centre that looks nothing like your product tells customers they've left your company. Some stop trusting it, and write in instead.
Zendesk branding basics, and where they live
Most branding sits in theme settings, which means no code and no developer.
That is ninety percent of the job, and it takes about an hour.
Domain, the part that matters most
Branding isn't only visual. A help centre on a Zendesk subdomain looks like a third party service, however good the theme.
Host mapping puts the help centre on your own domain, something like help.yourcompany.com, which is what customers expect and what your marketing site can link to without apology. It requires a DNS record and an SSL certificate, both of which Zendesk documents, and it is plan dependent in the sense that it applies per brand.
Do it early. Changing the domain later means redirects, re-indexing and every old link in every old email pointing somewhere odd.
Consistency beyond the help centre
Customers meet your brand in several Zendesk surfaces, and teams usually style one and forget the rest.
Email notifications carry a logo and a signature, configured per brand. Those emails are seen far more often than the help centre itself, because every ticket generates several.
The web widget has its own colour and text settings. A blue widget on a green site is a small thing that people notice.
Then there is voice, if you use it, where hold messages and greetings are brand assets nobody in marketing has ever heard.
Do one audit pass across all of them when you rebrand. There is no single place that updates everything, and the leftovers are always the ones customers see most.
Running several brands
Multibrand gives each brand its own help centre, its own theme, its own domain and its own support address, with one shared agent workspace behind it. It is the right structure for genuinely separate products or acquired companies.
The cost is maintenance, and it compounds. Every brand is a theme to update, a set of articles to write and a set of settings to keep aligned. Teams underestimate this by a lot, and two years in one brand is beautifully maintained while the other three are stale.
Two things that keep it manageable. Share a base theme across brands with only settings differing, so a fix lands everywhere rather than four times. And decide up front which content is genuinely brand-specific, because most policy articles are not, and duplicating them is how they drift out of agreement.
Write down which brand owns which support address as well. Multibrand accounts drift into a state where nobody is sure which inbox feeds which brand, and the symptom is a customer of one product receiving an email signed by another.
On theme mechanics generally, see the Guide themes guide.
What branding doesn't do
It's worth being blunt. A beautifully branded help centre with thin content deflects nothing. Branding buys credibility, and credibility only matters if the answer is there when someone trusts you enough to look.
So spend the hour on logo, favicon, colours and domain, then stop and go write articles. The teams that get this wrong spend six weeks on a theme and publish nine articles.
One last check before you call it done. Open the help centre on a phone, signed out, on mobile data. That's how a large share of your customers arrive, usually while irritated, and it's the view nobody reviews because everybody tests on a laptop with the office wifi and an admin session. Logo legible, search box reachable without scrolling, contact route obvious. If those three hold, your branding is finished.
Frequently asked questions
Where do you change the logo and favicon?
In the theme settings. Zendesk help center branding covers logo, Zendesk favicon, colours and fonts without touching code, and deeper Zendesk brand customization means editing the theme templates.
Where do I change the Zendesk branding logo?
In the theme settings for that brand. No code needed, and each brand carries its own logo.
Can I put the help centre on my own domain?
Yes, through host mapping, with a DNS record and an SSL certificate. Do it before you accumulate links, because changing it later is painful.
Do email notifications use the same branding?
They carry their own logo and signature settings per brand, configured separately from the help centre theme. It is the surface teams most often forget.
How many brands can I have?
It depends on your plan and the limits change, so check the current Zendesk docs. The practical limit is usually maintenance capacity rather than the licence.
Can I use a custom font?
Yes, with CSS in the theme. Weigh it against page speed, since a slow help centre loses more people than an off-brand typeface does.
Looks good, still duplicated
Branding earns trust. It does not stop the same customer writing in twice, and Ticket Merger does.
Start free trial14-day free trial. No credit card required.