Public sales and support chatbot

The public chatbot is the external assistant for your website and channel traffic. It answers questions from public content only, refuses code or internal-system questions, and can create sales leads or public support requests without exposing internal CRM tools directly.

What it can do

• answer questions about public products, courses, training, events, and published CMS content
• refuse requests for code, APIs, internal architecture, credentials, admin instructions, or private CRM data
• capture contact sales requests through the existing lead-intake pipeline
• capture get support requests through a reviewable public support intake
• record every session, message, refusal, action, and escalation in the backoffice

CMS page experience

Path: public CMS pages (/page/[slug])

Published CMS pages now show a dedicated assistant launcher.

1. Open a public CMS page.
2. Ask a question about the offering, course, event, or the page itself.
3. Use Contact sales when you want human commercial follow-up.
4. Use Get support when you need service help and want the team to review the request.

The assistant is intentionally narrow:

• it only uses public content for answers
• it will not reveal code or internal technical details
• it creates public support intake first, then operators promote that to an internal ticket when appropriate

Backoffice review

Path: AI → Public conversations (/ai/public-conversations)

Use this page as the operator control plane.

1. Review recent sessions by channel, visitor, source page, and latest activity.
2. Open a session timeline to inspect the transcript, structured actions, and full event history.
3. Review support requests and promote them to CRM tickets when they are ready for internal handling.

This ledger is the audit trail for:

• inbound visitor messages
• assistant replies
• policy refusals
• lead creation
• public support request creation
• support promotion to CRM tickets
• future channel normalization from WhatsApp and Telegram

Configuration

Path: AI → Public chatbot settings (/ai/public-chatbot-settings)

Use this page to control how the public assistant behaves for the active workspace.

1. Turn the assistant on or off globally.
2. Decide whether it should appear on CMS pages, landing pages, or both.
3. Enable or disable direct support-ticket promotion after public intake.
4. Save channel identifiers such as WhatsApp phone-number ids and Telegram bot usernames.
5. Review environment readiness for OpenAI, Meta, and Telegram tokens.

Important boundary:

• provider secrets still live in server environment variables
• the settings page maps channels and surfaces, but it does not expose secret keys in the UI
• support still enters the public-support ledger first, even when direct ticket promotion is enabled

Channels

The same policy and ledger are designed to work across:

• website CMS pages first
• WhatsApp next
• Telegram next
• Messenger and Instagram after a separate feasibility checkpoint

Even when channels differ, the operator experience stays the same because every conversation is normalized into the same session and event model.