Front-End Behavior & Modes: AI Only, AI+Human, Human Only

1. AI Only – telegram_mode = ai_only #

When AI only is selected:

• The chat behaves like a normal AI chatbot.
• According to the docs, Telegram endpoints and handoff logic exist but human mode is not available on the front-end in this mode.
• No AI/Human toggle appears for visitors.
• Messages are always sent to OpenAI using the existing chatbot OpenAI settings.

This is effectively a way to:

• Keep the Telegram bridge configured but temporarily disabled for users.

2. AI + Human – telegram_mode = ai_human #

Docs say:

“If telegram_mode = ai_human:
○ Users see a toggle/switch labeled (e.g.) ‘AI’ / ‘Human’.
○ When ‘Human’ is active:
■ Messages are forwarded to Telegram targets.
■ Replies from Telegram are sent back to the user through the REST endpoints.”

So in AI+Human mode:

• Chat UI shows a mode switch (e.g., a toggle or buttons “AI” / “Human”).
• Visitor can choose:
  • AI → messages go to OpenAI as usual.
  • Human → messages go to Telegram.

Step-by-step flow (user perspective):

1. User opens the chat.
2. They see a small mode toggle somewhere in the chat interface.
3. Initially, the bot might be in AI mode (depending on your defaults).
4. If they switch to Human:
   • New messages they send are forwarded to your Telegram bot and then into the target chats you configured.
   • When your team replies in Telegram, Davix reads those replies (via webhook or polling) and injects them into the chat as human messages.

image IMAGE PLACEHOLDER: Screenshot of the chat widget showing a small “AI / Human” toggle in the header or footer, with Human mode selected and a label explaining messages will be answered by staff. IMAGE image

3. Human Only – telegram_mode = human_only #

Docs list Human only as the third mode:

• In this mode, there is no AI/Human toggle for visitors.
• All messages are sent to human agents via Telegram.
• The chatbot acts purely as a front-end chat UI with Telegram bridging, not as an AI bot.

This is useful when:

• You want to run a human helpdesk using the same chat UI, but still benefit from Davix’s theming, logging, and Telegram integration.
• Or when temporarily suspending AI usage but keep the chat alive with human staff.

4. Interaction with Login-Only Option #

Docs say:

“If telegram_logged_in_only is enabled:
○ Only logged-in users can use human mode (checked via REST permission callbacks).”

So in AI+Human or Human-only modes:

• If telegram_logged_in_only is ON, non-logged-in visitors will:
  • Either not see the human option, or
  • See it blocked with a message, depending on your UI logic described in the code.
• The REST callers validate authentication before allowing messages to go through.

We’ll detail this in Article 4 (Availability & Login-Only).