SimpleBot support

Build it clearly.
Test it honestly.

Use these guides to create, train, test, and install your bot. Each direction matches the controls in the current SimpleBot dashboard.

Open your bots Start with the checklist
Quick start

Your shortest path to a useful bot.

Start with one job, a small set of trustworthy documents, and the questions real visitors already ask.

  1. 01
    Create

    Open Dashboard, select New bot, enter the primary website, add an optional logo, then name and create the bot.

  2. 02
    Train

    Open Knowledge, add a small set of clear and current files, and wait for every source to show ready. Use the training-material guide below to prepare them.

  3. 03
    Shape

    Select Instructions, set the system prompt, welcome message, and conversation starters, then select Save instructions.

  4. 04
    Preview

    Use Preview to try common, paraphrased, unsupported, and sensitive questions before launch.

  5. 05
    Connect

    After configuring Bookings & Intake, open Embed Bot. For WordPress, download the plugin, then sign in from the plugin and choose the bot. Other websites can use the website code.

  6. 06
    Launch

    Choose a plan for this bot, publish its saved configuration, and test the WordPress launcher. For another website platform, select its connected domain under Embed Bot and copy the website code.

Training material

Give your bot clear information it can trust.

Well-prepared sources produce better answers than a large collection of mixed or outdated files. Start small, test real questions, and improve the source whenever an answer is missing.

Write for customers

Use plain, direct answers under descriptive headings. Include exact steps, exceptions, eligibility rules, and the language customers actually use.

Keep one source of truth

Remove duplicate or conflicting versions. Add a last-reviewed date, and replace an old source instead of uploading another version beside it.

Separate live information

Use connected capabilities for changing catalog or account data. Avoid training product URLs, prices, stock, variations, and other facts already available through MCP.

Make the text searchable

Use selectable text, short sections, lists, and meaningful headings. Avoid scans, image-only PDFs, dense page furniture, and unrelated material.

Define boundaries

Document what the bot may answer, when sign-in is required, and when to offer human support. Never upload secrets or private customer information.

Test and refine

Ask exact questions, paraphrases, follow-ups, and unsupported questions in Preview. Correct the knowledge itself when the answer is incomplete or wrong.

A useful source usually includes

  • Business overview, audience, services, and terminology
  • Frequently asked questions with direct approved answers
  • Policies, limitations, exceptions, and effective dates
  • Login, registration, billing, cancellation, and support steps
  • Public versus signed-in customer instructions
  • Escalation guidance and the correct support contact
Starter prompts

Prepare your content with your preferred LLM.

Copy a prompt, replace the bracketed placeholder with your information, and review the result before uploading it to SimpleBot.

Turn my information into a training document

Use this when your policies, services, and answers are spread across notes or existing pages.

Organize the information I provide into a customer-facing knowledge document for SimpleBot.

Requirements:
- Use clear Markdown headings organized by topic.
- Put one subject in each short section.
- State the approved answer directly, in plain language.
- Add common customer questions and natural paraphrases for each topic.
- Preserve important qualifications, eligibility rules, exceptions, dates, and contact instructions.
- Separate public information from instructions that apply only to signed-in customers.
- Do not invent missing facts or use outside knowledge. Mark gaps as [INFORMATION NEEDED].
- Remove repetition, internal commentary, drafting notes, and instructions addressed to the AI.
- Do not include passwords, API keys, private customer data, or confidential internal information.
- Finish with a list of contradictions or unclear points I should resolve before uploading.

Here is my source material:
[PASTE YOUR INFORMATION HERE]

Audit an existing training document

Use this before replacing or adding a source in SimpleBot.

Review the following SimpleBot training document for accuracy and retrieval quality.

Check for:
- conflicting or duplicated answers;
- outdated policies, dates, contacts, links, prices, products, or availability;
- vague statements that could produce an unsupported answer;
- missing customer questions, synonyms, and paraphrases;
- internal terminology that should be rewritten for customers;
- content that belongs in a live integration instead of training material;
- private data, secrets, or instructions that should not be uploaded.

If the bot has a live catalog or MCP connection, flag product names, product URLs, prices, ingredients, variations, stock, and availability for removal from the training document. Live integrations should be the source of truth for those facts.

Return:
1. A prioritized issue list.
2. Questions I need to answer.
3. A cleaned Markdown version that does not invent information.

Document:
[PASTE YOUR DOCUMENT HERE]

Build a customer-support FAQ

Use this to cover the questions visitors are most likely to ask.

Create a comprehensive customer-support FAQ for a SimpleBot using only the business information I provide.

Organize it around real customer intents, including getting started, account access, ordering or service use, billing, cancellations, privacy, troubleshooting, human support, and any business-specific topics present in the material.

For each topic:
- write a clear canonical answer;
- include 3 to 5 natural ways a customer might ask the same question;
- preserve all restrictions, exceptions, and required steps;
- say when a signed-in account or human team is required;
- link only to URLs present in my source material;
- mark unsupported answers as [INFORMATION NEEDED].

Do not invent policies or facts. Do not include live product, price, stock, or account data that should come from an integration.

Business information:
[PASTE YOUR INFORMATION HERE]
Step-by-step guides

Go straight to the setting you need.

Account access

Sign in and open your Dashboard

  1. Select Login in the top-right corner of the home or Support page.
  2. Continue with Google, or enter your email address.
  3. Complete the displayed verification steps.
  4. After authentication, open Dashboard from the top-right button.

If the top-right button already says Dashboard, you are signed in. Never send a password, verification code, or session token to support.

Knowledge

Add material your bot can trust

  1. Open Dashboard, choose the bot, then select Knowledge in the left menu.
  2. Review the training-material guide on this Support page before preparing a large source collection.
  3. Select Add files, or select the upload area.
  4. Choose PDF, DOCX, TXT, Markdown, or HTML files up to 50 MB each.
  5. Wait for queued and processing sources to become ready.
  6. Use Preview to ask questions the new knowledge should answer, including natural paraphrases.

A failed source is not available to the bot. Read the displayed error and try a smaller, clean copy. When MCP supplies changing catalog or account data, do not duplicate that information in training files.

Behavior

Set the role, tone, and welcome

  1. Open the bot and select Instructions.
  2. Update the bot name and description under Name and description.
  3. Under How it should respond, describe the role, tone, audience, and boundaries.
  4. Edit the welcome message, then add each Conversation Starter in its own field.
  5. If the bot can track orders, add the customer tracking-page template under Customer tracking page.
  6. Select Save instructions and wait for confirmation.
  7. Use Preview to review the result.

Keep changing business facts in uploaded sources. Conversation Starters appear only when a visitor begins a new chat; later reply buttons adapt to the current conversation.

Conversation Starters

Start each chat with useful choices

  1. Open the bot and select Instructions.
  2. Find the public visitor and signed-in customer Conversation Starter lists under How it should respond.
  3. Add public questions that never imply access to private account data.
  4. Add signed-in questions for approved customer capabilities, such as tracking the customer’s latest order.
  5. Type one short opening question, then press Enter or select Add starter. SimpleBot shows up to three from the matching list when a visitor begins a new chat.
  6. Select Save instructions and wait for confirmation.
  7. Open Preview and confirm each button sends the text shown on it.

SimpleBot switches starter lists when the website verifies the customer’s email. After the visitor asks a question, it replaces starters with up to three context-aware reply buttons based on the latest answer, conversation history, approved capabilities, and verified-session state. Booking and human-support buttons remain separate validated workflows.

Bookings

Collect intake before Calendly

  1. Open the bot and select Bookings & Intake.
  2. Turn on the booking-intent option.
  3. Add the full HTTPS Calendly event link.
  4. Edit the button label, intake title, and introduction.
  5. Select Add for each question, choose its type, and mark Required when needed.
  6. For choice questions, enter options separated by commas.
  7. Select Save booking setup, wait for confirmation, then open Preview and ask “Can I book a demo?”

The Calendly link appears only after the visitor completes the required intake and consents to share it.

Other website platforms

Install SimpleBot without WordPress

  1. Open the bot and select Embed Bot.
  2. Under Connected domains, confirm the primary website is listed. Use Add another only for an additional website.
  3. Select the connected website whose installation code you need.
  4. Under Other website platforms, select Copy website code.
  5. Paste the code into the website’s site-wide custom-code area before the closing body tag.
  6. Publish the website change and test the live page.

Return to Embed Bot and select the connected website whenever you need the code again. Rotate its key only to revoke the existing installation; after rotating, replace the old website code.

WordPress

Install SimpleBot on WordPress

  1. Finish the bot setup and test it inside SimpleBot.
  2. Open Embed Bot early in the bot setup and download the unified SimpleBot for WordPress plugin.
  3. Upload and activate the plugin under WordPress → Plugins. The SimpleBot setup page opens automatically.
  4. Select Sign in and choose a bot. If the setup page did not open, select Start setup in the WordPress notice or open Settings → SimpleBot.
  5. Sign in to SimpleBot and choose the corresponding bot. Leave WordPress and WooCommerce capabilities selected, review the requested access, and approve the website. The website key, identity settings, and safe read-only capabilities are configured automatically.
  6. The plugin requests a cache purge after activation and connection. If the widget is missing or looks outdated, clear the WordPress cache plugin, host page cache, and CDN/network cache. On WP Engine, open WP Engine → Caching → Clear All Caches.
  7. Test the public page in a private browser window on desktop and mobile.

Each bot supports up to two connected domains. The HTML code under Embed Bot → Other website platforms is intended for non-WordPress installations. Custom capability code stays on the WordPress server.

Tools

Connect non-WordPress MCP capabilities

  1. Open the bot and select Advanced Settings.
  2. Select Connect server.
  3. Enter the server name and HTTPS Streamable HTTP URL.
  4. Enter authorization only in the protected dashboard field.
  5. Select Save and discover.
  6. Approve only the capabilities the bot should use.
  7. Choose Public data or Verified email required for each approved tool.

You can connect more than one external MCP server. Never paste credentials into chat. New server capabilities remain disabled until you refresh and approve them.

Human support

Configure human escalation

  1. Open the bot and select Human Support.
  2. Turn on Enable human escalation for this bot.
  3. Under Send escalated conversations to, enter the inbox monitored by the person or team responsible for follow-up.
  4. Adjust the visitor button label and select Save human escalation.
  5. Select Publish changes when the saved draft should become live.
  6. Test from the embedded website after sending at least one message.
  7. Complete the contact form, consent, and confirm the inbox receives the transcript.

The visitor must consent. SimpleBot reports success only after the email provider accepts the message.

Troubleshooting

Check the simple things first.

I cannot log in+

Select Login in the top-right corner, continue with Google or enter your email address, and complete the verification steps. After authentication, SimpleBot opens your Dashboard. If the button already says Dashboard, you are signed in.

My document is stuck+

Confirm the file is supported and under 50 MB. Wait several minutes. If it becomes failed, read the visible error and try a smaller, clean copy.

The answer is missing+

Confirm the source is ready and the answer exists as selectable text. Remove obsolete or conflicting sources, then test the question again.

The widget does not appear+

For WordPress, confirm the plugin is connected under Settings → SimpleBot. For another platform, confirm the website change is published and the script is present once. In both cases, confirm the exact site origin is active under Embed Bot and check whether the site blocks the script or iframe.

The website is not approved+

Compare the browser origin with the active Embed domain. Add the correct scheme and subdomain, then install the code generated for that domain.

A private question was refused+

The visitor must sign in through the host website and receive a session bound to the exact verified email. Typing an email into chat is not authentication.

Booking intake does not open+

Confirm Bookings is enabled, the HTTPS Calendly link is valid, at least one answerable question exists, and the bot was saved. Test with a clear new-booking request.

MCP tools are missing+

For a non-WordPress connection, open Advanced Settings, refresh the server, review the current catalog, approve the tool, and choose the correct identity policy. For WordPress and WooCommerce capabilities, open Embed Bot and use Reconnect in WordPress.

Changes will not save+

Check for a missing support inbox, incomplete identity settings, an invalid Calendly link, no intake questions, or choice questions without options.

A conversation starter is not useful+

Open Instructions and revise that Conversation Starter, or remove it with the trash button. Save and test again. Follow-up buttons are generated from the latest answer and never bypass authentication, consent, or tool policy.

The WordPress widget is missing or looks outdated after installation+

Open Settings → SimpleBot in WordPress and confirm the plugin is connected to the intended bot. The plugin requests an automatic cache purge, but some managed hosts and external CDNs require a manual purge. Clear the WordPress cache plugin, host page cache, and CDN/network cache. On WP Engine, open WP Engine → Caching → Clear All Caches. Then hard-refresh the page or test in a private browser window.

Platform admin is missing+

Platform administration is restricted to explicitly allowlisted SimpleBot operators. Confirm your Clerk user ID is in the server-side platform admin list, then sign out and back in. Never send a session token or secret in a support request.

Privacy boundary

Personal answers require the right person.

SimpleBot will not answer order, account, payment, subscription, or profile questions unless the website supplies an authenticated session for that exact verified email.

Current capabilities

Know what SimpleBot does today.

The current dashboard includes per-bot plans and usage, conversations, analytics, document knowledge, booking intake with Calendly, human escalation, approved MCP capabilities, and a unified WordPress plugin with customer identity and common WordPress and WooCommerce tools. WooCommerce bots can show product cards with images, names, prices, availability, and a View product link. Shoppers add items on the WooCommerce product page; SimpleBot can display their current cart with View cart and Checkout links. New or changed tools require owner approval, and private capabilities require the matching signed-in customer or administrator access.

Need more help?

Contact the SimpleBot team.

Email support@entheo.ai or use this form for account help, privacy requests, or security concerns. Include the affected bot name or ID and a short description, but never send passwords, API keys, MCP credentials, identity tokens, or private documents.