A hosted live chat widget for pages you already have

The public embed is a script tag. The loader is https://cdn.tkit.ai/widget.js and the tag carries data-widget-id with the id from that widget's settings. async is recommended so the script does not block the page. You do not add an npm package to show the launcher.

Widget ids in the product are eight letters or numbers. The sample in the docs uses your-widget-id until you replace it. A query string on the loader URL is still the same script. If you want a second look before publishing, the widget install check reads the tag in your browser and does not upload it.

Allowed domains decide which sites can open that widget. List the hosts you own. A wildcard such as *.example.com covers the subdomains under that pattern. If a host is not listed, the widget does not load there, which is how you stop a copied snippet from running on someone else's page.

The install check cannot see that list. After the tag looks right, open an allowed domain and send a test message. The install guide covers plain HTML and a Next.js script example. A site builder that accepts a footer script, including Webflow, can use the same tag.

Each workspace has its own appearance and copy: colors, logo, team avatars, greeting, and FAQs. The greeting is the first thing a visitor reads, so it should say what you can help with and when a person will follow up. The greeting guide walks through lines that are specific enough to be useful.

Visitors can read the FAQs you wrote before they start a conversation. That is not a separate help center product. It is the content you attach to the widget. If you run more than one product, give each workspace its own widget instead of sharing one greeting across unrelated brands.

A new conversation shows up in the shared inbox with unread state. The team replies from that inbox. You can raise a conversation as a ticket and move it through statuses such as open, resolved, and closed. Attachments travel with the thread. The point of the widget is that the message has one destination, not that the launcher is the whole product.

Tee, the built-in auto-replier, can answer from the notes and FAQs on that widget. It can be paused for one conversation, turned off for the widget, or renamed. A human still owns anything Tee cannot answer. Read the AI website chat page before you turn it on, and the shared inbox page for how the team handles the rest.