WordPress Chatbot Builder

WordPress powers roughly 43% of all websites on the internet - from personal blogs to enterprise publications - and WooCommerce is the most widely used e-commerce plugin in the WordPress ecosystem. If you run a WordPress site, your visitors already expect instant answers: to product questions, to shipping policies, to "where do I find X" navigation help. A chatbot that answers in seconds is the difference between a captured lead and a closed tab.

The official Conferbot WordPress plugin puts an AI-powered chat widget on your site with a single field of configuration: the Chatbot ID. No API keys, no theme edits, no shortcodes scattered across templates. Install the plugin, paste the ID in Settings > Conferbot, save - the chat bubble is live on your site.

What makes the WordPress integration stand out from a generic HTML embed is context. The plugin automatically identifies logged-in WordPress users (name and email) and, when WooCommerce is active, passes live cart data - cart total, item count, and store currency - to the bot. Your AI assistant and human agents see who they are talking to and what is in the shopper's cart, without you writing a line of code.

The bot itself is built in Conferbot's no-code visual builder and powered by the same AI engine that drives every Conferbot channel. Build the flow once and deploy it to WordPress, your website widget, WhatsApp, and beyond.

New to WordPress chatbots? Our WordPress chatbot plugin guide covers strategy and use cases in depth, and the WooCommerce + WordPress AI chatbot guide focuses on store owners. Running a different platform too? Conferbot ships the same one-credential integration for Shopify, BigCommerce, Wix, Joomla, Magento, OpenCart, Ecwid, and PrestaShop.

Source code & documentation: conferbot-wordpress on GitHub | Developer guide

The Conferbot WordPress plugin is a thin, careful wrapper around the official Conferbot web embed. It hooks WordPress's wp_head action and injects the standard loader into the head of your site's frontend pages:

<script src="https://cdn.conferbot.com/dist/v1/widget.min.js" async></script>

followed by a call to window.ConferbotWidget("YOUR_BOT_ID", "live_chat", options) where options carries the visitor identity and site context (detailed in the context section below). That is the entire contract: the same snippet you would paste by hand on any website, but generated for you with live WordPress and WooCommerce data on every page load.

One credential, nothing else

The Chatbot ID is the only credential the plugin needs. There is no API key, no workspace ID, no webhook secret. The widget resolves your bot's configuration, appearance, and conversation flows server-side from the ID at runtime. This has two practical consequences:

• Nothing sensitive is stored on your server. The Chatbot ID is public by design - it appears in your page source just like any chat vendor's site ID
• Changes are instant. Edit your bot's flows, colors, or greeting in the Conferbot dashboard and every WordPress page picks up the change on the next load - no plugin updates, no cache-busting rituals for the bot content itself

Try it before you sign up

The settings page includes a one-click demo bot button that fills in the public demo bot ID (691c970890527a0468f9b2c9). It works without a Conferbot account, so you can see the widget live on your actual site - your theme, your pages - before creating anything. When you are ready, build your own bot at app.conferbot.com and swap in its ID.

Admin pages are never touched

The loader is injected on the site frontend only. Your wp-admin, editors, and REST API responses are untouched, and the plugin adds zero queries to admin page loads.

There are two ways to install Conferbot on a WordPress site: the official plugin (recommended) or a direct embed of the widget snippet. Both take minutes; the plugin does more for you.

Option A: The Conferbot plugin (recommended)

One-click setup that automatically passes logged-in user identity and WooCommerce cart context to the bot, plus per-page visibility controls. Requirements: WordPress 5.8+ (tested up to 6.5) and PHP 7.2+.

1. In wp-admin, go to Plugins > Add New > Upload Plugin, upload the Conferbot plugin zip, click Install Now, then Activate
2. Get your Chatbot ID: in the Conferbot dashboard, open your bot, click Share, then Copy Bot ID (a 24-character hex string). No bot yet? Use the demo bot in the next step, or publish a flow from the template library
3. Go to Settings > Conferbot, paste your Chatbot ID - or click Try our demo bot to use the public demo bot without an account - turn the chat on, and click Save
4. Verify: open your site's frontend - the chat bubble appears. Log in as a WordPress user and start a chat; the conversation in your Conferbot inbox shows the user's name, email, and site context

Option B: Direct embed (no plugin)

The pre-plugin method still works everywhere: paste the canonical widget snippet into your theme's custom-code slot.

<script src="https://cdn.conferbot.com/dist/v1/widget.min.js" async></script>
<script>window.ConferbotWidget("YOUR_BOT_ID", "live_chat");</script>

Where to paste it: Appearance > Theme File Editor, in footer.php just before </body> - or use any header/footer-code plugin if you prefer not to edit theme files.

The trade-off: a direct embed does not pass the logged-in user or WooCommerce cart context automatically - that is exactly what the plugin adds - unless you hand-write the options argument yourself. It also lacks per-page controls and gets overwritten by theme updates when pasted into theme files.

Troubleshooting

• Widget not appearing? Confirm the bot is published in the dashboard and the Chatbot ID is the 24-character hex value. Testing with the demo bot isolates whether the problem is plugin setup or bot configuration
• Caching plugins: if you run a page cache (WP Rocket, W3 Total Cache, LiteSpeed), purge it after enabling the plugin so cached pages pick up the loader
• Page-level gating: if the widget shows on some pages but not others, check the per-page visibility settings described in the next section

The full merchant walkthrough with screenshots lives in the developer portal WordPress guide.

The settings page is deliberately a two-step form: paste the Chatbot ID, flip the switch. Everything else is either automatic or optional.

Chatbot ID field - paste anything

The ID field is forgiving. You can paste any of the following and the plugin extracts the 24-character ID automatically on save:

• The bare ID (24-character hex, from Share > Copy Bot ID)
• The full embed snippet copied from the dashboard's "Embed into website" screen
• A dashboard URL for the bot

Whitespace, uppercase hex, and surrounding markup are all normalized. Garbage input is rejected with a clear error instead of silently saving a broken ID.

Embed types

Choose how the chat appears on your site:

• Floating chat bubble (live_chat, default) - the familiar corner launcher that expands into a chat panel
• Popup window (popup_chat) - opens the conversation in a popup, useful for focused support flows

Per-page visibility

Unlike most platform integrations, the WordPress plugin supports per-page controls natively. Choose exactly where the chat appears: home, posts, pages, and - when WooCommerce is active - shop, cart, checkout, and account pages. The plugin resolves the current page type using WordPress conditional tags with WooCommerce-aware priority rules, so a product page is treated as "product", not just "page".

Common patterns:

• Commerce focus: show chat only on shop, product, cart, and checkout pages where buying questions happen
• Content focus: show chat on posts to convert readers, hide it on checkout to remove distraction
• Everything on: the default - the bot decides when to engage via dashboard-configured triggers

Advanced: widget script URL

An advanced field lets you point the loader at a different script URL - useful for staging environments or self-hosted widget builds. Leave it at the Conferbot CDN default otherwise. The plugin sanitizes this field and refuses javascript: and other non-HTTP schemes.

Note what is not here: colors, position, greetings, language, triggers. Those live in the Conferbot dashboard (see the theming section) so your bot looks and behaves identically across every channel you deploy it on.

Context is where the plugin earns its keep over a hand-pasted embed. On every page load, the plugin builds the options object for window.ConferbotWidget from live WordPress state:

Logged-in user identity

When a visitor is logged in to WordPress, the plugin passes a user object with:

• id - a stable identifier derived from the WordPress user ID
• name - the user's display name
• email - the user's email address

For guests, the user object is simply omitted - no placeholder data, no tracking hacks. In the Conferbot inbox, logged-in visitors appear by name with their email attached, so both the AI and your human agents can greet returning customers personally and skip the "what's your email?" dance.

Site context

Every page load includes customData with platform: "wordpress", the site name, site URL, and site language. Multilingual sites benefit immediately: the bot knows the visitor is on your German site versus your English one and can be flow-routed accordingly.

WooCommerce cart context

When WooCommerce is active, the plugin adds live commerce data to customData:

Field	Meaning
storeCurrency	The store's active currency code
cartTotal	The visitor's current cart total
cartItemCount	Number of items in the visitor's cart

This is passive but powerful. An agent answering "is this in stock in blue?" sees the shopper already has $180 in the cart - a signal to prioritize. Your AI flows can branch on the same data: a visitor with a non-empty cart lingering on the cart page is a candidate for a proactive assist; a first-time guest reading the blog gets a gentler lead-capture flow.

Privacy posture

The plugin passes exactly the fields above - nothing else. No browsing history, no order history, no admin data. All context travels over TLS to Conferbot's servers as part of the chat session, and the plugin stores only its own settings (bot ID and display options) in your database. See our data security and privacy guide for the full picture.

WooCommerce is the most widely used way to sell on WordPress, and it is where the Conferbot plugin's context features pay off most directly. The plugin detects WooCommerce automatically - no separate add-on, no extra configuration.

WooCommerce-aware page types

With WooCommerce active, the plugin's per-page visibility system gains commerce-specific page types resolved with priority rules: shop (the main catalog), product pages, cart, checkout, and account pages. A product page is matched as a product page even though WooCommerce implements it as a post type, and the checkout endpoint is distinguished from ordinary pages. That lets you run genuinely different chat strategies per stage of the funnel.

Funnel-stage playbook

• Shop and category pages: the discovery stage. A product-finder flow ("What are you shopping for today?") shortens the path from browsing to product page
• Product pages: the objection stage. Sizing, materials, shipping times, returns - the questions that stall a purchase. AI answers drawn from your product content resolve them in seconds
• Cart page: the hesitation stage. The bot sees cartTotal and cartItemCount, so a dashboard-configured proactive prompt can offer help precisely when a shopper with a full cart stalls
• Checkout: many stores hide the widget here to remove distraction - one checkbox in the plugin's visibility settings. Others keep a minimal support presence for payment questions. Both are one-click choices
• Account pages: logged-in customers get personalized support - the agent already sees their name and email

Identified customers, better support

WooCommerce customers are WordPress users, so the moment a customer logs in, every chat they start is attributed to their name and email in your Conferbot inbox. Support conversations stop being anonymous: "Where is my order?" comes from a known customer, and your agent can act immediately rather than authenticating identity first.

What this version does not do

Honesty matters: the plugin passes cart context to the bot; it does not push outbound webhooks (order status changes, abandoned-cart events, product updates) from WooCommerce into Conferbot. Server-side commerce webhooks are on the roadmap but are not part of this version. For deeper WooCommerce chatbot strategy, read the WooCommerce chatbot guide and AI chatbot for WooCommerce and WordPress.

WordPress spans everything from a hobby blog to a headless enterprise CMS, and chat earns its place differently across that spectrum. The highest-return patterns:

1. WooCommerce sales assistant

Answer pre-sale questions - sizing, shipping, stock, returns - the moment they arise on product pages. Pre-sale questions are purchase-intent signals; unanswered, they become abandoned sessions. An AI assistant that responds in seconds captures sales your FAQ page loses. Start from an e-commerce flow in the template library.

2. Lead generation on content

Blogs are WordPress's superpower. A reader deep in a how-to post is a warm lead; a conversational prompt ("Want the checklist for this? I can send it over") converts far better than a static sidebar form. Captured leads flow to your CRM through Conferbot's integrations.

3. Support deflection

Feed the bot your documentation and policies and let AI answer the repetitive 80% - "how do I reset my password", "what is your refund policy" - while human handover catches the rest. Fewer tickets, faster answers, same team.

4. Membership and LMS sites

Because the plugin identifies logged-in users, membership sites (MemberPress, LearnDash, WooCommerce Memberships) get personalized support for free: members are greeted by name and agents see exactly who is asking. Course questions, billing issues, and content navigation all route through one chat.

5. Appointment and inquiry booking

Service businesses on WordPress - clinics, agencies, consultants - can let the bot qualify inquiries and book calls conversationally instead of losing visitors to a buried contact form.

6. Multilingual audiences

The plugin passes the site language, so WPML/Polylang-style multilingual sites can route visitors to language-appropriate flows, and the widget UI itself is localized from the dashboard.

7. Feedback and research

Conversational NPS and feedback surveys get completion rates static forms rarely match - useful after purchases, course completions, or content milestones.

For a broader tour of chat-driven revenue tactics, see chatbots for e-commerce sales.

A deliberate design decision shapes the whole integration: the plugin does not duplicate widget settings. Appearance and behavior are configured once in the Conferbot dashboard under Customize and delivered to the widget at runtime. The plugin stays a thin loader; your brand configuration lives in one place and applies to every channel.

What you control from the dashboard

• Position - left or right corner, offsets, mobile behavior
• Colors and theme - brand colors for the launcher, header, and message bubbles; light and dark themes
• Avatar and branding - bot name, avatar image, welcome header
• Language - localized widget UI strings
• Auto-open and load delay - open the chat automatically after a delay, or stay minimized until clicked
• Proactive prompts - greeting messages that slide out based on time on page or visitor behavior
• Disabled URLs - suppress the widget on specific URLs, complementing the plugin's page-type controls with URL-level precision

Why dashboard-driven beats plugin-driven

Chat vendors that stuff appearance settings into their WordPress plugin create a synchronization problem: the widget on your site drifts from the widget on your other channels, and every tweak requires a WordPress login. With Conferbot, a marketer can restyle the widget, rewrite the greeting, and adjust proactive prompts without touching WordPress at all - and the change is live on the next page load. If you later add the Shopify app for a second storefront or deploy the same bot to any other website, they match automatically.

Theme compatibility

The widget renders inside its own isolated container using Web Components and Shadow DOM, so your theme's CSS cannot break the widget and the widget's styles cannot leak into your theme. It works with block themes, classic themes, and page builders (Elementor, Divi, Beaver Builder) alike, because it never modifies your theme's markup - it is appended by the loader script at runtime.

For flow-level personalization - different greetings per page type, cart-aware prompts - combine dashboard triggers with the context the plugin passes (see the context section above).

The widget on your WordPress site is the front door; what answers behind it is the full Conferbot platform.

Visual flow builder

Design conversation flows in the drag-and-drop builder: welcome messages, button choices, forms, conditions, and actions. Flows handle the structured work - lead qualification, appointment booking, order-status triage - with zero code. The template library includes ready-made flows for e-commerce, lead generation, and support that you can publish in minutes.

AI answers from your content

Connect Conferbot's AI engine and the bot answers free-form questions from your knowledge: docs, policies, product details. Instead of forcing visitors down rigid button paths, the AI handles the long tail of phrasing ("do u ship 2 canada??") and responds naturally, falling back to your flows or a human when confidence is low.

Human handover with WordPress context

When a conversation needs a person - complex complaint, big-ticket sale, anything the bot should not guess at - it hands over to your team in the shared live chat inbox. Here the plugin's context work compounds:

• The agent sees the visitor's name and email if they are logged in to WordPress - no identity verification round-trip
• On WooCommerce stores, the agent sees the cart total and item count - a $400 cart gets a different urgency than an empty one
• The site name and URL distinguish conversations when you run multiple sites into one workspace

Beyond the chat window

Conversations, leads, and outcomes feed Conferbot analytics - completion rates, busiest pages, handover frequency - so you can iterate on flows with data. Captured leads sync to your CRM and tools via 15+ integrations. And since the same bot runs on every channel, a customer who starts on your WordPress site and follows up on WhatsApp is talking to the same brain.

Not sure whether you need AI flows, live chat, or both? Chatbot vs live chat: when to use each breaks down the trade-offs.

WordPress site owners are rightly paranoid about third-party scripts - Core Web Vitals are a ranking factor, and one bloated chat widget can drag down LCP across the whole site. The Conferbot plugin is engineered around that concern.

Async, non-blocking loader

The widget script is injected with the async attribute and served from Conferbot's CDN (cdn.conferbot.com). The browser downloads and executes it off the critical rendering path: your content paints first, the chat bubble mounts after. There is no synchronous script, no document.write, no layout work before first paint.

No render blocking, no layout shift

The widget mounts into its own container appended to the page - it does not reflow your content, so it contributes no Cumulative Layout Shift to your page body. The heavy chat UI is loaded only when relevant; the initial footprint is the small loader.

Zero theme and template modifications

The plugin adds one hook to wp_head. It does not edit theme files, does not register front-end assets of its own, adds no database queries on cached pages beyond option reads, and does not touch your templates. Deactivate it and every trace is gone from your markup; delete it and uninstall.php removes its options from the database.

SEO considerations

• Content integrity: the widget renders client-side after load - your server-rendered HTML, the thing crawlers index, is unchanged
• No cloaking, no injected links: the plugin adds a script tag, nothing else - no footer links, no hidden content
• Caching friendly: the injected snippet is deterministic per page state, so full-page caches (WP Rocket, LiteSpeed, Varnish) cache it safely. Purge once after install
• Indirect SEO upside: visitors who get answers stay longer and bounce less - engagement signals search engines reward. A chatbot also captures the questions visitors actually ask, which is a content-ideas goldmine

Comparing embed approaches for a custom-built site instead? See how to add a chatbot to any website and the website widget page.

A plugin that injects JavaScript into every page of your site deserves scrutiny. The Conferbot WordPress plugin is open source (GPLv2 or later, per WordPress.org requirements) and built to be audited - the full source is on GitHub.

Tested where it counts

The plugin ships with a PHPUnit suite - 23 tests, 66 assertions, green on PHP 7.4 and 8.2 - covering the code paths that matter for safety:

• Bot ID extraction: bare IDs, full embed snippets, dashboard URLs, and garbage input are all parsed or rejected predictably
• Settings sanitization: invalid embed types are rejected; the advanced script URL field refuses javascript: and other non-HTTP schemes; enabling the widget without a valid ID is refused
• Script-injection safety: the user context is inlined as script-safe JSON - a user display name containing a closing script tag cannot break out of the snippet and inject markup
• Visibility logic: WooCommerce-aware page-type resolution and per-page gating are unit tested, so "hide on checkout" means hidden on checkout

Beyond unit tests, the plugin is verified end to end in a dockerized WordPress 6.5: activation, loader render with correct context, logged-in identity, per-page gating, and the real CDN widget mounting and chatting.

WordPress-native hardening

• The settings page checks capabilities (admin-only) and uses nonces against CSRF
• All options pass through a sanitize layer before persistence
• The plugin requests no extra roles, creates no tables, and schedules no cron jobs
• Clean uninstall: deleting the plugin removes its options via uninstall.php - no orphaned rows

Data boundaries

Conversations happen between the visitor's browser and Conferbot's servers over TLS; chat transcripts never pass through or rest on your WordPress server. The plugin stores only its own settings. For Conferbot's platform-side posture - encryption, retention, GDPR tooling - see the security and privacy best practices guide.

The WordPress plugin directory is crowded with chat options. They cluster into a few categories, each with a real trade-off profile - here is an honest comparison by category rather than invented claims about specific competitors:

Category comparison

Capability	Conferbot plugin	Generic live chat plugins	Manual embed snippet	Contact form plugins
Setup effort	One field (Chatbot ID)	Account + plugin settings	Theme edit or code-snippet plugin	Form builder setup
AI answers	Built in	Often a paid add-on or absent	Depends on vendor	None (async replies)
Live agent handover	Shared inbox included	Usually included	Depends on vendor	Email only
Logged-in user identity	Automatic	Varies, often manual JS	Manual coding required	Manual fields
WooCommerce cart context	Automatic	Rare	Manual coding required	None
Per-page visibility	Built in, Woo-aware	Sometimes	Manual conditionals	Per-page shortcodes
Omnichannel (same bot on WhatsApp, etc.)	Yes	Rarely	Depends on vendor	No
Response time for visitor	Instant (AI) or live	Live hours only, or bot add-on	Depends on vendor	Hours to days

The honest trade-offs

• If you only want humans answering during office hours, a simple live chat plugin is fine - but you inherit its offline dead zone. Conferbot covers nights and weekends with AI and flows
• If you are comfortable editing code, the manual embed of any vendor works - the plugin's value is the automatic user/cart context, per-page gating, and sanitized settings you would otherwise hand-build
• If you just need a message inbox, a contact form is simpler - but forms convert a fraction of what conversations do, as we cover in chatbot vs live chat vs form

Pricing: the plugin itself is free and works with every Conferbot plan, including the free plan. Paid plans start at $19/mo when you outgrow the free tier - there is no separate per-plugin or per-channel charge.

You can have a chatbot on your WordPress site before your coffee cools. The path:

1. Try the demo bot first (optional, no account). Install the plugin, click Try our demo bot in Settings > Conferbot, save, and watch the widget run live on your own theme with the public demo bot (691c970890527a0468f9b2c9)
2. Create your free account at app.conferbot.com - the free plan includes the visual builder, AI, and the live chat inbox; no credit card required
3. Build or pick a bot. Start from scratch in the no-code builder or publish a flow from the template library - the WooCommerce and lead-generation templates map directly onto WordPress use cases
4. Publish and connect. Copy the Bot ID (Share > Copy Bot ID), paste it into Settings > Conferbot, choose your page visibility, save
5. Iterate with data. Watch conversations in the inbox, review analytics, and tune your flows and proactive prompts from the dashboard - no further WordPress changes needed

Resources

• Plugin source on GitHub (GPLv2, PHPUnit-tested)
• Developer portal: WordPress integration guide
• WordPress chatbot plugin guide - strategy and examples
• WooCommerce chatbot guide - store-specific playbook
• Pricing - free plan available, paid from $19/mo

Selling on more than one platform? The same bot deploys to Shopify, BigCommerce, Magento, PrestaShop, OpenCart, Ecwid, Wix, and Joomla with the same one-credential setup.