A help center on your own domain: white-label done right

A white-label help center is a knowledge base served on your own domain — help.yourbrand.com — with your branding, rendered server-side so it looks native rather than bolted on. The setup is a CNAME and a TLS certificate; the payoff is trust and higher deflection, because customers stay in your experience instead of bouncing to a vendor subdomain. Done on a multi-tenant platform, every workspace gets its own isolated, branded subdomain.

Why your own domain

A help center on help.yourbrand.com feels native and builds trust; one on a vendor subdomain feels like an afterthought. The difference shows up in deflection rates. A few reasons the domain itself matters:

• Trust. Customers recognize your domain and don't second-guess whether they've left your site.
• Consistency. The help center sits alongside your product and docs instead of in a visibly third-party space.
• SEO. Content on your own domain builds your domain's authority, not the vendor's.
• Continuity. If you ever change tools, your help URLs can stay put.

The DNS and trust details

It’s a CNAME and a certificate, rendered server-side with your brand color. Mechanically, the setup is short:

• CNAME. Point help.yourbrand.com at the platform's hostname so requests route to the right workspace.
• TLS certificate. Issued and renewed automatically for your subdomain, so the padlock is yours, not a shared cert.
• Server-side rendering. Pages render with your brand color and logo on the server, which keeps them fast and indexable without a flash of unstyled content.

The same domain-ownership discipline that makes email trustworthy applies here — if you've set up BYODKIM for outbound mail, adding a help-center CNAME is the same kind of DNS change.

Branding beyond the logo

White-label is more than swapping a logo. To actually feel native, the help center should carry:

• Your brand color applied consistently to headers, links, and buttons.
• Your logo and favicon, so the browser tab matches your site.
• Clean, readable typography rather than an obviously templated layout.
• No vendor attribution in the chrome — the experience reads as yours.

The goal is that a customer reading an article can't tell it's powered by a third party, and shouldn't have to care. The same brand color you set once should flow through the public help center, the authenticated portal, and the transactional emails that link back to them, so the whole loop reads as one product rather than a stitched-together set of tools.

White-label in a multi-tenant platform

Done in a multi-tenant platform, every workspace gets its own isolated, branded subdomain. That isolation is what makes white-label safe at scale: one tenant's branding, content, and data never bleed into another's. For agencies running support for many clients, this is the difference between one workspace per client and a credible per-client help center — the model described in the agencies solution. Isolation should fail closed and be enforced server-side, the same standard covered in RBAC for support teams.

It pays off in deflection

Good self-service answers the common questions before they become tickets — the mechanics are in measuring CSAT and deflection. A help center deflects when:

• Articles are easy to find — strong search and clear structure beat a long index.
• Content tracks the questions your inbox actually receives, which you can mine from canned replies and macros.
• The path from "couldn't find an answer" to "open a ticket" is short, so self-service never feels like a dead end.

Deflection isn't about hiding the contact button; it's about answering enough that fewer people need it. A practical way to keep the content honest is to review which articles get traffic and which questions still arrive as tickets despite a published answer — that gap usually means the article is hard to find or doesn't actually resolve the issue, not that the question is rare.

Help center and portal together

The public help center pairs naturally with an authenticated magic-link portal, where customers see their own ticket history without a password — covered in magic-link support portals. On the same branded subdomain, anonymous visitors read articles and signed-in customers track their conversations, all inside your domain. You can see both in the product on the customer portal section.

Common pitfalls

A few things that make a white-label help center feel less native than it should:

• Forgetting the certificate edge cases. Make sure the bare and www variants resolve and redirect cleanly.
• Mismatched branding. A help center on your domain but with default colors undercuts the whole effect.
• Stale content. A branded help center full of outdated articles deflects nothing and erodes trust.
• Hiding the human. Self-service should make contacting support easy when the article doesn't answer the question.

Frequently asked questions

What do I need to put a help center on my own domain?

A CNAME record pointing your chosen subdomain (like help.yourbrand.com) at the platform, plus a TLS certificate that's issued and renewed for you. The pages then render server-side with your brand color and logo.

Is a white-label help center different from a customer portal?

They're complementary. The help center is public, searchable knowledge-base content; the portal is an authenticated view where a signed-in customer sees their own tickets. Both can live on the same branded subdomain, often via a passwordless magic link.

How does white-label work for an agency with many clients?

On a multi-tenant platform, each client gets an isolated workspace with its own branded subdomain. One agency can run separate, native-looking help centers per client without their content or data mixing.

Does a help center actually reduce ticket volume?

It can, when the content matches the questions your inbox receives and search makes answers easy to find. The lever is relevance, not volume of articles — and you should still make opening a ticket easy for the cases self-service doesn't cover.