One script tag, three places you can put it. It trains on your own pages, posts and PDFs, answers in 95+ languages, and uninstalls by deleting a line.
<script src="https://customerbot.co/script.js" data-bot-id="YOUR_BOT_ID"></script>They all load the same widget. The difference is where the line lives and what survives your next theme update.
Best for most sites
If you already run something like a header-and-footer code plugin, paste the tag into the footer field and save. It survives theme updates and needs no code access at all.
Best for a child theme you control
Hooking wp_footer loads the widget site-wide with no plugin at all. Put it in a child theme so a parent-theme update does not wipe it.
add_action('wp_footer', function () {
?>
<script src="https://customerbot.co/script.js" data-bot-id="YOUR_BOT_ID"></script>
<?php
});Best for a single landing page
When you only want the assistant on the pricing page or one campaign landing page, drop the shortcode into a Shortcode block instead of loading it site-wide.
[customerbot bot-id="YOUR_BOT_ID"]
WordPress sites tend to have far more content than a support assistant needs. Being selective is the difference between sharp answers and vague ones.
Paste your domain and CustomerBot fetches the reachable URLs, shows you the list, and lets you pick which ones to train on. Bulk-train the whole set in one pass or start with ten that matter.
A ten-year blog archive is mostly noise for a support assistant. Train on the evergreen guides and skip the news posts — you can add more later once analytics tell you what people ask.
Price lists, spec sheets, terms. Uploaded, parsed and indexed alongside your pages, with text pulled out of image-heavy pages rather than skipped.
The answers you retype every week. Stored verbatim so the phrasing you have refined over years is what gets repeated.
In practice, four things account for nearly every “it is not working” on WordPress. All four have a one-line fix.
| Symptom | Almost always because | Fix |
|---|---|---|
| The bubble does not appear | A caching or optimisation plugin is serving a page generated before the change. | Purge the cache in the plugin and in your host’s CDN, then hard-reload. Check the page source for the script tag before assuming anything else is wrong. |
| It appears on some pages only | The tag went into a template that not every page uses, or into a per-page shortcode. | Use the wp_footer hook or a footer script field instead — both apply to every page the theme renders. |
| It vanished after a theme update | The snippet was in the parent theme’s functions.php and was overwritten. | Move it into a child theme, or use a plugin field that lives in the database instead of a file. |
| A JS optimiser breaks it | Deferring, combining or lazy-loading third-party scripts can prevent the widget from initialising. | Add the CustomerBot script to the optimiser’s exclusion list. Most plugins have one, and this is exactly what it is for. |
Training is a deliberate action, not a live mirror of your site. When you publish or substantially rewrite something, re-train that URL from the training screen — the old passages are replaced and the assistant answers from the new text immediately. Make it part of your publishing checklist and it takes ten seconds.
No. The functions.php route needs nothing installed, and a header-and-footer plugin is only a convenience for sites where editing theme files is impractical. There is nothing to keep updated.
Yes. The tag renders through wp_footer, which every properly built theme calls — page builders included. If your builder has its own custom-code area, that works too.
It is a single small script loaded from a CDN at the end of the body, so it does not block rendering. If you run an aggressive optimisation plugin, exclude the script from combining and deferring rather than letting it be mangled.
It reads them the way a visitor does — by crawling the product pages you publish. For live stock or order status you would connect the relevant endpoint as an API tool, which the assistant calls during the conversation.
The assistant detects the language of each message and replies in it across 95+ languages, regardless of which translation plugin you run. You can train it on your primary-language content and it will still answer visitors in theirs.
Delete the line. There is no database table, no orphaned options and no uninstall routine — that is the practical advantage of a script tag over a plugin.
The free plan indexes a real WordPress site and gives you a working assistant to interrogate before you edit a single theme file.
Start free