Everything you need to know — from creating your first bot to embedding it on your website.
QubotAi lets you build a smart, trained AI chatbot for your website — without writing a single line of code. You feed it your content, it learns from it, and your visitors get instant, accurate answers around the clock.
Whether you run a small business, an e-commerce store, a SaaS product, or a professional service — QubotAi turns your existing knowledge into a 24/7 customer-facing assistant that handles questions, collects leads, and keeps visitors engaged.
Your bot answers questions at 2 AM on a Sunday, while you sleep. No missed leads, no frustrated visitors waiting for a reply.
When a visitor asks something the bot can't answer, it can collect their name and contact details — turning a dead-end into a warm lead for your team.
Repetitive questions — pricing, hours, return policy, how-tos — get answered instantly. Your team focuses on the queries that actually need a human.
The bot detects the visitor's language and replies in the same one automatically — no extra setup needed for a multilingual audience.
Add the bot to any website — WordPress, Shopify, Webflow, or plain HTML — by pasting two lines of code. No developer needed.
See what visitors are asking, how many sessions you're getting, and which bots are performing — all from a single dashboard.
Upload your docs, paste your FAQs, or point it at your website. Hit Train and the bot learns your content in minutes.
Set your brand color, choose a voice, write an opening message, and adjust the persona with a Master Prompt — all from the dashboard.
Copy two lines of code from your bot's page and paste them into your site. Your AI chatbot is live — immediately, everywhere.
A bot is your AI-powered chatbot. You can create multiple bots — one per website, product, or use-case, depending on your plan.
Open a bot and click Edit to access all settings. They are grouped into four sections.
masterPrompt passed via the embed snippet (see Section 6) interacts with this Master Prompt.
#4f46e5 (indigo).
Controls automatic AI summarization of conversations after a visitor goes idle. Manual summarization from the conversation detail page is always available regardless of this setting.
Allows your widget to accept file and image uploads from visitors. Uploaded files are stored securely and are not processed by AI or read as knowledge — they are simply collected for your team to review and download.
Contexts are the knowledge sources your bot learns from. Without contexts, your bot can only use its Master Prompt. Add at least one context before training.
Open your bot → click Add Context. You can add multiple contexts of different types to the same bot.
Directly paste or type any text — FAQs, product descriptions, policies, or anything you want the bot to know. Ready immediately — no processing needed.
Best for: Short FAQs, quick facts, manual content entry.
Provide a URL and QubotAi scrapes the content automatically. Three scraping modes:
sitemap.xml URL; scrapes all listed pages (up to 100).Best for: Entire websites, documentation portals, knowledge bases.
Upload any PDF file (max 20 MB). QubotAi extracts the text content automatically.
Best for: Product manuals, brochures, reports, legal documents.
Upload a .doc or .docx file (max 20 MB). Text is extracted and processed automatically.
Best for: Internal documentation, onboarding materials, SOPs.
Upload a .csv or plain text file (max 20 MB). Rows are extracted as structured text the bot can reference.
Best for: Product catalogues, pricing tables, structured data.
Upload a .md or .txt file (max 20 MB). Great for developer documentation or any plain-text content.
Best for: README files, developer docs, changelogs.
File and website contexts must be processed before training. You will see one of these statuses on your bot's context list:
Training converts all your contexts into searchable AI knowledge (vector embeddings). The bot uses these at query time to find the most relevant chunks and include them in its response.
You must retrain whenever you want the bot to reflect changes. Retrain when:
For website and file-based contexts, you can click Reprocess on the context to re-fetch/re-extract its content (without adding a new context). This is useful when:
After reprocessing completes (Ready), click Train Bot to apply the new content.
Before embedding the bot on your live website, test it directly from your dashboard using the Try Bot button — available on a bot's detail page once its status is Ready.
The Try Bot page opens a live, full-featured chat interface powered by the same AI engine your visitors will use. Use it to:
Copy the two-line snippet from your bot's detail page and paste it just before the </body> closing tag on any page of your website.
Replace YOUR_API_KEY with the API Key from your bot's settings page. Each bot has a unique key — do not mix them up.
The snippet works on any platform — WordPress, Shopify, Webflow, Wix, custom HTML, or any framework.
Add a masterPrompt key to provide additional instructions on a specific page. Depending on your Widget Prompt Strategy setting (see Section 2), this will either replace your default Master Prompt or be appended to it.
You can override the Widget Theme setting from your bot dashboard on a per-page basis using the theme key. Useful if only one page on your site has a dark background.
Create a small component that injects the script once on mount:
The Master Prompt is the single instruction that defines how your bot behaves. Your training data provides the facts; the Master Prompt provides the personality, rules, and fallback behavior.
Best when you want to capture contact details for questions the bot can't answer.
Best for lifestyle, creative, or consumer brands.
Best for legal, medical, or compliance-heavy contexts.
Override the default prompt only on your pricing or landing page.
Go to Analytics in the sidebar to get a birds-eye view of how all your bots are performing. Data is aggregated across every bot you own.
Total number of individual exchanges (user message + bot reply) across all your bots, all time.
Number of unique visitor sessions that have chatted with any of your bots. Each browser session is counted once.
Count of your bots that are in Ready status and have received at least one message.
Total messages ÷ total sessions. A higher number means visitors are having longer, more engaged conversations.
Number of sessions where a visitor hit the per-session exchange limit you configured. Useful for tuning your Chat Limits setting.
A dual-line chart showing sessions and messages per day over the past 30 days. Gaps on days with no activity are shown as zero — not omitted — so you can clearly see quiet vs. busy periods.
A ranked table of your bots sorted by total message count. Shows message count and unique session count per bot — useful when you have multiple bots and want to see which ones are getting the most traffic.
The 5 most recently active sessions across all bots, with the last message preview and timestamp. Click any session to jump straight to its full conversation in Chat History.
Go to Chat History in the sidebar to browse every conversation your bots have had. You can filter by bot and paginate through sessions.
Each row in the list represents one visitor session and shows:
Click any session to open the full conversation transcript, displayed in the same chat-bubble format the visitor saw. You can also see:
On any session detail page, click Generate Summary to have the AI produce a structured summary of that conversation in seconds.
The summary is structured into four sections using Markdown:
Go to Export Data in the sidebar to download your bot's conversation data as CSV files. You select a bot and an optional date range, then download one or both export types.
One row per individual message exchange. Downloads as .csv. Contains:
YYYY-MM-DD).
HH:MM:SS).
Yes or No — flags messages that were sent after the session exchange limit was hit.
One row per visitor session. Downloads as .csv. Contains:
YYYY-MM-DD HH:MM:SS).
Both exports accept an optional From and To date. Leave both blank to export all data. When a range is set, the filename includes the dates for easy archiving — e.g. my-bot-conversations-2025-01-01-to-2025-01-31.csv.
Interact Mode turns your text chatbot into a fully voice-driven conversation. Visitors can speak to the bot, hear its reply spoken aloud, and interrupt it mid-sentence — just like a real conversation.
https:// before enabling this feature.
Choose the voice the bot speaks with. Available voices:
Visitors do not have to wait for the bot to finish speaking. If they start talking while the bot is mid-reply, the bot detects the interruption, stops speaking immediately, and begins listening. This makes conversations feel natural and fluid.
The bot automatically detects the language of each spoken message and replies in that same language. Speak in English, get an English reply. Speak in Hindi, get a Hindi reply — no configuration needed.
In Interact Mode the bot keeps its replies short and conversational — typically one sentence — so they sound natural when spoken aloud. Bullet points, lists, and markdown formatting are suppressed automatically in voice mode.
Get an automatic email digest of all conversations your bots have had — delivered to your registered email address at whatever frequency you choose. Each email summarises every session in 2–3 plain-English sentences so you can stay on top of what your visitors are asking without opening the dashboard.
The report relies on AI-generated conversation summaries. Here is what happens automatically before each email is sent: