Settings
Settings is the admin area for workspace-level behavior. The dashboard currently shows two active tabs: Bot and Integrations. API Keys, Connection, and GDPR controls are hidden until a dedicated release.
Bot
| Setting | What it does |
|---|---|
| Bot Name | Adds the workspace bot name to Clark's system prompt. |
| Language | Auto follows the user language; a selected language forces replies in that workspace language. |
| Greeting Message | Used when a linked Telegram chat sends /start. |
| Support Email | Shown when users ask for human support. |
| Accent Color | Stored as workspace brand color for brand-aware document/UI components. |
| Extra System Prompt | Added to Clark's system prompt as workspace-specific instructions. |
Chat Behavior
| Setting | What it controls |
|---|---|
| Listener Mode | Clark saves chat context and can answer when mentioned, replied to, contacted directly, or when it detects a high-confidence useful intervention. |
| Auto Reply | Clark answers every text message in Telegram/Slack group chats without requiring a mention. Use carefully. |
| Daily Summary | Runs Monday through Thursday at the workspace end-of-day hour. If there are no messages for the period, Clark skips it. |
| Weekly Summary | Runs every Monday at 10:00 in the workspace timezone and covers the previous week. |
| Only for CEO / Admin | Sends summaries privately to the CEO/admin when a private delivery target is available. |
| Timezone and business hours | Used by summary schedules and business-hours behavior. |
Settings saved here are workspace defaults. Individual chats can still override chat-level behavior from the Chats page.
Listener Mode
listener_mode=true enables quiet listening in Telegram groups. It applies when auto_reply=false and a group message does not mention Clark.
How it behaves:
- Clark still saves every message into chat history;
- the listener counter is stored as
xdoc:listener_counter:{tenant}:{chat}; - Clark stays silent for the first 2 messages after the counter starts or resets, so it has context;
- questions containing
?are analyzed as soon as the initial context is available; - ordinary messages are analyzed roughly every 5th message;
- the agent must return
SKIPor briefly step in when it has a useful answer from memory, documents, or chat context.
If listener_mode=false, unmentioned group messages do not trigger an answer and are only kept as context/pending escalation.
Auto Reply
auto_reply=true makes Clark answer every text message in Telegram/Slack groups without a mention. In Telegram, Auto Reply bypasses Listener Mode: the message goes directly to the normal active agent response.
Slack currently supports mention OR DM OR auto_reply. The autonomous SKIP/respond Listener Mode is implemented for Telegram.
Integrations
Clark always stores CRM data internally. When Sync with External is enabled, new leads and deals are also sent to configured external systems.
| Integration | Status |
|---|---|
| Bitrix24 | Uses an incoming webhook URL. Test calls get_deals; sync creates leads/deals. |
| AmoCRM | Uses domain and access token. Test calls get_leads; sync creates leads/contacts/deals. |
| 1C | Uses a base URL and optional credentials. Test calls counterparties; sync can create counterparties. |
| Messaging Channels | Informational: Clark currently supports Telegram and Slack chats. Manage chats on the Chats page. |
Secrets are masked when loaded. Saving the form without changing a masked secret does not overwrite the real stored value.