Overview
Domain whitelabelling lets you replace the default Receive module URL with your own branded subdomain. Instead of your users seeing a generic platform URL when they access a form, they see a URL that belongs to your organisation — keeping the experience consistent with your brand from first click to submission.
For example, rather than accessing forms via the default platform URL, your users can reach them through something like forms.yourorganisation.com.au. The same custom URL applies to the Receive module login and every published digital form in your tenant.
Whitelabelling is set up by the ChandlerCX team and requires a short configuration step on your end. The process involves your IT team updating a DNS record, followed by ChandlerCX completing the platform-side configuration.
Request required: Domain whitelabelling isn't self-service. You'll need to request it through the Chandler CX support team — either during your initial onboarding or at any point afterwards. Reach out to helpdesk.chandlercx.com/support to get started.
How it works
The setup uses a CNAME (Canonical Name) record — a standard DNS configuration that points your subdomain to the platform's Cloudflare address. Once both sides are configured, traffic to your subdomain is routed through Cloudflare and delivered by the CX Platform module.
Your IT team handles the DNS side. ChandlerCX handles the platform side. Neither step can be completed without the other, and ChandlerCX can't complete their step until your DNS record is in place.
What you need to provide
Before setup can begin, you'll need to decide on the subdomain you want to use for the Receive module. It needs to be within a domain your organisation controls — your IT team can help confirm what's available.
Example: A subdomain like forms.yourorganisation.com.au would replace the default Receive module URL for your tenant, and would appear in the browser address bar whenever a user accesses your forms or logs into the Receive module.
If you also want to whitelabel other CX Platform modules, you can include those in the same support request — each module requires its own subdomain.
Setup process
- Submit a request to Chandler CX — contact helpdesk.chandlercx.com/support with the subdomain(s) you'd like to use and the CX Platform module(s) you want to whitelabel.
- Update your DNS settings — ask your IT team to add a CNAME record pointing your subdomain to its Cloudflare address. The format is:
yoursubdomain.com.au→yoursubdomain.com.au.cdn.cloudflare.net - Confirm DNS is live — once your IT team has made the change, let the Chandler CX support team know the CNAME is in place. This is the trigger for the platform-side configuration to begin.
- Chandler CX completes the configuration — the team will point the new subdomain to your CX Platform module. You'll be notified once this is done.
- Test the new URL — once confirmed, access the module or a published form via your new subdomain to verify everything is working as expected.
Example: Requested subdomain: forms.yourorganisation.com.au
CNAME record added by IT team:forms.yourorganisation.com.au→forms.yourorganisation.com.au.cdn.cloudflare.net
Result: the Receive module login and all published digital forms will now appear at forms.yourorganisation.com.au. Users will see your branded URL in the address bar at every step.
DNS must be configured first: ChandlerCX cannot complete the platform-side configuration until your DNS CNAME record is in place and confirmed. Starting the ChandlerCX step before DNS is ready will cause the setup to fail. Make sure your IT team has made the change and you've verified it before notifying the support team to proceed.
Once whitelabelling is set up, the change is permanent and automatic — users accessing your forms or modules will always see your branded URL, with no ongoing maintenance required.