Configure web chat widget appearance
Customize how the SmartBot web chat widget looks and behaves on your website, including its display mode, position, branding colors, logos, fonts, text content, and sound notifications.
Note: For conceptual background, see SmartBot overview.
Audience: Organization admins and center admins who manage the web chat widget appearance.
Before you begin
- You must have Org Admin or Center Admin access.
- The web channel must be enabled for at least one center in your organization. Bot Settings access requires both admin privileges and web channel enablement. Organizations that configure the web channel at the center level (rather than at the organization level) are recognized automatically.
Permission: Bot Settings requires admin privileges and requires the web channel to be active on at least one center.
Steps
Access the Bot Settings panel
- Log into the SmartBot admin console.
- Select settings from the navigation menu.
- Select Bot Settings from the settings navigation.
Configure widget display and position
- In the Bot Settings panel, configure the following display properties:
- Widget Mode β Select how the widget appears when a guest first loads the page:
- Minimized β The widget appears collapsed with a greeting message visible.
- Expanded β The full chat window opens automatically.
- Icon-only β Only the floating button is shown; guests tap or click to open the chat.
- Widget Position β Choose Left or Right to set where the widget appears on the page.
- Widget Mode β Select how the widget appears when a guest first loads the page:
- Select Save to apply your changes.
Worked example: A spa wants guests to see a welcoming greeting without the full chat window opening immediately. The admin sets Widget Mode to Minimized, enters "Welcome to Serenity Spa! How can we help you today?" as the Greeting Text, and positions the widget on the Right side of the page to keep it out of the way of main page content.
Configure branding and colors
- In the Bot Settings panel, configure the following branding properties:
- Header Color β Enter a hex color code for the widget header background (for example,
#4A2C8Ffor a deep purple). - Font Color β Enter a hex color code for text within the widget (for example,
#FFFFFFfor white text on a dark header). - Font Family β Select a Google Font to use for the widget text.
- Header Logo β Provide a URL to the image displayed in the widget header.
- Chat Logo β Provide a URL to the image used as the bot's avatar during a conversation.
- Header Color β Enter a hex color code for the widget header background (for example,
- Select Save to apply your changes.
Configure widget text content
- In the Bot Settings panel, configure the following text fields:
- Header Text β The title displayed in the widget header bar.
- Greeting Text β The message shown when the widget is in minimized mode.
- Button Text β The label on the button that opens the chat.
- Bot Name β The name displayed as the sender for the bot's messages.
- Select Save to apply your changes.
Configure sound notifications
- In the Bot Settings panel, locate the Sound Notifications setting.
- Toggle sound notifications on or off to control whether the widget plays a sound when new messages arrive.
- Select Save to apply your changes.
Tips
- Match your brand identity β Use the same hex color codes, fonts, and logo URLs that appear on your website. Consistent branding builds guest trust and makes the web chat widget feel like a native part of your site.
- Test all three widget modes β Before settling on a display mode, preview how the widget appears for guests who land on your site for the first time. Minimized mode works well for sites where the chat widget should not distract from primary content; expanded mode works well for high-intent landing pages such as a "Book Now" page.
- Keep greeting text concise β When the widget is in minimized mode, guests see only the greeting text. Aim for one short, action-oriented sentence (for example, "Ready to book? We're here to help.") so it reads at a glance without being cut off on mobile screens.
- Use a square logo image for the chat logo β The chat logo appears as a small circular avatar during a conversation. A square image with equal padding on all sides prevents unexpected cropping.
- Disable sound notifications for always-open kiosk deployments β If your web chat widget runs on an in-center kiosk or lobby screen, consider turning off sound notifications to avoid disrupting the environment.
Troubleshooting
The Bot Settings panel is not visible after logging in. The Bot Settings panel requires both admin privileges and at least one center with the web channel enabled. Confirm that your account has Org Admin or Center Admin access, and verify with your administrator that the web channel has been activated for at least one center in your organization. If the web channel is configured at the center level rather than the organization level, the system checks for any active center with web enabled β ensure at least one such center exists.
Changes to colors, logos, or text do not appear on the website after saving. Your website may be caching the widget configuration. Clear your browser cache and reload the page where the widget is embedded. If the change still does not appear, confirm that the snippet URL embedded in your website is pointing to the correct organization's web chat widget.
The header logo or chat logo is not displaying in the widget. The logo fields accept image URLs, not file uploads. Verify that the URL you entered is publicly accessible (not behind a login or firewall), that the URL points directly to an image file (for example, ending in
.pngor.jpg), and that the hosting server allows the image to be loaded from an external domain (CORS-permissive hosting).The selected Google Font does not appear in the widget. Font loading depends on the guest's browser being able to reach Google Fonts. In environments where external font sources are blocked (for example, some corporate or restricted networks), the widget falls back to the browser's default font. This is expected behavior and does not indicate a configuration error.