Add an AI Chatbot to Your BigCommerce Store

What connecting BigCommerce gets you

BigCommerce stores tend to carry deeper catalogues than the average storefront, and depth is what generates questions. Specification differences between two similar SKUs. Whether a variant ships to a given country. What the returns window is on a sale item. Each one is answered somewhere in your store, and each one is a shopper deciding whether to keep going.

Connect Evoriqa and an AI agent answers from your own product and policy content, on every storefront page, without your team touching the inbox.

Where the snippet goes

BigCommerce has a purpose-built home for third-party scripts, so no theme file gets edited. The widget goes into Script Manager, which lives in the channel settings for the storefront you're adding it to.

Create a script, paste the Evoriqa snippet, and set the location to the footer so it loads after the page itself. For placement, choose the storefront scope — which BigCommerce defines as every page that isn't checkout or order confirmation — rather than all_pages. More on why that matters below.

Choosing which pages it loads on

This is the one setup decision BigCommerce gives you that most platforms don't, and it's worth two minutes.

Script Manager's scopes are all_pages, storefront, checkout, and order_confirmation. The default instinct is all_pages, and it's usually the wrong one. A shopper on the checkout page has already decided; a chat bubble there is a distraction from a conversion in progress, and the questions it would catch are the ones you wanted answered three pages earlier. storefront puts the agent on browse, product, and cart pages — where the doubt actually is — and leaves checkout clean.

The exception is order confirmation. If "where is my order" is your highest-volume message, scoping a script to order_confirmation as well gives customers a place to ask right after they buy, which is when expectations get set.

Before you start

You'll need control-panel access to your store and your embed snippet from the Install tab, which comes with your chatbot id already filled in. If you don't have a workspace yet, create one free at app.evoriqa.com — no credit card needed.

One real prerequisite: your store must not be on a Blueprint theme. Script Manager is available on non-Blueprint stores, and scripts added through it don't render on the legacy Blueprint engine at all. If you're still on Blueprint, this integration is blocked until you migrate to Stencil — a real gate, not a preference.

Training it on a deep catalogue

A large catalogue is where a grounded agent earns its keep and where a generic chatbot falls over. Crawl the storefront so the agent picks up product pages, category descriptions, and your shipping and returns policies, then check the result in the playground before it goes live.

Ask it the comparison questions your customers actually ask — two similar SKUs, a compatibility question, a sizing edge case — and confirm it quotes your content rather than inventing an answer. On a catalogue with hundreds of near-identical products, the failure mode isn't "it doesn't know", it's "it confidently described the wrong variant". The playground is where you catch that.

Confirming it's live

Open a product page in a private window and look for the chat bubble in the bottom-right, then check the cart page too. If you scoped to storefront, the absence of the bubble on checkout is correct, not a bug.

Common questions

Head or footer? Footer. It loads after the page has rendered.

Does it work on every storefront I run? Script Manager is per storefront channel, so a multi-storefront setup needs the script adding to each channel you want it on.

Can I edit a script added by an app? Not always. Scripts installed via the Scripts API appear in Script Manager but can only be modified by the API account that created them — though a control-panel user can still delete them.

Will it clash with my theme? No. The widget is isolated in a shadow DOM, so its styles and your Stencil theme's never meet.