Global and conditional chatbots

Injecting the Aimogen Pro chatbot site-wide, and the full set of URL, content, role, language, device, browser, IP and time conditions.

AI Chatbot › Global Chatbots injects a floating chatbot across the site, with a large set of conditions deciding where it appears.

Aimogen Update: Inject Chatbot to the Entire Site Front End or Back EndEnabling global injection.Watch on YouTube

This tutorial was recorded before Aiomatic was renamed to Aimogen Pro. Some labels or interface elements may differ slightly from the current version.

Multiple Global Chatbots On Different Post CategoriesUsing the conditions to show different bots in different places.Watch on YouTube

This tutorial was recorded before Aiomatic was renamed to Aimogen Pro. Some labels or interface elements may differ slightly from the current version.

Enabling#

Setting	Controls
`Inject Chatbot Globally To Your Site`	Master switch. Can target the front end, the admin, or both
`Chatbot Location`	`bottom-right`, `bottom-left`, `top-right`, `top-left`
`Chatbot Width`	Default 460px
`Chatbot Open Icon` and `Chatbot Open Icon Width`	The launcher bubble
`Custom Chatbot Shortcode To Be Injected Globally`	Inject a specific configured shortcode instead of the default bot

That last setting is how you run several different global chatbots: point each condition set at a different shortcode with different persona and settings.

Automatic opening#

Four triggers can open the chat without the visitor clicking. Each has its own message, URL restriction and once-per-visitor flag.

Trigger	Settings
On page load	`page_load_chat`, `page_load_chat_delay`, `page_load_chat_once`, `page_load_chat_urls`, `page_load_chat_message`
On exit intent	`page_exit_chat`, `page_exit_chat_once`, `page_exit_chat_urls`, `page_exit_chat_message`
On scroll depth	`page_scroll_chat`, `page_scroll_chat_percent`, `page_scroll_chat_once`, `page_scroll_chat_urls`, `page_scroll_chat_message`
On inactivity	`page_inactive_chat`, `page_inactive_chat_time`, `page_inactive_chat_once`, `page_inactive_chat_urls`, `page_inactive_chat_message`

chatbot_invite_message sets an invitation message shown on the launcher.

Exit intent on a pricing page, opening once, is defensible. Immediate auto-open on every page is not.

Conditions#

Every condition comes as a pair — a blocklist and an allowlist. Set one or the other, not both.

URLs and content#

Setting	Effect
`Do Not Show The Chatbot On These URLs`	URL blocklist
`Show The Chatbot Only On These URLs`	URL allowlist
`Do Not Show The Chatbot On This WordPress Content`	By post, page or post type
`Show The Chatbot Only On This WordPress Content`	The allowlist equivalent

Audience#

Setting	Effect
`Do Not Show The Chatbot For These User Roles` / `Show ... Only For These User Roles`	By WordPress role
`Do Not Show The Chatbot For These Languages` / `Show ... Only For These Languages`	By site locale
`Do Not Show The Chatbot For These IP Addresses` / `Show ... Only For These IP Addresses`	By IP

Excluding administrator is a common first move — you do not need the bubble while you work.

Device and client#

Setting	Effect
`Do Not Show The Chatbot For These Devices` / `Show ... Only For These Devices`	Desktop, tablet, mobile
`Do Not Show The Chatbot For These Operating Systems` / `Show ... Only ...`	By OS
`Do Not Show The Chatbot For These Browsers` / `Show ... Only ...`	By browser

Detection uses the bundled Mobile Detect library on the user agent, which is a heuristic. Do not rely on it for anything security-relevant.

Time#

Setting	Effect
`Show The Chatbot Between Specific Hours Each Day`	A daily time window
`Days When To Always Show The Chatbot`	Force on for specific weekdays
`Days When To Never Show The Chatbot`	Force off

Useful when the chatbot escalates to a human team: show it during staffed hours, hide it otherwise.

Extensions in the global chatbot#

Enable Chatbot Extensions In The Globally Injected Chatbot controls whether tool calling is active for the global bot.

Several global chatbots#

The pattern is:

Configure a persona per audience.
Build a shortcode for each, with its persona and settings.
Put one in Custom Chatbot Shortcode To Be Injected Globally and set the conditions for it.

Because conditions are global rather than per-shortcode, running genuinely different bots on different sections usually means placing shortcodes in templates rather than relying on global injection alone.

Still stuck? Open a support ticket and include the diagnostics from Aimogen Pro › System & Logs › System Info.