AI Help Chat Settings

Purpose

Controls the AI chat assistant that appears inside the admin (and optionally on your public site). When enabled, members and admins can ask "how do I…" or "where do I find…" questions and get an answer that quotes the help documentation and can deep-link back to the right screen.

When to use this

Turn the assistant on for your tenant.
Tweak the welcome message and the suggested prompts.
Decide whether unresolved chats escalate to a support ticket (Chatwoot).

Key fields

Enabled — master switch for this tenant.
Welcome message — first message shown when a user opens the widget.
Quick questions — array of suggested prompts shown as buttons.
Theme — primary colour, position (bottom-right / bottom-left), bubble size.
Show sources — whether the assistant quotes which doc its answer came from.
Tickets enabled — whether the "Couldn't help, raise a ticket" flow is offered.
Ticket routing — where unresolved questions land (Chatwoot inbox, email).
External docs URL — optional override for the View Documentation link in the header.

Common tasks

Turn the assistant on

Settings > AI Help.
Toggle Enabled on.
Save. The system provisions an API key against the chat service and re-indexes the help docs (takes ~30 seconds).
Refresh the admin — the green chat bubble appears at the bottom right.

Customise quick questions

AI Help > Quick questions.
Add 4-8 short prompts users likely want: "How do I create a page?", "How do I add an event?".
Save.

Route unresolved chats to Chatwoot

Connect Chatwoot via Contact Settings first.
AI Help > Tickets enabled = on, Ticket routing = Chatwoot.
Save. When the assistant can't help, it offers a one-click escalation to Chatwoot.

Gotchas

Enabling triggers a re-index of the help docs in pgvector. Allow ~30 seconds before testing.
The assistant only knows what's in the docs — keep your collection-specific Help pages current. See Documents library and the tenant docs in nooq-cms-payload/docs/tenant/help/.
Show sources — turning this on makes answers feel more trustworthy but lengthens them. Most clubs leave it on.
The API key is scoped per tenant — disabling the feature revokes the key. Re-enabling provisions a new one.
Public-site widget — separate from the in-admin assistant. The public widget uses anonymous sessions and a stricter intent classifier.