BidirectionDocs
Open the console

Add your domain

List the websites your agent runs on. It works there as soon as you add one — proof by DNS is only for single sign-on.

SettingsDomains

Your widget runs on the websites you list in Settings · Domains. Add a domain and it works there straight away — there is nothing to prove. On a site that is not on the list, the widget stays hidden.

Add it#

  1. Open Settings and choose the Domains tab.
  2. Enter the domain — support.acme.com. You can paste the full URL straight from your address bar (https://support.acme.com/pricing) and we take the host from it.
  3. Press Add domain.

It appears on the list as Active. Your agents can run there now.

You can also start from an agent: on its Deployment tab, step 1, Say where it may run, has an Add a domain link that brings you here.

Owners and Admins add and remove domains. Everyone else sees the list read-only.

www and the bare domain#

Adding either spelling covers both. You do not need two entries for acme.com and www.acme.com. This applies to the www pair only — a subdomain like app.acme.com is its own entry, and so is a staging or preview address.

Which agents run there#

A domain that no agent is attached to works for every agent in your workspace. To keep a domain for one agent, attach it on that agent's Deployment tab — see Attach domains to agents.

Customer calls and test calls#

Calls that start on a domain on your list are customer calls, and they count in your numbers. Calls you start from the console's own test pages — Test conversation and Agent preview — are test calls, and they stay out of your numbers. See Preview before you launch.

If another workspace lists the same domain#

That is allowed. Several workspaces can list the same domain, so nobody can block you by adding yours first. Listing a domain gives a workspace nothing on its own: the widget only runs where the page loads that workspace's own code.

Prove ownership — for single sign-on only#

You do not need this for the widget. Only single sign-on needs proof that a domain is yours, and the proof is a DNS record.

  1. In Settings · Domains, press Prove ownership on the domain.
  2. Press Copy record. The record looks like bidirection-verify= followed by a long string of letters and numbers.
  3. Add it as a TXT record with your DNS provider — either on the domain itself or on _bidirection-verify. in front of it (_bidirection-verify.acme.com), whichever your provider makes easier.
  4. Press Check.

When it passes, the domain reads Active · owner proven.

If it still fails after 15–30 minutes, the record is usually at the wrong host name or has a typo. Compare it character for character with the record in the console.

Only one workspace can prove a domain.

Removing a domain#

Remove takes the domain off your workspace's list. It does not touch your DNS. Bidirection lists what happens before you confirm: your agents stop answering there immediately, any agent attached to it is detached, and — if you proved the domain — single sign-on that relies on it stops working.

You can add it again later.