The default URL for your Customer Hub will be a subdomain of the TeamSupport URL.
The company “Bits & Bytes” might have a default URL of
bitsandbytes.na1.teamsupport.com and a Wiki document might route to a URL of
While you are welcome to use this URL, you may also decide to mask this URL for branding purposes, or to provide a more seamless user experience for your customers. TeamSupport achieves this through using CNAME – which is a method to alias domain names.
Using CNAME “Bits & Bytes” might have a Landing Page URL of
bitsandbytessoftware.co and a Wiki document might route to a URL of
Steps to change the Customer Hub URL using CNAME
- You must first own the domain that you would like to use as your alias. Once you own the domain, you will need to establish a subdomain that will be used for your Customer Hub. Your domain registrar should have all of the tools and instructions that you need in order to get your subdomain setup.
- The next step will be to make your subdomain the alias for your Customer Hub. This is also achieved through the admin tools for your domain registrar. When configuring your CNAME, it will ask the URL to which your subdomain should point. You will put the “Landing Page URL” which can be found by going to Admin -> My Portal -> Customer Hub -> Basic Hub Settings tab -> “Customer Hub URL”. Your registrar should indicate that it may take several days for this mapping to be completed.
- While you are waiting for the CNAME mapping to complete, you can move on to adding the CNAME URL to your Customer Hub settings. This setting can be found by going to Admin -> My Portal -> Customer Hub -> Basic Hub Settings tab -> “CNAME Redirect URL”. You will need to put your subdomain URL in this field. If this step is not completed, your subdomain will not redirect properly.
- You will need to supply TeamSupport with the SSL certificate for the CName. This can be an export of IIS and must be in PFX format. Here is a link to help change to PFX format if necessary. Note that hosting an SSL certificate is limited to customers on our Enterprise plan. We strongly advise against using wildcard certificates because of the potential security risks.
Need more help with this?