Your own domain

An agency can serve the dashboard, the sign-in page and the AI employee's script from a domain of its own, such as ai.youragency.com. Its clients then never see Blengi's address: not in the browser bar, not in the install code on their website.

Setting it up

1. Open Branding in the partner dashboard (agency owners only) and choose Set up your domain.
2. Enter a subdomain of a domain you own. The main domain itself (youragency.com) cannot point to us: DNS does not allow a CNAME there.
3. Add the two records the page shows where the domain's DNS is managed:

   Type	Name	Value
   CNAME	ai.youragency.com	the address shown on the page
   TXT	_ai-verify.ai.youragency.com	your agency's code, shown on the page

   The CNAME sends the traffic to us. The TXT record proves the domain is yours, so no one else can claim it first.
4. Choose Check now, or leave it: a new domain is checked again every hour for a week.

At Cloudflare, set the CNAME to DNS only (the grey cloud). With the proxy on, the domain points to Cloudflare instead of us and the secure connection cannot be set up. Some DNS providers want only the first part as the name (ai and _ai-verify.ai) and add the domain themselves. A provider that flattens the CNAME is fine as long as the domain answers with our addresses only.

What the states mean

State	What it means
Waiting for DNS	One or both records are not found yet. The page shows which. DNS changes can take a few hours.
Setting up	Both records are right. The server is getting the certificate for the secure connection, which takes up to 10 minutes.
Live	The domain is in use (see below).
Secure connection failed	The DNS is right, but the certificate could not be set up. The reason is shown. Most often something sits in front of the CNAME, such as Cloudflare's proxy, or a CAA record forbids Let's Encrypt. Fix it and choose Check now.
DNS changed	A live domain's records were removed or changed, found by the daily check. The domain is no longer used until the records are back.

Once the domain is live

• Install code — the script tag and the Tag Manager form of every client's AI employee load from https://ai.youragency.com/w/widget.js, and the widget talks to the API on that domain. Codes already on a client's site keep working: replacing them is optional.
• Sign-in page — https://ai.youragency.com/login shows your branding without the ?p= code. The Branding page's sign-in link becomes this address.
• Dashboard — your people and your clients can work on your domain; the session belongs to that domain.
• Demos — links to your demos open on your domain.
• Allowed origins — a page on your domain may run the chat of any of your clients' AI employees, without adding the domain to each one's list.

One domain per agency. To use another one, remove the current domain first: everything goes back to Blengi's address at once. Mails still link to Blengi's address for now.