Overview

Platform domains are the primary web addresses your organisation's members use to reach and sign in to CX Platform. They're the front door your team uses to get into the platform, and they also cover access to any associated ChandlerCX connected platforms your organisation is set up with.

CX Platform supports full white-labelling, which means these access domains run under your own organisation's domain and branding. Signing in feels like part of your own environment rather than a generic third-party login, so your team gets a consistent, recognisable way in.

This matters because your platform domains are where your members authenticate, so a branded, trusted address helps everyone know they're in the right place. It also keeps access to CX Platform and your connected platforms tidy and consistent, all sitting under domains you recognise.

Your domains are set up once, when you first come on board, across two separate environments: a test environment for building and checking your work, and a production environment for live, day-to-day use. It's a coordinated task rather than a self-service one, because it involves a few changes on your side (with your Domain Name System, or DNS, provider) as well as configuration inside CX Platform.

‍

Set up once, during onboarding
‍Platform domains are configured as part of your onboarding, working alongside the CX Platform team, and cover both your test and production environments. You won't change them in day-to-day use, so if your team is already signing in, there's usually nothing here you need to do.

‍

What your platform domains cover

With full white-labelling, the addresses your team uses to sign in all carry your own brand. Depending on your licensing, your platform domains cover:

• Access to CX Platform – your branded sign-in address for the platform itself, where your members authenticate and get to work.
• Access to connected ChandlerCX platforms – the same branded approach extends to any associated platforms your organisation uses, so your team moves between them under a consistent set of addresses.

Exactly which platforms are covered depends on what your organisation is licensed for, and your onboarding contact will confirm the details. Each is provided in both your test and production environments, which we'll cover next.

Test and production environments

Your platform domains come in two matching sets, one for each environment. Both are white-labelled to your brand, but they're kept separate so your team can build and check changes safely before they go live.

• TEST – a non-production environment where your team can build, configure and validate their work. It's the safe place to try things out and confirm everything behaves the way you expect before go-live.
• PROD – your production, or live, environment. This is the address your team uses for day-to-day work once everything is ready.

The usual flow is to build and confirm your work in TEST first, then move into PROD once you're happy with it.

‍

Set up your domains during onboarding

Here's how the process runs from start to finish.

1. Decide which branded domain (or subdomain) you'd like your team to use for access, and check you have the authority to make DNS changes for it, or know who does.
2. Share your chosen domains with your CX Platform onboarding contact. They'll guide the naming for both your test and production environments.
3. The team will send you the exact DNS records to add for each environment. For an access domain, this is usually a Canonical Name (CNAME) record that points your branded address to CX Platform, along with the certificate needed to secure it over HTTPS.
4. Add the records with your DNS provider. If your DNS is managed by your IT team, hand the records to them to apply.
5. Let the team know once the records are in place. They'll verify everything resolves correctly and switch your domains on across both environments.

That's it. Once your domains are verified and live, your members sign in through your own branded address, with test and production kept neatly separate.

Change a domain later

Need to move to a different domain down the track, perhaps after a rebrand or a change to your web setup? Because a domain change involves DNS updates and re-verification, it's handled with the CX Platform team rather than switched on your own.

Get in touch with your usual support contact and they'll walk you through the same steps, coordinating the cutover across your test and production environments so your team keeps uninterrupted access while the new records take effect.