Skip to main content

Chatbot Configuration

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.

Prerequisites​

  • The project is set to public (Project Settings → Make Project Public). If it is not public, the widget will not be reachable on your website.
  • You have permission to edit Public Chatbot settings for the project.
  • A Default Agent exists (or will be selected) to answer visitor messages.
  • For Okta client identity: the host page can supply an Okta access token, and you have the Okta Issuer URI.

Accessing the Configuration Interface​

  1. Navigate to your EKB dashboard and open your project.
  2. Go to Public Chatbot in the sidebar menu.
  3. Select the tab you want to configure.
warning

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.

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:

GroupPurpose
GeneralName, copy, suggestions, disclaimer, and default agent
Conversation experienceHow chats look and behave for visitors
CapabilitiesAttachments and tool-call behavior
Access & sessionAuthentication, Okta identity, and idle-session clearing
AppearanceColors, typography, and branding images

General​

FieldDescription
Chatbot NameThe name displayed in the chat window.
Input Placeholder TextThe placeholder shown in the message input box before the user types.
Welcome MessageThe greeting sent when a visitor opens the chat.
SuggestionsPredefined questions shown as prompts. Enter each suggestion on a new line.
Show DisclaimerWhen enabled, displays a disclaimer below the message input. A Disclaimer Text field appears so you can edit the message (up to 500 characters).
Default AgentThe 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.

Conversation experience​

SettingDescription
Show Thinking ProcessWhen enabled, the chatbot displays the AI’s reasoning steps alongside its final response.
Enable Multiple ChatsWhen enabled, visitors can start and manage more than one conversation.
Display SourcesWhen enabled, shows citations and sources used to generate responses.
Display Welcome message above toggle icon (Delay in seconds)Seconds to wait before showing the welcome message above the chatbot toggle. Use -1 to disable. Allowed range is -1 to 10.

Capabilities​

SettingDescription
Allow AttachmentsWhen enabled, visitors can attach files when sending messages.
Allow Tool CallsWhen enabled, visitors can trigger tools and workflows from the public chatbot.
Hide Tool CallsWhen enabled (default), tool calls and their output are hidden. When disabled, tool calls appear as collapsible accordions, matching the main chat experience.

Access & session​

SettingDescription
Enable AuthenticationWhen 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 ChatWhen 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:

SettingDescription
Clear after (minutes)Idle time before the conversation is cleared. Minimum 1, maximum 1440 (24 hours).
Ask Before ClearingWhen enabled, the visitor is asked whether to continue or start a new conversation instead of clearing automatically. The prompt waits until they answer.
info

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.

Appearance (visual branding)​

Use this group for colors, text size, and images. Click Reset to Default to restore visual branding settings to their original values.

SettingDescription
Font Size (px)Text size for the chatbot UI.
Message Bubble/Header ColorHex color for message bubbles and the header background.
Toggle Icon ColorHex color for the chatbot toggle button.
Text ColorHex color for message text.
Caret Background ColorHex color for the caret (cursor) background.
Pre-Chat Attention ImageImage shown before the chat begins (for example a logo or brand asset).
Toggle Button ImageCustom image for the chatbot toggle button.
Widget Header ImageCustom image for the chat widget header.
Pre-Chat Attention Image BehaviorWhen the pre-chat image is shown: Always show on refresh, Never show, or Show every 24 hours.

Troubleshooting (Appearance)​

SymptomWhat to check
Widget missing on the siteProject is public; embed script from Integrations matches this project
Wrong agent answersGeneral → Default Agent
Disclaimer not visibleShow Disclaimer is on and Disclaimer Text is non-empty; Save
Chat clears while the visitor is idleAuto-clear Idle Chat is on — review minutes and Ask Before Clearing
Idle setting will not saveEnter Clear after between 1 and 1440 minutes, or turn Auto-clear off
Tool calls visible / hidden unexpectedlyAllow Tool Calls vs Hide Tool Calls (Hide is default when tool calls are allowed)
Okta identity not appliedToggle on; correct Okta Issuer URI; host page actually passes the access token

Saving Changes​

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.