Timetics AI

⌘K
  1. Home
  2. Timetics AI
  3. Settings
  4. How Do I Connect My Own Custom Domain to Timetics AI?

How Do I Connect My Own Custom Domain to Timetics AI?

What is a Custom Domain?

A custom domain is a unique, branded address used to identify your website on the internet (e.g., yourname.com). By default, our platform provides you with a free subdomain (like ://app.timetics.ai). A custom domain replaces this default link with a professional address that you completely own.

Why do you need it?

  • Professional Branding: It makes your business look credible, trustworthy, and established to your visitors.
  • SEO Benefits: Search engines like Google rank websites with custom domains higher than those using free subdomains.
  • Easy to Remember: A short and unique domain name is much easier for your users to memorize and share.

Step-by-Step Instructions

Step 1: Access Custom Domains

Navigate to Dashboard → Settings → Custom Domains. This page also shows your Personal URL (e.g. `portal.timetics.ai/your-username`), which you can copy and share at any time.

Step 2: Add Your Domain

In the “Custom Domains” section, type the domain you want to use in the input field (for example, `bookings.example.com`) and click “Add Domain”. Timetics AI registers the domain against your workspace and generates the exact DNS record you need to add.

Step 3: Configure the DNS Record

Open a new tab and sign in to your DNS provider (Cloudflare, Namecheap, GoDaddy, etc.). Add the CNAME record shown on the domain card:

  • Type: CNAME
  • Name: your subdomain (e.g. `bookings`) — or `@` for a root domain
  • Value / Target: the target shown on the card (e.g. `app.timetics.ai`)
  • TTL: 300 (or your provider’s default)

Save the record and wait a few minutes for DNS to propagate.

Step 4: Verify the Domain

Return to the Custom Domains page and click “Verify” on the domain card. Timetics AI checks that your CNAME points to the correct target. If the record has propagated, the status changes to “Connected”. If it hasn’t yet, verification keeps retrying automatically in the background — click “Retry Verification” once you’re sure DNS is set.

Step 5: Wait for SSL (HTTPS)

As soon as the domain connects, Timetics AI provisions an SSL certificate for it automatically. The card first shows an “SSL pending” badge, then switches to a green “HTTPS” badge once the certificate is live (usually within 10–30 seconds). Your booking page is now served securely at your own domain.

Step 6: Remove a Domain (Optional)

To stop using a custom domain, click the trash icon on its card and confirm. The domain is unlinked from your workspace, its SSL certificate and server config are cleaned up, and your booking page is no longer served at that address.

Key Functionality

Once connected, your workspace’s public booking page is served on your own domain instead of the shared Timetics URL. When a visitor loads your custom domain, Timetics AI reads the incoming hostname, resolves it to your workspace, and renders your public booking page — themes, branding, and schedules included. Your original Personal URL keeps working alongside the custom domain.

Domain Statuses

  • Pending Setup — Domain added; DNS record not yet verified. Click “Verify” after configuring DNS.
  • DNS Verification Pending — Timetics AI is checking DNS and will keep retrying automatically.
  • Connected — DNS verified; the domain now serves your booking page. SSL is provisioned next.
  • Failed — Verification did not pass. The card shows an error and step-by-step troubleshooting; fix DNS and click “Verify” again.

Prerequisites

  • Active Timetics AI account on a plan that includes custom domains
  • A domain you own, with access to its DNS settings
  • Ability to add a CNAME record at your DNS provider

Notes

Custom domains are gated by workspace plan. If your plan does not include the feature, the section shows an “Upgrade your plan” prompt and adding a domain is blocked until you upgrade.

Subdomains (e.g. `bookings.example.com`) use a standard CNAME and are the simplest to set up. Root/apex domains (e.g. `example.com`) require CNAME flattening, which not all providers support, use Cloudflare or DNSimple, or point an A record to your frontend IP instead. The domain card flags this automatically for root domains.

SSL is fully automatic — there is nothing to upload or configure. If the “HTTPS” badge does not appear after a few minutes, remove and re-add the domain, or contact support.

How can we help?