Connect your custom domain
By default, your booking pages, funnels, and client portal live at long, generic URLs like app.intellivizz.ai/widget/abc123xyz. That works, but it's not branded — customers see Intellivizz, not you. Connecting a custom domain (or subdomain like book.yourbusiness.com) lets your customer-facing surfaces use your own branded URLs.
This is a Day-1 setup task because DNS changes can take 1–48 hours to propagate, so the earlier you start, the better. The actual configuration is small — maybe 10 minutes of work — but the wait time is unavoidable.
Decisions to make first
Use a subdomain or a full domain?
Most clients use a subdomain (book.yourbusiness.com or app.yourbusiness.com) rather than connecting a full root domain (yourbusiness.com). Why?
Your existing website probably already lives at yourbusiness.com — you don't want to break it
Subdomains keep your CRM-driven content separate from your marketing/SEO website
Common pattern: book.yoursite.com for booking pages, portal.yoursite.com for client portal, learn.yoursite.com for course/membership
NOTE — If you don't have an existing website
If you don't already have a website at yoursite.com, you have two options: (1) Use Intellivizz CRM's built-in website builder and connect the root domain (yoursite.com) to it. (2) Use a subdomain anyway (book.yoursite.com) and leave the root for later. Both work — option 1 is faster to launch, option 2 is more flexible long-term.
Step-by-step
1. Log in to your domain registrar
Your domain registrar is wherever you bought the domain — GoDaddy, Namecheap, Google Domains (now Squarespace Domains), Cloudflare, etc. You'll need administrator access to make DNS changes.
57. Find the email confirming your domain purchase if you don't remember the registrar
58. Log in with your admin credentials
59. Navigate to DNS settings (sometimes under "Manage DNS", "DNS Management", or "Domain Settings")
2. Add the required DNS records
In Intellivizz CRM, go to Settings → Domains → "+ Add Domain". You'll be shown the exact DNS records to add at your registrar. The standard pattern:
| Record type | Host / Name | Value / Points to |
|---|---|---|
| CNAME | book (or chosen subdomain) | domains.intellivizz.ai |
| TXT (verification) | @ or _intellivizz | Random verification string given by Intellivizz |
WARNING — Don't replace existing records by accident
If you're adding a CNAME for 'book' and your registrar's DNS panel has an existing 'book' record (rare but possible), update or delete that one first. Adding a duplicate often results in only one being honored, with unpredictable results. Always read the existing records before adding new ones.
3. Wait for DNS propagation
After saving the records at your registrar, DNS changes propagate across the internet over 1–48 hours. Most of the time it's under 1 hour, but plan for up to 48 hours.
60. Set TTL (time to live) to 1 hour or 3600 seconds for faster updates
61. If verification fails, wait 30 minutes and try again — don't keep clicking, it's just propagation
62. Once verified, the status changes to "Connected"
4. SSL certificate auto-provisions
Once the domain is verified, Intellivizz CRM automatically requests an SSL certificate from Let's Encrypt and installs it. This usually takes 5–15 minutes.
You'll see status change from "Connected" to "SSL Active"
Test by visiting your domain in an incognito window — it should load with a green padlock
Certificates auto-renew every 90 days; you don't need to do anything
5. Map specific products to the new domain
Now that the domain is live, point specific products at it:
63. Calendars: Calendar settings → Booking Page URL → use the new custom domain
64. Funnels: Funnel settings → Domain → select your custom domain
65. Memberships: Course settings → Domain
66. Client Portal: Settings → Client Portal → Domain
Field reference
| DNS field | What it means |
|---|---|
| Type | The kind of record. CNAME is the most common; some registrars require an ALIAS or ANAME for root domains. |
| Host / Name | The subdomain part. "book" makes book.yoursite.com; "@" or blank means the root yoursite.com. |
| Value / Points to / Target | Where the record sends traffic. For Intellivizz: domains.intellivizz.ai |
| TTL | Time-to-live — how long DNS resolvers cache the value. 1 hour (3600s) is the common default. |
Worked examples
Worked example: Adding 'book.heritageaccounting.com' for a CPA firm
Heritage Accounting already has a marketing website at heritageaccounting.com hosted on WordPress. They want their tax-prep booking page to live at book.heritageaccounting.com without disrupting the main site.
Steps: (1) Log in to Namecheap (their registrar). (2) Go to Domain List → Manage → Advanced DNS. (3) Add a CNAME with Host=book, Value=domains.intellivizz.ai, TTL=1 hour. (4) Add the TXT verification record Intellivizz provides. (5) Save. (6) Wait 25 minutes. (7) Click Verify Domain in Intellivizz CRM — it confirms. (8) Wait another 10 minutes for SSL. (9) Visit book.heritageaccounting.com in incognito — sees the booking page with green padlock.
Total elapsed time: ~40 minutes. Total active work: 10 minutes.
Worked example: Connecting a brand-new root domain to Intellivizz Sites
Marco Hidalgo just registered marcohidalgorealty.com last week. He has no existing website, so he's going to use Intellivizz CRM's site builder.
Because there's no existing site to protect, he's connecting the root domain (no subdomain).
At Cloudflare, he removes the parking-page A records, then adds: ALIAS / ANAME @ → domains.intellivizz.ai. (Cloudflare supports CNAME flattening for root, so a CNAME also works.)
He also adds a CNAME: www → marcohidalgorealty.com so both versions work.
After 15 minutes, Verify Domain succeeds. He builds his site in Intellivizz CRM Funnels and goes live the same afternoon.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Verify Domain fails immediately | Records not yet saved at registrar, or you're checking too soon | Confirm records at registrar; wait 30 min; try again |
| Verify works but SSL won't activate | Conflicting CAA record at registrar restricting Let's Encrypt | Remove or update CAA records to allow letsencrypt.org; or remove CAA entirely |
| Domain shows "Connected" but visiting it returns a 404 | Domain is verified but no product is mapped to it yet | Map a calendar, funnel, or page to the domain in their respective settings |
| My existing website broke after adding records | Replaced an existing A or CNAME by mistake | Restore the previous record from your registrar's audit log; only the SUBDOMAIN should be changed |
| dig/nslookup shows correct value but Intellivizz still won't verify | DNS cache at Intellivizz's verifier hasn't refreshed | Wait 15 more min; if persists, contact support — they can force a recheck |
| Mobile devices don't connect, desktop does | DNS-over-HTTPS on the mobile resolving to a stale value | Wait the full 48 hours of TTL; or test with airplane-mode-on/off cycle |
| After it was working, domain stops resolving | TTL expired and registrar removed the record (or you removed it) | Re-add the records; check registrar billing isn't lapsed |
| Multiple subdomains conflict (book + portal + learn) | Each needs its own CNAME record at the registrar | Add 3 separate CNAME records: book → domains.intellivizz.ai, portal → domains.intellivizz.ai, learn → domains.intellivizz.ai |
Success criteria
I logged in to my domain registrar and added the required CNAME and TXT records
I clicked Verify Domain in Intellivizz CRM and got a 'Verified' confirmation
Status changed to 'SSL Active' — I can see the green padlock in incognito
I mapped at least one product (calendar, funnel, or page) to the new domain
Visiting the new domain shows my Intellivizz-hosted page, not a 404
My existing website (if any) still works correctly at the root domain
