Docs · Phone & SMS Setup

Putting the CRM on your own domain

Two DNS records and about ten minutes of your time, then up to an hour of waiting. Your team signs in at your address instead of ours, and your clients never see our name.

Who this is for

An agency owner or admin on the white-label plan who wants the CRM at their own address. You need access to wherever your domain's DNS is managed — often the registrar you bought it from, or whoever built your website.

Before you begin

• Decide the exact address you want. Almost everyone should use a SUBDOMAIN like app.youragency.com or crm.youragency.com, not your bare domain — your website already lives there, and pointing the root at us would take it down.
• Get access to your DNS settings. If your website was built for you, this is usually the person who built it. You are looking for a page called DNS, Name Servers, or Advanced DNS.
• Allow an hour. The work is ten minutes; DNS changes then spread across the internet on their own schedule.

Steps

1. In Agency Settings → Branding → Custom Domain, type the address you want (e.g. app.youragency.com) and click Connect domain.
2. We show you two records. Copy them exactly — DNS is unforgiving about stray spaces and trailing dots.
3. Add the TXT record. This proves you own the domain; it does not affect your website. You can delete it once we say Live.
4. Add the CNAME record. THIS is the one that sends visitors to your CRM. If your registrar rejects a CNAME because a record already exists at that name, delete the old one first — two records cannot share a name.
5. Come back and click Check DNS. If it says we can't see it yet, that is normal; wait and click again.
6. Once it reads Live, open your new address. It should load your CRM, with your logo, over https.

Your domain is a set of signposts. Right now nothing points app.youragency.com anywhere, so a browser asking for it gets no answer. The CNAME record is the signpost that says 'this address is served over there'. The TXT record is separate and exists only so we can confirm you actually control the domain before we start serving your branding on it — without that check, anyone could point a hostname at us and stand up a convincing copy of your agency on an address they own.

HTTPS is handled for you. Once the CNAME resolves we issue the certificate automatically; there is nothing to buy and nothing to install. It usually completes within a few minutes of the domain going Live.

Adding a domain does not take the old one away. Your team can keep signing in at the shared address for as long as they like — the two work side by side, so there is no cutover moment and nothing breaks while you are still testing.

How to check it worked

• The domain reads Live in Agency Settings.
• Visiting your new address loads the sign-in page with YOUR logo and colours, not ours.
• The padlock in the browser shows a valid certificate for your domain.
• Your existing website is still up. If it went down, you pointed the ROOT domain at us instead of a subdomain — remove that record and use a subdomain.

Common mistakes

• Pointing the bare domain (youragency.com) at us. That is where your website lives, and it will disappear. Use a subdomain.
• Adding the records at the wrong registrar. If your name servers point somewhere else — a host, a CDN, Cloudflare — the DNS you need to edit is THERE, not where you bought the domain.
• Typing the full hostname into the Name field when your registrar only wants the label. Some want 'app', some want 'app.youragency.com'. If your registrar shows existing records, copy whichever style they use.
• Clicking Check DNS once, seeing it fail, and assuming it is broken. Propagation of up to an hour is normal and there is nothing to fix in the meantime.
• Deleting the TXT record before the domain reads Live. It is the proof of ownership; remove it after, not during.

Related

Where this lives in the app

This is documentation for Virtual Closer. Book a walkthrough or sign in.