Chatbot settings

Chatbot behaviour, appearance, and knowledge base are managed from the settings tabs.

Tabs

• General — name, language, opening hours
• Appearance — primary colour, launcher colour, logo, and chat widget position
• Knowledge — documents and URLs the chatbot learns from
• Responses — personality, tone, forbidden topics
• Integrations — email, Slack, Teams, CRM

The primary colour is used by the header, user messages, and primary buttons. The launcher can have its own colour, and its icon contrast is selected automatically. A white header therefore does not force the launcher to be white.

Current page recognition

The Understand the visitor’s current page switch in AI settings helps the chatbot interpret referential questions. For example, “What does this include?” on a pricing page can be associated with that knowledge-base page.

The feature is off by default. It can be enabled when the chatbot has at least one ready web page in its knowledge base. You do not need to change the embed code or configure the customer site. The chat widget checks the page for each message, so navigation in a single-page application is picked up automatically.

Recognition is used only when the browser page matches exactly one web page in the knowledge base. If there is no match or the match is ambiguous, the chatbot uses its normal knowledge search. Page-aware search does not displace the strongest result from the normal search.

Privacy and boundaries

• The chat widget removes query parameters and the fragment, then derives a fixed identifier from the page origin and path in the browser.
• The chat widget does not send Aihio the raw page URL, page title, text, headings, forms, input fields, or other DOM data.
• The identifier is not stored with the conversation or written to application logs. It is used only to scope knowledge retrieval for that message.
• Keep the feature disabled on sites where the URL path identifies a person or contains sensitive information. If it is enabled in such an environment, assess the processing and describe it in the site’s own privacy notice.

The feature is optional and does not affect normal chatbot behaviour while disabled.

Test recognition with the chat widget published on the website. The dashboard preview does not have the customer page URL, so it uses normal knowledge search.