Multi-Role AI Chatbot adds a floating, context-aware AI chat assistant to any Drupal site, serving several distinct audiences from a single module: a staff console, authenticated clients scoped to their own data, anonymous visitors, and any number of admin-created custom chats. Each chat has its own system prompt, welcome message, visibility rules and suggestion buttons, and talks to a AI provider powered by Anthropic Claude . It is ideal for teams that want a single, governed chat experience covering internal support, client self-service and public visitor help — with strict privacy, per-chat budget controls and optional escalation into a support workflow.

Key features

Multiple audiences, one module — Configure a staff console for authenticated team members, a clients chat for authenticated non-staff users, an anonymous-visitor chat, and any number of custom chats such as "SEO" or "Marketing".
Per-chat personality — Each chat defines its own system prompt, welcome message and suggestion chips, so the assistant behaves appropriately for its audience.
Visibility rules — Show each chat only to the right roles and on the right pages, so the floating button appears exactly where it should.
Read-only database context — Optionally let a chat read selected, allow-listed database areas as conversation context, always restricted to what the chat's visibility role is permitted to see and never another user's data.
Monthly budget controls — Set a monthly spend budget per chat to keep AI usage predictable and under control.
Escalation to task requests — Optionally let users escalate technical problems into structured support task requests directly from the conversation.
Polished floating widget — A minimizable chat panel with suggestion chips, optional image attachments where enabled, and UI state persisted in the browser.

How it works

Once a chat audience is enabled and the visitor's role and current page match its visibility rules, the module renders a floating chat button. The assistant builds its conversation context from the configured system prompt plus only the read-only database areas the visibility role is permitted to access. Administrators manage every chat from a single settings page under Configuration » Web services, where they enable audiences, write prompts and suggestions, set visibility, choose the AI provider and model, and define budgets and escalation behavior. Permissions (use ai ticket chat, use clients ai ticket chat, use anonymous ai ticket chat and administer ai ticket chat) gate who can use each chat and who can configure the module.

Use cases

Internal support console — Give staff a context-aware assistant that clarifies, classifies and drafts support requests.
Client self-service — Offer authenticated clients an assistant scoped strictly to their own data.
Public visitor help — Answer anonymous visitors' questions with a dedicated prompt and visibility profile.
Department-specific chats — Spin up custom chats for teams like SEO or Marketing, each with its own behavior and audience.

Part of the Central Connect AI suite

Multi-Role AI Chatbot is a consumer module of the Central Connect AI suite, built on the suite's shared foundation. It is fully usable standalone, and integrates with the other suite modules when present:

Central Connect AI SDK — the shared connection layer the chatbot builds on. Required.
AI Ticket Chat — when present, escalated chat requests are routed into its support task backend, giving you a complete AI-assisted support pipeline. Optional.
Web Health Status — a site-owner dashboard in the same suite whose multi-role assistant block is powered by this module.

Requirements

Drupal — Drupal 10.3+ or Drupal 11.
Drupal core — User module.
Central Connect AI SDK — the shared connection layer for the suite.
Session Limit — required contributed dependency.
AI provider API key — an API key for the chosen provider (Anthropic or Gemini), supplied through settings.php or State, never as exported configuration.
Optional: AI Ticket Chat for routing escalated requests into a support task backend.

Privacy and security

CSRF protection — All state-changing endpoints require a CSRF request header token.
Rate limiting — The message, session and task endpoints are protected by Drupal's Flood API.
Strict payload validation — Message and history length, numeric IDs, image MIME type and size, and allowed context URLs are all validated.
Allow-list database context — Database context is allow-list only and additionally filtered by the visibility role's permissions, so a user can never query another user's data.
Secrets never exported — API keys and other secrets are read from settings.php or State and are never written to exportable configuration.

Maintainers and sponsor

This module is developed and maintained with sponsorship from Tangram Consulting as part of the Central Connect AI suite. Contributions, bug reports and feature requests are welcome through the project's issue queue on drupal.org.

AI Chatbot & Live Chat - Customizable Roles