Chatbot User Manual

For full integration guide, API reference, and technical details, see Chatbot Technical Documentation.

Overview

Liteed Chatbot is a web widget that answers questions using your content. You can create multiple chatbots, each with its own purpose, style, and context. This guide covers setup, onboarding, and best practices for writing effective context.

Daily limits

• Chatbots creation: up to 2 per day.

Create a chatbot

1. Open Chatbots.
2. Click Create, choose a name, and save.
3. Open the chatbot card to define Context, Allowed origins, and Actions.

Onboard the chatbot to your website

1. Define Context. If no context is defined, the chatbot will not reply. Context is the knowledge base that defines what the chatbot knows and how it speaks.
2. Set Allowed origins. If no allowedOrigins are defined, the chatbot will not appear on your website. Add your production and test domains like https://example.com.
3. Install the widget snippet. See Chatbot technical documentation #integration.
4. Test it live. Open your site, start a chat, and refine your context until answers sound right.

Warning: when you save widget configuration (including theme and behavior), the changes take effect immediately and will be applied to visitors on their next page load. If you are unsure, test changes on a staging domain first.

The widget remembers whether it was open or closed for about 15 minutes after the last user interaction. After 15 minutes of inactivity, the UI state expires and the widget starts from its default state again (usually closed).

Theme and appearance

Each chatbot has a UI — Theme section in the management page. Here you can control how the widget looks and behaves on your site.

Theme mode

• Auto (follow system): widget follows the visitor's operating system preference (light or dark).
• Light: force light theme for all visitors.
• Dark: force dark theme for all visitors.

Theme mode is applied globally per chatbot. Visitors will see the new mode on their next page load after you press Save in the chatbot settings.

Custom theme colors

You can optionally customize colors for light and dark themes. For each side (Light theme colors and Dark theme colors) you can:

• Click Customize to reveal individual color fields.
• Set custom values (for example brand accent color or link color).
• Tick Default to return a specific field to the built-in palette.

Custom colors are per chatbot and do not affect other chatbots. If no custom color is set for a field, Liteed uses a default value that is optimized for readability.

Warning: clicking Reset colors to defaults clears all custom colors for both light and dark themes for this chatbot. This action cannot be undone in the UI and your previous color palette will be lost.

Launcher button and button-less usage

In the theme section you can enable Do not show launcher button. When this option is on, the floating chat button is hidden. The widget is still loaded, but visitors do not see the default launcher.

This mode is useful if you want to use your own custom button or link (for example in the site header or footer) to open the chat. Ask your developer to connect your custom button to the Host-controlled API described in the technical documentation. A typical setup looks like this:

1. In the dashboard:
   - Enable "Do not show launcher button" for the chatbot.
   - Save the configuration.

2. On your website (developer task):
   - Add your own "Chat with us" button.
   - On click, dispatch a browser event to open the widget:

   window.dispatchEvent(new Event('liteed:ui:open'));

3. Optionally, use other events:
   - 'liteed:ui:close' to close the chat.
   - 'liteed:ui:expand' and 'liteed:ui:minimize' to control size.
            

Combined with custom theme colors, this gives you full visual control while keeping the behavior of the managed widget.

How to write good Context

The context defines what your chatbot knows and how it behaves. Write it as plain text or lists. The AI automatically adapts to the visitor's language; if no language is detected, it defaults to the language of your context. You can also define it explicitly by adding: "Use English as default language."

Recommended structure

• Site awareness: include page titles, short summaries, and links. Chatbot may suggest these pages. Use relative paths:
  • /docs — technical documentation overview
  • /about — company background and values
  • /pricing — pricing plans and billing details
  • /contact — contact form and support info
• Company overview: who you are, what you do, your location, languages served, and working hours.
• Products and services: detailed list with features, target users, and pricing logic.
• Portfolio and clients: describe major completed projects or sample case studies.
• Pricing rules: factors influencing cost, available packages, contract process, and payment terms.
• FAQs and policies: delivery time, refund rules, warranty, communication preferences.

Example context (in English)

About the company:
We help small and mid-sized businesses automate repetitive tasks using AI.
Registered in London, operating globally. Support hours: 9:00–18:00 UTC.

Services:
- Business process automation
- Website chatbots
- Custom integrations with CRMs and APIs
Typical delivery time: 2–3 weeks.
Use English as default language.

Site map:
- /about — company overview and mission
- /services — automation tools for teams
- /pricing — subscription options and setup fees
- /contact — message form and support channels

Pricing logic:
Depends on complexity, team size, and integrations. 
Chatbot can help estimate setup time based on input data.
            

Write naturally and keep updating the context as your site evolves. Frequent small edits improve quality over time.

Welcome text (first message)

The welcome text is the message that appears automatically at the start of every new chat session, shown as if sent by the assistant.

It is defined in the “Welcome text” textarea, located directly under the Context field in the Manage Chatbot UI.

Default behavior

By default, the welcome text includes:

• a short greeting
• a privacy notice
• a reminder not to send sensitive or personal data
• links to Terms and Privacy pages

Customizing

You may freely rewrite the welcome text to match your brand voice, tone, and style. You may also modify built-in links or replace them with your own.

Important: The built-in privacy links embedded in the widget UI (About view and widget footer) remain unchanged regardless of your custom welcome text. Those links always point to the official Liteed legal pages.

Recommended uses

• Greeting visitors with a brand-aligned intro
• Explaining what the chatbot can do
• Guiding the visitor toward the right questions
• Linking internal pages like /pricing or /contact

Example

Hello! I’m here to help you explore our services and answer any questions.
You can ask me about features, pricing, or how automation works for your use case.
            

Actions (highlight)

Actions extend the chatbot beyond answering text. Each chatbot can have several actions configured independently. These actions help automate user engagement, scheduling, and data collection. Transfer to agent is not yet available.

• Prompt suggestions: small quick buttons with questions or commands to guide the user.
• Open link: open a specified URL in a new or current tab.
• Request contacts: collect basic contact info (name, email, phone).
• Request callback: let users leave a number and time for a callback.
• Custom form: show a small form with custom fields for quotes or feedback.

Troubleshooting

• Chatbot not visible: check that your domain is added to Allowed origins.
• Chatbot silent: ensure the Context is filled and clear. The chatbot will not talk if it has no content to rely on.
• Wrong chatbot showing: make sure your installed snippet contains the correct appKey.
• Actions not working: verify that the action is enabled and configured correctly.
• Widget opens or closes unexpectedly after some time: remember that UI state expires after about 15 minutes of no user activity. After that, the widget returns to its default state.

Privacy and security

• Widget appears only on allowed domains (allow-listed origins).
• Sessions are isolated; users cannot see others' messages.
• Do not include credentials or private data in the Context.

FAQ