This guide helps your team get more value from TurboHelp's Live Chat tools. Use it to understand the feature, configure it correctly, and know what to check before relying on it in your daily support workflow.
At a Glance
Use the live chat widget to support visitors in real time without forcing them to leave your site.
Configure identity, routing, forms, and campaigns before driving production traffic to the widget.
Test the widget on desktop and mobile after every meaningful configuration change.
The Live Chat widget settings are divided into the following sections. We’ll go through what each of them contains and how to manage them below.
Widget tab
This is where you manage the widget's appearance and behaviour.
Home Screen
This is the first view your customers see when they open the chat widget. You can customize:
Messages: Set different greeting messages for known, logged-in users versus anonymous visitors. You can also customize the introduction, chat titles, and descriptions.
Background: Make the widget match your site's branding by choosing a flat color, a gradient, or uploading a background image.
Links: Add menu items to the widget's home screen that can link to your help center articles, external pages, or other resources.
Chat Screen
This section controls the appearance of the screen during an active conversation. You can enhance the user experience by enabling options like:
Show previous messages: Allows returning customers to see their past conversation history within the widget.
Show agent avatar: Displays your support agents' profile pictures, adding a personal touch to the conversation.
Launcher
The launcher is the button on your website that customers click to open the live chat widget. You can adjust its position on the page (e.g., bottom right, bottom left) and choose its style. You can display it as a default icon or use custom text to make it more descriptive, like "Chat with us!".
Style and Themes
To ensure brand consistency, you can fine-tune every visual aspect of the widget. Under the Style section, you can either select a predefined theme (like Light or Dark) or create your own.
Custom themes allow you to control:
Fonts
Colors (background, foreground, accent colors, etc.)
Radius (the roundness of corners)
Active Screens
This section allows you to control which main views are available to users inside the widget. You can toggle the visibility of:
Home: The initial welcome screen.
Conversations: A list of the user's past conversations (both tickets and chats).
Help: An area where users can view and search help center content.
By enabling or disabling these screens, you can simplify the widget to only offer the functionality you need.
You can also set default screen to "new chat" or "new ticket" to launch directly into a conversation when live chat is opened.
Forms
Forms are used to gather essential information from your customers.
Pre-chat form: If enabled, this form appears before a customer can start a chat. You can use it to request information like their name, email, or the department they need to reach, ensuring your agents have context from the very beginning.
Post-chat form: This form will appear after user's chat was closed. It's a good place to request user to rate their experience.
For both forms, you can configure which fields are available and which are required.
Automating Chat Workflows with Timeouts
The Timeouts tab helps you manage your support queue efficiently by automating actions on inactive chats. This prevents stale conversations from blocking up your agents' capacity.
Tip: These rules work together to create a self-managing chat queue that keeps conversations moving and maximizes agent availability.
You can configure three key rules:
Transfer customer to another agent: If a customer doesn't respond for a set number of minutes, the chat can be automatically transferred to another available agent or put back into the queue.
Mark chat as inactive: After a period with no messages, a chat can be marked as "inactive." This is useful because inactive chats don't count towards an agent's concurrent chat limit, freeing them up to help other customers.
Close the chat: If a conversation has been inactive for an extended period, you can have the system automatically close it. Customers can always reopen the chat later by simply sending a new message.
Configuring File Uploads
In the Uploads tab, you control the files that can be shared between your customers and agents.
Here, you can:
Set a maximum file size (in bytes) for any single upload.
Create an "Allowed extensions" list to act as a whitelist (e.g.,
jpg, pdf, docx), allowing only those file types to be uploaded.Create a "Blocked extensions" list to prevent specific file types from being uploaded (e.g.,
exe, zip).
If the "Allowed extensions" list is left empty, all file types are permitted except those in the "Blocked extensions" list.
Securing Your Live Chat Widget
The Security tab contains crucial settings for ensuring your chat widget is used correctly and securely.
Trusted Domains: This is an important security feature. By listing your website's domains here (e.g.,
your-website.com), you prevent others from copying your widget's code and placing it on their own unauthorized websites. You can use a wildcard (*.your-website.com) to include all subdomains.Important: It is strongly recommended to populate the Trusted Domains field. Leaving it blank allows anyone to embed your chat widget on their website.
Enforce Identity Verification: For applications where users log in, this feature provides a higher level of security. When enabled, the widget uses a secret key to cryptographically verify the identity of your logged-in users. This ensures that the user is who they claim to be and prevents others from spoofing their identity in the chat.
Tip: This is an advanced security feature recommended for platforms where users have accounts and may discuss sensitive information through chat.
Installing the Widget on Your Website
Once you've configured your widget, it's time to add it to your site! Navigate to the Install tab to get your unique code snippet.
Simply copy the provided <script></script>
Best Practices
Keep the first widget experience short: ask only for the information agents truly need.
Verify identity for logged-in users before exposing account-specific conversation history.
Check widget behavior on key pages after changing themes, forms, or security rules.