The Public Chatbot configuration interface allows you to customize your chatbot’s appearance, behavior, and functionality. Settings are organized into three tabs: Appearance, Integrations, and Teams App.
Navigate to your EKB dashboard and open your project.
Go to Public Chatbot in the sidebar menu.
Select the tab you want to configure.
If your project is not set to public, the chatbot will not be accessible on your website. To change this, go to your project settings.
Appearance
Integrations
Teams App
The Appearance tab is organized into grouped settings with a sticky Chatbot Preview on the right. Existing permissions and save behavior are unchanged — only the layout and grouping are new.Groups on this tab:
Group
Purpose
General
Name, copy, suggestions, disclaimer, and default agent
Conversation experience
How chats look and behave for visitors
Capabilities
Attachments and tool-call behavior
Access & session
Authentication, Okta identity, and idle-session clearing
The placeholder shown in the message input box before the user types.
Welcome Message
The greeting sent when a visitor opens the chat.
Suggestions
Predefined questions shown as prompts. Enter each suggestion on a new line.
Show Disclaimer
When enabled, displays a disclaimer below the message input. A Disclaimer Text field appears so you can edit the message (up to 500 characters).
Default Agent
The AI agent that handles chatbot responses. A preview card shows the agent’s name, description, and connected tools; open the agent from the card when you need to edit it.
When enabled, visitors can attach files when sending messages.
Allow Tool Calls
When enabled, visitors can trigger tools and workflows from the public chatbot.
Hide Tool Calls
When enabled (default), tool calls and their output are hidden. When disabled, tool calls appear as collapsible accordions, matching the main chat experience.
When enabled, visitors must authenticate before using the chatbot.
Client Identity Resolution (Okta)
When enabled, the embedded chatbot can resolve identity (name, email, and similar) from an Okta access token supplied by the host page, without requiring the visitor to log into this platform. The token is never stored or shown to the AI model. Enabling this reveals an Okta Issuer URI field (for example https://your-tenant.okta.com/oauth2/default).
Auto-clear Idle Chat
When enabled, a conversation left inactive for the configured time is cleared and the visitor starts fresh — including while they still have the chat open. The previous conversation remains in their chat history.
When Auto-clear Idle Chat is on, these additional controls appear:
Setting
Description
Clear after (minutes)
Idle time before the conversation is cleared. Minimum 1, maximum 1440 (24 hours).
Ask Before Clearing
When enabled, the visitor is asked whether to continue or start a new conversation instead of clearing automatically. The prompt waits until they answer.
If the project’s default agent uses a Salesforce toolkit, you may also see Per-user Salesforce Authentication. When enabled, each chatbot user signs in with their own Salesforce account before Salesforce tools run.
Click Save to apply your configuration. Use Reset to Default in the visual Appearance group to revert branding settings only. Unsaved changes are not applied to the live widget until you save.
The Integrations tab provides embed codes and connection options for adding your chatbot to websites and messaging platforms.
Two embed scripts are available — a Window Script and a Widget Script — for adding the chatbot to any website as a full window element or a floating chat bubble respectively.For detailed instructions on embedding the chatbot in websites and frameworks such as Next.js, React, Angular, and WordPress, see Integrate EKB Chatbot to Your Website & Apps.
