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.

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.

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.

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