Use these guides to create, train, test, and install your bot. Each direction matches the controls in the current SimpleBot dashboard.
Hi! I’m SimpleBot. I can explain how the platform works, help you choose a plan, or walk you through setup.
Start with one job, a small set of trustworthy documents, and the questions real visitors already ask.
Open the dashboard, select New bot, add a name and description, then select Create bot.
Open the bot, select Knowledge, choose Add files, and wait for every source to show ready.
Select Instructions, set the system prompt, welcome message, and reply buttons, then select Save instructions.
Select Test Bot and try common, unsupported, and sensitive questions before launch.
Select Embed, copy the one-time code created for the primary website, and add it to the site.
A failed source is not available to the bot. Read the displayed error and try a smaller, clean copy.
Keep changing business facts in uploaded sources. Reply buttons should offer clear, relevant next questions and never imply an action the bot cannot complete.
SimpleBot can show up to three server-approved reply buttons after an answer. Booking and human-support buttons stay separate because they open validated workflows.
The Calendly link appears only after the visitor completes the required intake and consents to share it.
If the code is lost, rotate the domain key and replace the old script with the newly generated one.
A native WordPress plugin is planned but is not required. Some managed WordPress plans restrict custom scripts or reserve them for administrators.
Never paste credentials into chat. New server capabilities remain disabled until you refresh and approve them.
The visitor must consent. SimpleBot reports success only after the email provider accepts the message.
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.
Confirm the source is ready and the answer exists as selectable text. Remove obsolete or conflicting sources, then test the question again.
Confirm the site change is published, the script is present once, and the exact site origin is active under Embed. Check whether the site blocks the script or iframe.
Compare the browser origin with the active Embed domain. Add the correct scheme and subdomain, then install the code generated for that domain.
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.
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.
Open Tools, select Refresh, review the current catalog, approve the tool, and choose the correct identity policy. New tools are never approved automatically.
Check for a missing support inbox, incomplete identity settings, an invalid Calendly link, no intake questions, or choice questions without options.
Open Instructions and revise that Reply button CTA in its separate field, or remove it with the trash button. Save and test again. Buttons are suggestions; they do not bypass authentication, consent, or tool policy.
Confirm the live WordPress origin is approved, the script was published once, and your role or host permits custom JavaScript. Clear page, host, and CDN caches, then test in a private browser window.
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.
SimpleBot will not answer order, account, payment, subscription, or profile questions unless the website supplies an authenticated session for that exact verified email.
Paid checkout, finalized plans, owner-facing analytics, webpage ingestion, conversation export, native calendar booking, and confirmed write-capable MCP actions are not available in the current customer dashboard. Restricted platform observability is available through Langfuse.
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.