BigCommerce Chatbot Builder

BigCommerce is a leading open SaaS e-commerce platform, popular with mid-market and enterprise merchants who want SaaS reliability without a walled garden - strong APIs, multi-storefront support, and a serious B2B feature set. Stores at that level face a support equation with bigger numbers on both sides: catalogs are larger, order values are higher, and a single stalled B2B buyer can represent more revenue than a hundred abandoned consumer carts.

The Conferbot BigCommerce app puts an AI-powered chat widget on your storefront with one merchant-facing setting: the Chatbot ID. Install the app, paste the ID, flip the switch - the widget loads on every storefront page via BigCommerce's Scripts API, with no theme edits and no Stencil template surgery.

The integration is built the way BigCommerce intends apps to be built: OAuth install, HS256-verified signed-payload load and uninstall callbacks, and a storefront Script registered with auto_uninstall: true so removing the app removes every trace from your storefront automatically. Each conversation arrives in Conferbot tagged with your store's context, so agents and flows always know which storefront they are serving.

Behind the widget sits the full Conferbot platform - the no-code visual builder, AI answers, and a shared live agent inbox. Build the bot once, run it on BigCommerce and every other channel you operate.

Useful reading: chatbots for Shopify Plus and BigCommerce enterprise covers the mid-market/enterprise angle, chatbots for e-commerce the fundamentals, and how to add a chatbot to any website the general technique. Running other platforms too? The same one-credential setup exists for Shopify, WordPress/WooCommerce, Magento, PrestaShop, OpenCart, Ecwid, Wix, and Joomla.

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

The Conferbot BigCommerce app is a small Node.js application that wraps the official Conferbot web embed in BigCommerce's app lifecycle. On every storefront page load, the Script it registers boots:

window.ConferbotWidget("YOUR_BOT_ID", "live_chat", options)

The widget itself is the standard Conferbot loader from https://cdn.conferbot.com/dist/v1/widget.min.js - the same widget that runs on any website - and options carries your store's context: platform: "bigcommerce" and your store hash, plus the logged-in customer when available.

One credential

The Chatbot ID is the only credential you handle. No API keys, no webhook secrets, no Stencil edits. The ID is public by design; the widget resolves your bot's flows, appearance, and behavior server-side from it at runtime. That means:

• Instant updates: change your bot's greeting, colors, or flows in the Conferbot dashboard and the storefront reflects it on the next page load - no app redeploy, no theme republish
• Minimal stored state: the app stores your bot ID and an enable switch; conversations run between the shopper's browser and Conferbot's servers over TLS

A no-op until you configure it

Until a bot ID is saved and the switch is on, the per-store loader returns an empty script. Installing the app changes nothing visible on your storefront until you deliberately enable it - and toggling it off removes the widget just as instantly, without uninstalling.

Try it before you sign up

The settings page offers a one-click demo bot (691c970890527a0468f9b2c9) that works without a Conferbot account. Watch the widget mount and chat on your real storefront - your theme, your catalog - before creating anything at app.conferbot.com.

There are two ways to install Conferbot on a BigCommerce store: the app (recommended) or a direct embed via Script Manager. Both take minutes; the app manages the script lifecycle for you.

Option A: The Conferbot app (recommended)

One-click install that registers the widget on all storefront pages and automatically passes store context (platform, store hash) to the bot - with clean auto-uninstall built in.

1. Install the Conferbot app from your store's control panel and approve the permission prompt (the only scope requested is Content: modify). The app exchanges the OAuth code for a token and registers a storefront Script via the Scripts API v3 - async, on all pages, with auto_uninstall: true
2. On the app's settings page, paste your Chatbot ID: in the Conferbot dashboard, open your bot, go to Share, and copy the Bot ID (a 24-character hex string). The bare ID, the full embed snippet, or a dashboard URL all work. No bot yet? Click the one-click demo bot, or publish a flow from the template library first
3. Flip the switch and Save
4. Verify: open your storefront - the chat bubble appears. Send a test message and see it arrive in your Conferbot inbox tagged with your store hash

Option B: Direct embed (no app)

The pre-app method still works: add the canonical widget snippet through BigCommerce's own script tooling.

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

Where to add it: Storefront > Script Manager - create a Script placed in the Footer, on all pages.

The trade-off: a direct embed does not pass the store hash or logged-in customer automatically - that is what the app adds - unless you hand-write the options argument yourself. You also manage the script's lifecycle manually instead of getting the app's auto-uninstall.

Self-hosting from source (optional, for developers)

The app is open source (MIT) and can run as your own private BigCommerce app:

1. Create a draft app in the BigCommerce Developer Portal: Auth callback APP_URL/auth, Load callback APP_URL/load, Uninstall callback APP_URL/uninstall, and request the Content: modify scope
2. Copy .env.example to .env with your client ID and secret; APP_URL must be public HTTPS
3. Run npm install then npm start, and install the draft app on your sandbox store from the dev portal

Full walkthrough in the developer portal BigCommerce guide and the GitHub README.

The settings page is a deliberate two-step form - paste the ID, flip the switch - because everything else belongs in the Conferbot dashboard, where it stays consistent across all your channels.

The Chatbot ID field accepts anything reasonable

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

The app extracts and validates the ID on save; malformed input is rejected with a clear error rather than silently persisting a broken configuration. Settings-save-with-full-snippet-paste is one of the cases in the automated test suite.

Embed types

• Floating chat bubble (live_chat, default) - the corner launcher shoppers expect
• Popup window (popup_chat) - opens the conversation in a dedicated popup

The master switch

The enable toggle controls whether the per-store loader emits the widget at all. Off means a no-op loader - handy for pausing chat during a flash sale or a support-team offsite without uninstalling anything.

Page-level control

The Scripts API injects on all storefront pages by design. To keep the widget off specific pages - checkout, landing pages, policy pages - use disabled URLs in the Conferbot dashboard under Customize; the widget checks the current URL at boot and stays hidden on matches. (Built-in page-type checkboxes are a feature of our server-rendered integrations like WordPress and PrestaShop, where the platform exposes page types to the plugin.)

The app itself is free

The Conferbot subscription is the product; the BigCommerce app carries no charge of its own. It works with every plan including the free plan, with paid plans from $19/mo and no per-channel fees.

BigCommerce apps have a well-defined lifecycle, and this integration implements all of it properly - worth understanding if you evaluate apps by their engineering.

Install

1. You install from the control panel. BigCommerce calls the app's auth callback with a code, scope, and context
2. Token exchange. The app exchanges the code at login.bigcommerce.com/oauth2/token for an access token bound to your store hash
3. Script registration. Using the Scripts API v3, the app registers its per-store loader - async, all pages, auto_uninstall: true. Registration is idempotent: reinstalling never leaves duplicate scripts (a tested case)

Every later visit: signed payloads

When you open the app from the control panel, BigCommerce sends a signed_payload_jwt - a JWT the app verifies with HS256 against its client secret before showing your settings. Expired, malformed, or wrong-secret payloads are rejected; all four verification cases are covered in the automated test suite. This is the mechanism that ensures only BigCommerce, on behalf of your store's authenticated staff, can open your app settings.

Uninstall: clean by construction

Uninstalling triggers the app's signed uninstall callback, which removes the store record. And because the storefront Script was registered with auto_uninstall: true, BigCommerce removes the script from your storefront automatically - no leftover third-party JavaScript quietly loading on a store that dropped the app months ago. If you have ever audited a storefront and found orphaned script tags from long-gone vendors, you know why this matters.

Runtime

On each storefront page load, BigCommerce injects the Script; the loader looks up your saved settings and, if enabled, boots the CDN widget with your bot ID, embed type, and store context. Loader output uses script-context-safe JSON encoding, so no stored value can escape the script context.

Tested end to end

The open-source repo ships 12 automated tests covering store-hash extraction and validation, all signed-payload JWT verification cases, install token exchange, Script registration idempotency, settings save with full-snippet paste, loader no-op before configuration, uninstall cleanup, and - in browser mode - a real headless-Chrome storefront asserting the CDN widget mounts.

Conversations from your BigCommerce storefront arrive in Conferbot with structured context attached, which is what elevates the app above a hand-pasted generic embed.

Store context

Field	Meaning
platform	Always "bigcommerce" - lets flows, routing, and reports identify the channel
storeHash	Your store's unique BigCommerce identifier - pins every conversation to the exact store it came from

Customer identity

When a logged-in customer can be identified on the storefront, a user object is attached so the conversation belongs to a known customer rather than an anonymous visitor. Guests come through without a user object - no synthetic identities, no fingerprinting.

What this enables

• Multi-store operators: several BigCommerce stores can share one Conferbot workspace, with every conversation labeled by store hash - agents always know which brand and catalog they are answering for
• Channel-aware flows: a flow can branch on platform - BigCommerce shoppers get commerce-first menus while your marketing-site visitors get lead-capture flows, from the same bot
• Segmented analytics: in Conferbot analytics, BigCommerce conversations are separable from your website, WhatsApp, and other channels - you can see which storefront generates the volume and the leads

What is not passed - a deliberately narrow boundary

The app does not read your catalog, orders, price lists, or customer database. Its only BigCommerce scope is Content: modify - the Scripts API permission. Cart-level detail (cart total, item count) is currently a feature of our server-rendered platform integrations like WooCommerce, Magento, and PrestaShop; outbound webhooks (order events, abandoned-cart triggers) are not part of this version. For a platform holding enterprise commerce data, a chat app that requests the minimum and is publicly auditable is the right default. See our security and privacy guide for Conferbot's platform-side posture.

BigCommerce skews mid-market, multi-channel, and increasingly B2B - and the chat patterns that pay off reflect that profile.

1. B2B buyer qualification

Wholesale and bulk inquiries are high-value and high-friction: minimum quantities, trade pricing, net terms, freight. A flow that qualifies the buyer - company, volume, timeline - and routes serious prospects to a salesperson with the transcript attached turns a contact-form black hole into a pipeline. On B2B stores this single flow can justify the entire deployment.

2. Pre-sale question capture

Spec compatibility, shipping to a region, warranty terms, stock at quantity - the questions that stall carts. AI answers drawn from your policies and product content resolve them in seconds, around the clock, in the shopper's session rather than in tomorrow's email queue.

3. Large-catalog navigation

Stores with tens of thousands of SKUs strain faceted search. A guided product-finder conversation ("What are you building? What is the operating temperature?") gets technical buyers to the right SKU faster than filter checkboxes - and feels like the counter service that built loyalty in the offline era.

4. Order support deflection

"Where is my order?" and returns eligibility dominate ticket volume. Flows triage them - collect the order number, set expectations, hand off genuine exceptions to a human - so your agents spend their day on judgment calls, not lookups.

5. Quote requests and lead capture

For configurable or high-ticket products, a conversational quote-request flow captures requirements plus contact details and syncs them to your CRM through Conferbot integrations - far better completion than a ten-field form.

6. Promotion and campaign engagement

Dashboard-configured proactive prompts greet visitors with the current campaign on relevant pages - a soft, dismissible nudge rather than an interstitial popup.

7. Multi-storefront consistency

Operators running several stores get one bot, one inbox, one analytics view - with each conversation tagged by store. Compare notes with the enterprise playbook in chatbots for Shopify Plus and BigCommerce enterprise and revenue tactics in chatbots for e-commerce.

The app owns nothing about the widget's appearance - by design. Every visual and behavioral setting lives in the Conferbot dashboard under Customize and is delivered to your storefront at runtime.

Dashboard-driven settings

• Position - corner, offsets, mobile placement
• Colors and theme - brand palette for launcher, header, and bubbles; light and dark themes
• Branding - bot name, avatar, welcome header
• Language - localized widget UI for international storefronts
• Auto-open and load delay - open automatically after a delay, or wait for the click
• Proactive prompts - behavior-triggered greetings for product and campaign pages
• Disabled URLs - suppress the widget on checkout or any URL pattern

Why this fits BigCommerce operations

Mid-market stores have separation of duties: an agency owns the Stencil theme, marketing owns campaigns, support owns the chat experience. Because the widget is injected by the Scripts API and styled from the dashboard, each team works without stepping on the others - marketing rewrites the proactive prompt for a promo weekend with no theme deploy and no developer ticket, and a theme redesign ships without anyone remembering to re-paste a chat snippet.

Isolation from your theme

The widget renders in its own isolated container built on Web Components and Shadow DOM: your theme's CSS cannot distort it, and its styles cannot leak into your category grids. It coexists with the usual storefront stack - analytics tags, review widgets, personalization scripts - because it never modifies DOM your theme owns.

One look across every channel

Configure appearance once and it applies wherever the bot runs - your BigCommerce storefront, your corporate site, a sister store on Shopify or Magento. One brand, one bot, one place to change it.

The widget is only the surface. Behind it, Conferbot layers automation and human support so volume goes to machines and judgment goes to people.

Flows for structure

The drag-and-drop builder handles deterministic work: B2B qualification questionnaires, order-status triage, returns eligibility, quote-request capture. Buttons, forms, and conditions keep buyers on rails where rails help, and the template library provides e-commerce starting points you can publish in minutes.

AI for the long tail

Buyers do not phrase questions like your documentation does. The AI engine, fed your policies and product knowledge, answers free-form questions naturally and falls back to flows or a human when confidence is low. It is the layer that covers nights, weekends, and the question nobody scripted.

Handover with context

When a conversation needs a person - a five-figure wholesale negotiation, an escalated complaint - it lands in the shared live chat inbox with the full transcript and its BigCommerce context: which store (by store hash), what was already asked and answered, and the customer identity when known. Your agent continues the conversation instead of restarting it.

One inbox across channels

BigCommerce conversations sit alongside your website, WhatsApp, and Messenger threads in a single inbox. A buyer who starts on the storefront and follows up on WhatsApp is one customer history, not two tickets in two tools.

Measure and iterate

Analytics show flow completion, drop-off points, handover rates, and recurring questions - the feedback loop for improving both the bot and the store content that generated the questions. Deciding how much to automate? Chatbot vs live chat: when to use each lays out the trade-offs honestly.

BigCommerce merchants invest heavily in storefront performance - Core Web Vitals affect both conversion and organic rankings, and enterprise SEO teams audit every third-party tag. This integration is engineered to pass that audit.

Async at every layer

The storefront Script is registered async via the Scripts API, and the widget it loads from cdn.conferbot.com is likewise non-blocking. Nothing sits on the critical rendering path: category grids, product images, and the add-to-cart button render at full speed, and the chat bubble mounts afterward.

No layout shift, no theme weight

The widget mounts into its own container appended to the page, contributing no Cumulative Layout Shift to your content. Because injection happens through the Scripts API rather than theme code, your Stencil theme's bundle carries zero extra weight - and theme redesigns can never orphan a forgotten chat snippet in an old template.

Clean lifecycle

Before configuration, the loader is a no-op returning an empty script - installing the app costs your storefront effectively nothing until you enable the widget. On uninstall, auto_uninstall: true means BigCommerce itself removes the Script: no orphaned third-party JavaScript, which is more than can be said for many manually pasted embeds.

SEO posture

• Indexed content untouched: the widget renders client-side after load; the HTML served to crawlers is exactly your theme's output
• No injected links, no hidden text: the app adds a script tag and nothing else
• Engagement upside: shoppers who get answers stay longer and bounce less, and chat transcripts are a running log of the questions your product pages fail to answer - free input for your content roadmap

General embed-performance techniques are covered in website chatbot widget setup; the platform-agnostic version of this integration is the Conferbot website widget.

The BigCommerce marketplace offers plenty of chat options, from lightweight live chat to full helpdesk suites. An honest comparison by category, without invented claims about specific competitors:

Category comparison

Capability	Conferbot app	Generic live chat apps	Helpdesk suites	Manual theme embed
Setup effort	One field (Chatbot ID)	Account + settings	Significant onboarding	Theme code edit
AI answers	Built in	Often a paid add-on tier	Usually on higher tiers	Depends on vendor
Visual flow builder	Included	Varies	Included, complex	Depends on vendor
Live agent inbox	Included	Usually included	Core feature	Depends on vendor
Store scope requested	Scripts only (Content: modify)	Varies	Broad (orders, customers)	None
Clean uninstall	auto_uninstall + signed callback	Varies	Usually	Manual removal per theme
Same bot on WhatsApp/Instagram/website	Yes, one builder	Rarely	Sometimes, per-seat pricing	Depends on vendor
Open source integration	Yes (MIT, on GitHub)	Rarely	Rarely	n/a

The honest trade-offs

• If you need order actions inside the chat window (refund, reship, edit an order without leaving chat), a helpdesk suite with broad admin scopes does more - at suite pricing, suite onboarding, and suite data access. Conferbot deliberately requests only script placement
• If you want human-only chat during office hours, a minimal live chat app suffices - until volume or time zones outgrow it. Conferbot's free plan makes layering automation on top a zero-risk experiment
• If your operation spans platforms - BigCommerce plus a WordPress content site plus WhatsApp - one bot across all of them is the actual differentiator, as covered in the enterprise multi-platform guide

Pricing: the app is free; your Conferbot plan is the only cost. The free plan is real, and paid plans start at $19/mo with no per-channel fees.

From an empty storefront corner to an AI assistant answering buyers, in one sitting:

1. See it live first (optional, no account). Install the app, click the one-click demo bot (691c970890527a0468f9b2c9) on the settings page, save, and watch the widget run on your actual storefront
2. Create your free account at app.conferbot.com - the free plan includes the visual builder, AI, and the live inbox; no credit card required
3. Build or borrow a bot. Publish an e-commerce flow from the template library - pre-sale FAQ, product finder, B2B qualification - or design your own in the builder
4. Connect it. Copy the Bot ID (Share > Copy Bot ID), paste it into the app settings, flip the switch, save
5. Tune from the dashboard. Brand colors, a proactive prompt for product pages, disabled URLs for checkout - all without touching BigCommerce again
6. Iterate with data. Watch conversations in the inbox and let analytics point at the flows worth improving

Resources

• App source on GitHub (MIT, 12 automated tests including browser e2e)
• Developer portal: BigCommerce integration guide
• Chatbots for Shopify Plus and BigCommerce enterprise
• Chatbots for e-commerce: the fundamentals
• Pricing - free plan available, paid from $19/mo

Operating beyond BigCommerce? The same bot deploys with one credential to Shopify, WordPress/WooCommerce, Magento, PrestaShop, OpenCart, Ecwid, Wix, Joomla, and any website.