How to Change Your Freshdesk Portal URL (Custom Domain)

First, know which "URL" you're changing

Freshdesk has two different things people call the portal URL, and they are not the same job. The first is your base Freshdesk URL — the company.freshdesk.com subdomain that Freshdesk assigns you. The second is a custom portal URL (also called a vanity URL), a domain you own, like support.acme.com, that you map onto Freshdesk so customers never see the freshdesk.com address at all.

This guide is about the second one, because that is what almost everyone means by "changing the portal URL" — putting your support portal on your own brand. If you literally want to rename the freshdesk.com subdomain, that is a separate flow with heavier consequences, and Freshworks documents the fallout in Customizing your helpdesk URL. We will fold the most important of those consequences into the "what breaks" section below, because a custom domain shares many of the same gotchas.

What you need before you start

A domain you control and access to its DNS. You need to be able to add a CNAME record at your DNS host — GoDaddy, Cloudflare, Namecheap, Route 53, or wherever your domain lives. If someone else manages DNS, loop them in first, because the record is the load-bearing step.

A supported plan. The custom portal URL is a paid-plan feature. Per Freshworks' documentation, it is available on the Growth, Pro, and Enterprise tiers (and on the legacy Blossom, Garden, Estate, and Forest plans) — but not on the Free plan. If you are on Free and want a branded portal, that is the upgrade you are buying.

Admin rights. You need to be logged in as an administrator to reach the Portals settings.

Step 1: Add the custom URL in Freshdesk

Everything starts inside Freshdesk. Per the official Use a custom portal URL and verify DNS guide, the path is:

1. Log in as an Admin and go to Admin → Portals.
2. Hover over the portal you want to change and click the Edit icon.
3. On the Portal Settings tab, find the Portal URL field.
4. Enter your custom support URL — for example, support.acme.com — and save.

If you run multiple portals (one per product or brand), note that each portal has its own URL field, so you set the custom domain per portal rather than once for the whole account.

Step 2: Point the CNAME record at Freshdesk

Once you save the custom URL, Freshdesk generates a CNAME record and its value for you. Copy both. Then, in your domain's control panel:

1. Open your DNS Manager (on GoDaddy, for example, this is Admin tools → DNS Manager → Add CNAME record).
2. Create a CNAME record where the host is your subdomain (support) and the value is the target Freshdesk gave you.
3. For TTL, Freshworks suggests a value between 30 minutes and 1 hour, or you can leave it blank to accept the default.
4. Save the record.

Do not skip the verification. Back in Freshdesk, DNS verification is a mandatory gate — per the documentation, "Without DNS verification, you cannot proceed further." DNS propagation can take anywhere from a few minutes to a few hours depending on your host and the TTL, so if verification fails on the first try, give it time and retry rather than assuming something is wrong.

Step 3: Wait for the SSL certificate

This is the step that surprises people, so plan for it. After your CNAME is verified, Freshworks automatically requests an SSL certificate for your custom domain — you do not have to buy or upload one. The catch is timing and access:

• The SSL verification may take up to 24 hours to activate.
• Until the certificate is procured, your portal on the custom URL is inaccessible. The old freshdesk.com URL keeps working, but the new branded one will not serve traffic until the certificate lands.

Because of that inaccessible window, the smart move is to complete steps 1–3 before you publish the new URL anywhere — before you update your website's help link, your email signatures, or your marketing. Get the green padlock first, then announce the address.

The gotchas that keep the domain "pending"

Most failed custom-domain setups die at DNS, not in Freshdesk. Three specific things account for the majority of stuck cases, all of them documented by Freshworks:

• Proxying on the CNAME. If your DNS provider automatically activates a proxy on the record, it can hold the custom domain in a pending state indefinitely. On Cloudflare this is the orange-cloud toggle — set it to DNS only (grey cloud) for the support subdomain.
• Cloudflare Zone Hold. If you use Cloudflare, go to Overview → Quick Actions → Zone Hold and uncheck "Also prevent subdomains," or the hold will block the subdomain Freshworks needs.
• CAA records. If your domain has CAA records restricting which certificate authorities may issue for it, add pki.goog and letsencrypt.org to the records for your subdomain, or the automatic SSL request will be refused.

If your domain sits in "pending" for more than a day, walk this list before opening a support ticket — it is almost always one of these three.

What breaks when the URL changes — and how to soften it

A custom portal URL is a real move, and moving a web address has consequences. Freshworks is candid about this for URL changes generally, and it is worth being clear-eyed about before you flip the switch:

• Agents get logged out. Anyone signed in will hit a "We couldn't find the URL" error and must log back in at the new address. Warn your team before, not after.
• Old inline images stop rendering. Images embedded in existing tickets can stop displaying, even though new tickets after the change are fine.
• Existing ticket-status links break. Any ticket-status URLs you have already sent in replies and email notifications will become invalid.
• Knowledge base links break. Links to solution articles and forum posts you have shared with customers will point at the old address.

And there is a reconfiguration checklist to run after the change: verify your email "Forwarded to" address still converts mail into tickets, reauthorize any custom mailbox so it does not disconnect, update webhook callback URLs in your automations, replace your feedback widget code on your site with the new URL, and reconfigure third-party integrations that were pointed at the old address.

On SEO specifically: if your old support portal was indexed by Google, treat this like any domain migration. The cleanest fix is a 301 redirect from the old portal path to the new one so link equity and existing search rankings follow the move. Freshdesk's hosted portal does not give you server-level redirect control the way your own web server would, so for a heavily indexed knowledge base, coordinate with whoever owns your DNS and web infrastructure, submit the new URL in Google Search Console, and update your sitemap and internal links to the new domain. This is the honest limit of the native feature: Freshdesk will get your portal onto a custom domain and secure it, but the redirect-and-reindex housekeeping that protects your SEO is on you.

Where an AI layer fits after the move

Changing your portal URL is infrastructure work — it does not change how many tickets land or how fast they get answered. Once the domain is settled, the real question is throughput: can your team keep up with the volume arriving at the shiny new address?

That is a different problem from DNS, and it is where an AI agent layer earns its place. Macha runs on top of the Freshdesk you already use as a native connector — it is not a replacement portal or a competing help desk, and it does not care what URL your customers see. You connect Macha to Freshdesk with your subdomain and API key, and it reads and writes the same tickets, drafting grounded replies, resolving repetitive questions, and looking up order or account status through a custom tool that turns a REST API into something the agent can call. If you are weighing whether to build that yourself or adopt a platform, the build-versus-buy tradeoff is worth reading first, and the practical mechanics live in how to automate Freshdesk with AI. (Macha connects to Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. Credits are consumed per AI action, not per resolution — the pricing page breaks that down.)

The division of labour is clean: Freshdesk owns the portal and its address, and an agent layer on top handles the answering. And because that timing is a separate lever entirely, it is worth understanding how your business hours shape when work actually gets done once the traffic is flowing.

FAQ

Where do I change the portal URL in Freshdesk? Log in as an Admin, go to Admin → Portals, hover over the portal and click the Edit icon, then open the Portal Settings tab and enter your custom address in the Portal URL field. Freshdesk then generates a CNAME record for you to add at your DNS host.

Do I need to buy an SSL certificate? No. After you verify the CNAME, Freshworks automatically requests and provisions the SSL certificate for your custom domain. It can take up to 24 hours to activate, and your custom URL is inaccessible until it does — so set it up before you publish the new address anywhere.

Why is my custom domain stuck on "pending"? The usual causes are DNS-side: a proxy enabled on the CNAME record (set Cloudflare to DNS-only), a Cloudflare Zone Hold with "Also prevent subdomains" checked, or CAA records that don't allow pki.goog and letsencrypt.org. Fix those and re-verify.

Will changing the URL break my existing ticket and knowledge base links? Yes — existing ticket-status links in past replies and notifications, shared solution-article and forum links, and inline images in old tickets can all break. Plan a 301 redirect from the old portal to the new one and update the links you control, then resubmit the new URL in Google Search Console.

Can I add AI to my Freshdesk portal without replacing it? Yes. Macha connects to Freshdesk as a native connector and runs on top of your existing portal — whatever URL it lives on — drafting and resolving tickets while Freshdesk stays the system of record. It doesn't replace your help desk or its custom domain.

Ready to put your team's throughput on the same upgrade curve as your portal? Start a free trial of Macha and connect it to your Freshdesk in minutes.