AddMyBot.

AddMyBot setup guide

How to add an AI chatbot to your website with AddMyBot

Prepare knowledge, approve sources, allow your website origin and install the AddMyBot widget. Check the live site and troubleshoot common setup problems.

Updated · Examples are illustrative; no customer information is used.

What you need before installing

AddMyBot is a website AI customer support chatbot that retrieves information from your business knowledge. Installation needs an AddMyBot account, an agent, current indexed sources and permission to add a script to your website. You do not need to put a server API key in the page.

Start privately. Uploading a document or copying the widget script does not approve its contents for visitors. Publishing is a separate decision that can disclose selected source text, names and webpage citations.

1. Prepare knowledge and test privately

  1. Create an agent.

    In your workspace Overview, create an agent if you do not already have one. Each owner has one business and one agent.

  2. Add useful information in Knowledge.

    Use Add manual text for FAQs, upload a supported document or import selected text from one public webpage. Review the extracted text and index the current revision.

  3. Check a known question in Playground.

    Wait for Indexed for internal retrieval, then test a question whose answer is present. Read the answer and cited source before allowing visitors to use it.

2. Allow the exact website origin and approve sources

Open Website in the workspace. Under Allowed website origins, enter the exact origin on which the widget will run: scheme, hostname and optional port, without a path or trailing slash. HTTPS is required except for explicit HTTP localhost testing. You can configure up to five origins.

Select only the current indexed sources you intend visitors to use. Read the disclosure acknowledgement, confirm your approval and enable public website access only when ready. Save publication settings. Changes to publication settings can invalidate existing visitor sessions; reload the website afterward.

  • https://shop.example.com is an illustrative origin. It does not allow https://www.shop.example.com or http://shop.example.com.
  • https://shop.example.com/help is a page URL, not an origin. Wildcards are not supported.
  • Editing source text requires fresh indexing and approval. A private Playground answer does not prove that the same source is published.
  • Origin restrictions constrain browser embedding; they do not prove domain ownership or prevent a non-browser client from forging headers.

3. Copy the installation snippet into your website

Use Copy snippet in Website, then place that exact script before the closing body tag in the pages where chat should appear. If your website builder provides a custom-code or footer-script area, use it only if your plan and site permissions support script execution. Preview modes and published pages can behave differently.

This is an illustrative example, not a working installation. Replace YOUR_PUBLICATION_ID with the value copied from your own workspace. The publication identifier is not a server API key. Never paste an API key or a private signing secret into HTML.

<script async src="https://addmybot.com/widget.js"
  data-publication="YOUR_PUBLICATION_ID"></script>

4. Verify the published website

Publish your website changes, open the actual allowed HTTPS origin and reload. Confirm the launcher and agent greeting appear. If you have approved a live test and have remaining capacity, ask one non-sensitive known question and review its answer and citation. Do not repeatedly send questions just to test the script.

A successful localhost test is useful installation evidence, but it does not establish a working live website installation. Playground testing does not create customer conversation records. Accepted website questions can create retained conversations; consented follow-up requests can appear in Leads. Saving a lead sends no email automatically.

Troubleshoot an absent widget or unavailable answer

  • No launcher: check that the published page contains the copied script once, that your builder executes it, and that the browser has not blocked it. Ask your site administrator to review any script/frame policy rather than disabling security protections.
  • Origin rejected: compare the address bar with the saved exact origin, including www, HTTPS and port. Do not broadly add origins to work around a mismatch.
  • No approved knowledge: check the selected source revision in Website. Processed text still needs indexing, and indexing alone is not publication approval.
  • AI unavailable: check Overview readiness and remaining allowance. Current reservations permit roughly four generated answers per owner per day across Playground, widget and API; shared/provider limits can reduce availability.
  • Uncertain delivery: use the offered retry with the same request and unchanged question. A new request is not a recovery shortcut and may consume additional allowance.

Know the current product boundaries

This guide covers the website widget. AddMyBot does not provide WhatsApp, voice, CRM integration, whole-site crawling or automatic knowledge refresh. Live human handoff is not enabled on this installation. AI answers may be wrong even when cited; keep your business contact route available for questions that need a person.

Monthly accepted requests are not a promise of generated answers. Accepted fallbacks and failures can count. Paid purchase is currently unavailable; a larger proposed monthly plan does not increase the daily AI ceiling.