Navigation
ELOWEN · Documentation

Last updated: October 27, 2026

Browse documentation · Create and enable a chatbot
Channels and chatbots

Create and enable a chatbot

Create the Chetty account behind a chatbot, allow the domain it answers on and switch it on.

Before you start

  • You are an administrator and the Chatbot plugin is installed.
  • At least one active managed Project exists.
  • You know the monthly spend ceiling you want, because a chatbot cannot be enabled without one.

Admin: Only an administrator can create, configure and enable chatbots.

Create the chatbot

  1. Open Chatbots in the main navigation and click New chatbot.
  2. In Account, choose Create a new account, or Use an existing chatbot account to attach a chatbot to an account you already made.
  3. Type a Username and the Display name that visitors see in the chat panel.
  4. Pick exactly one active Managed Project. The chatbot works inside it, owns the transcript, and takes its behaviour and knowledge from that Project's AGENTS.md.
  5. Click Create chatbot. The chatbot appears in the list with status Draft.

A new account becomes a chatbot account: it cannot sign in and cannot be an administrator.

What a chatbot needs

A chatbot answers nobody until three things hold: at least one allowed domain, exactly one active managed Project, and a non-administrator chatbot account. The plugin checks all three again before every admitted message.

If the account's Project is deleted, the chatbot is disabled but keeps its account and conversation history. It is not moved to another Project automatically, so bind it to one again before you re-enable it.

Allow the domain

  1. Open the chatbot in the list and find Allowed domains.
  2. Type the site origin as scheme and host, with no path, for example https://www.example.com.
  3. Click Add domain.
  4. Repeat for every origin that should reach the chatbot.

Note: With no domain listed, the chatbot answers nobody. Once the chatbot is enabled only https origins are accepted; plain http works only for a loopback host such as localhost, for local test pages.

Copy the embed snippet

  1. Open Embed snippet in the chatbot's detail.
  2. Click Copy snippet and send the snippet to the website owner.

The public ID inside the snippet identifies the chatbot and is not a secret. What admits a visitor is the allowed domain, not the ID.

Give the account its tools and model

Every chatbot account needs the tools listed as Required tools in Shared settings. Grants are given per account on the Users screen, which also owns later edits.

A chatbot whose account lacks a grant still answers visitors, but the model never sees the missing tool. Without ChatbotPageAction it cannot touch the page at all.

The answer comes from the chatbot's own account, so the Model row in Account and Project states which model is resolved and why: the account's own pick, the instance default, or a model the account's allow-list forced. Change it on that account.

Turn it on

  1. Open the chatbot and click Enable.
  2. Confirm in the dialog.

Enabling admits visitors from the allowed domains, and every message spends the chatbot's own account. To stop, click Disable and confirm: visitors are refused immediately and recorded conversations stay in the transcript.

Check that it worked

  1. Open the customer's page from an allowed domain in a fresh tab.
  2. Send a short question through the widget.
  3. In Chetty, open Chatbots → Conversations and check that the exchange is listed.

If it does not work

  • No answer at all: check that the chatbot is enabled, that the page origin matches an allowed domain exactly in scheme and host, and that the account has exactly one active managed Project.
  • The detail warns about the Project: the account has none or several. Set exactly one.
  • It answers but cannot use the page: grant the required tools on Users.
  • The widget shows a busy notice: a message is waiting for a free turn, or Chetty is restarting.