How to Set Up & Customize the Freshdesk Customer Portal

The three layers of portal customization

Before touching anything, it helps to know that Freshdesk stacks customization in three distinct layers, and you rarely need all three. The basic appearance layer handles brand color, logo, fonts, and portal name with no code at all — this is what most teams actually need. The theme layer lets you clone the default design, swap in a different look wholesale, or import one someone else built. And the advanced layout layer opens a code editor for custom CSS, JavaScript, and page-level structural changes when the first two aren't enough.

Each layer sits deeper than the last, and each carries different plan requirements. Start at the top and only descend when a genuine need pulls you down — a surprising number of "we need custom CSS" requests turn out to be solvable with the no-code color picker.

Step 1: Brand the portal with the no-code appearance editor

This is where the majority of the visible impact comes from, and it requires no developer. Per Freshworks' Customizing your customer portal documentation, the default Freshdesk portal ships with the Marina theme, and you tune its look under the portal editor.

1. Go to Admin → Portals, hover over the portal you want to change, and click the Edit icon.
2. Open the Customize step (or the Appearance tab). You'll see brand controls on the left and a live preview on the right.
3. Set your logo, portal name, and primary brand color — the primary color propagates to buttons, links, and accents across the portal.
4. Adjust the finer color slots if you need them: body elements, header and footer, cards, tabs, and form elements can each be styled independently.
5. Pick your heading and body fonts, then preview across desktop, tablet, and mobile before you publish.

The before/after on our own demo portal was stark: swapping the stock Freshworks blue for a single brand color and dropping in a logo took under five minutes and moved the portal from "clearly a Freshdesk tenant" to "looks like it belongs to us." For most teams, this step alone is the whole job.

Step 2: Change the theme or import a new one

If color and logo tweaks aren't enough — say you want a materially different layout for the home page or knowledge base — you move up to themes. The portal's Appearance tab lists your current theme (Marina by default), an Available themes gallery, and options to clone or import.

• Clone & edit the current theme when you want to keep Marina's structure but make deeper, code-level changes safely on a copy rather than the live design.
• Import a theme to apply one you've built or acquired. Freshworks documents importing themes as .zip files, and there's a small ecosystem of third-party theme shops (for example, Breezythemes) that sell ready-made Freshdesk themes if you'd rather not build from scratch.
• Download any theme (via the three-dot menu) to get it as a .zip — useful for version-controlling your portal design or moving it between accounts.

Themes are the right tool when the change is structural and reusable. If you just want your colors on the existing layout, stay in Step 1.

Step 3: Point the portal at your own domain

A branded portal on a yourcompany.freshdesk.com URL still leaks the vendor's name in the address bar. A custom domain — support.yourcompany.com — closes that gap. Per Freshworks' custom portal URL and DNS guide, the flow is:

1. Go to Admin → Portals, hover over the portal, click Edit, and open the Portal Settings tab.
2. Under Portal URL, enter your custom support URL (e.g. support.acme.com).
3. Freshdesk generates a CNAME record. Copy the record and its value.
4. In your DNS manager (GoDaddy, Cloudflare, Route 53, etc.), add the CNAME record pointing your subdomain at Freshdesk. Some newer setups also require a TXT record for verification.
5. Save and wait for DNS to propagate, then for Freshworks to procure the SSL certificate.

Two honest gotchas here. First, the portal is inaccessible on the custom URL until the SSL certificate is issued, which can take up to 24 hours — don't cut this over in the middle of a busy support day. Second, if your DNS provider proxies the CNAME (Cloudflare's orange cloud is the classic culprit), the domain can hang in a pending state; disable proxying, and if you use CAA records, make sure they include pki.goog and letsencrypt.org so the certificate can actually be issued. Custom URLs are available from the Growth plan onward (not on Sprout/Free).

Step 4: Advanced CSS and layout (when you truly need it)

When basic appearance and themes still can't express your design, Freshdesk's advanced portal customization opens a developer-friendly code editor for custom CSS and JavaScript. Per the Customize Portal Layout and Pages documentation, this layer lets you restructure the header, footer, and page layout across roughly 17 customizable portal pages — the Home page, Solutions/knowledge-base sections, ticket forms, and more.

The important caveat: advanced customization with custom CSS and JavaScript is gated to the Pro and Enterprise plans. On Free and Growth, the code editor is off the table, so if editing raw CSS is a hard requirement, budget for the higher tier. This is also the layer to approach with the most care — hand-written CSS and JS on top of Freshworks' markup can break when the platform updates its templates, so keep changes in a cloned theme and version-control your .zip exports.

What Freshdesk's portal customization can and can't do

Here's the honest map of the layers, plan gating, and effort:

The native tooling is genuinely capable across all four. But notice what customizing the portal doesn't touch: it changes how support looks, not how fast or how well it answers. A gorgeous, on-brand portal with a slow queue behind it is lipstick on a wait time. The portal can present a knowledge base beautifully, but it can't read a customer's typed question, understand intent, and surface (or write) the right answer — the customer still has to search, guess the right article, or give up and file a ticket that a human then works from scratch.

Where an AI layer picks up

This is the seam where an AI agent layer fits — and it's worth thinking through the build-versus-buy tradeoff before reaching for one. The broader category of AI agents for customer service exists to do the reasoning your portal template can't: understanding a question in plain language and returning a grounded answer instead of a list of blue links.

Macha is one such layer, and to be clear about the boundary: it runs on top of the Freshdesk you already use as a native connector — it does not replace your help desk, your portal, or its themes. You connect Macha to Freshdesk with your subdomain and API key, and it works the same tickets and knowledge base your portal already exposes: answering portal questions from your solution articles, drafting or posting grounded first replies so tickets resolve faster, and looking up order or account status through a custom tool that turns a REST API into something the agent can call. If you want the full picture of automating the workflow behind the portal, we cover it in how to automate Freshdesk with AI, and the SLA policies that govern speed sit right alongside it.

The clean division of labour: use Freshdesk's portal customization to own the look and the front door, and layer an agent on top for the part the template can't do — actually answering. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. And credits are consumed per AI action, not per resolution — the pricing page breaks that down.)

FAQ

Where do I customize the Freshdesk customer portal? Go to Admin → Portals, hover over your portal, and click the Edit icon. The Customize/Appearance tab holds logo, color, and font controls; the Portal Settings tab holds the custom URL; and the theme gallery lets you clone or import a whole design.

What is the default Freshdesk portal theme? The default theme is Marina. You can keep it and just change colors and your logo, clone it to make deeper edits safely, or import an entirely different theme as a .zip file.

Can I use my own domain for the Freshdesk portal? Yes. Under Admin → Portals → Edit → Portal Settings → Portal URL, enter a custom URL like support.acme.com, then add the generated CNAME (and, in some setups, a TXT record) in your DNS manager. Freshworks auto-procures the SSL certificate, which can take up to 24 hours — the custom URL is inaccessible until it's issued. Custom URLs require the Growth plan or above.

Which plans allow custom CSS on the Freshdesk portal? Advanced portal customization with custom CSS and JavaScript is gated to the Pro and Enterprise plans. Basic appearance changes (logo, colors, fonts) and theme cloning are available more broadly, so confirm the exact behaviour against your own plan.

Can I add AI to the portal without replacing Freshdesk? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and runs on top of your existing portal and knowledge base — it doesn't replace them. It answers portal questions from your solution articles and drafts grounded replies, while Freshdesk stays the system of record for your content and design.

Ready to put a fast, accurate answer behind that freshly branded front door? Start a free trial of Macha and connect it to your Freshdesk in minutes.