AI Chatbot for WooCommerce: Emporiqa Sales Assistant

No. You do not create an account with an AI provider, paste an API key, or manage tokens or usage limits. The AI model cost is already inside the per-conversation price, so there is no second bill.

You'll get an email before the credit is exhausted, and again when the next billing month's spend approaches your $59/month default cap. If no card is on file when the credit runs out, the widget pauses on your storefront. Your store keeps working, but the chat doesn't answer until you add a card. The cap is a hard ceiling: spending stops when you hit it, and you control whether to raise it or not from the billing dashboard.

You can read every conversation in the dashboard, and low-rated ones are flagged automatically, so you find out from the transcript rather than from a customer complaint. Product facts follow your synced catalog, so prices and stock track your store. When the chatbot isn't sure, it says so and offers to bring in a person instead of guessing. You can also open any live conversation and take it over yourself, not only the ones that asked for help.

It recommends. Ask it for "a gift for a runner under 60" and it returns products you stock, with the reason it picked them, then offers to add one to the cart. AI product recommendations come from your synced catalog, including variations, stock, and price.

No, it sits alongside it. Your search box matches words; the chatbot understands a sentence with several conditions in it and answers in the shopper's own language. Shoppers who know the product name still use search.

Both. It answers shipping, returns, payment, and policy questions from the pages you sync, and it can look up an order status for a customer. When a request needs a person, such as a refund, it brings in your team with the conversation attached.

The plugin is free, and you can install it and connect your store without a card. The Emporiqa service behind it is pay-as-you-go: $25 of signup credit (about 100 conversations on us), then $0.25 per conversation with a monthly cap you set. A conversation is billed once, when the shopper writes their first message, so bringing your team into it adds no second charge. If the chatbot never talks to a shopper, you never pay.

Live chat routes a shopper to a person, so it answers when someone is at the keyboard. This chatbot answers on its own from your synced catalog, recommends products, and handles objections, so nobody has to sit at a desk for a shopper to get an answer. Your team can still open any live conversation and take it over, whether or not the shopper asked for a person.

You don't need them for the one-click flow. In Settings → Emporiqa, click Connect to Emporiqa. You'll sign in on emporiqa.com, pick a store, and the plugin receives the connection details for you. To paste them yourself, expand I'd rather paste credentials manually on the same settings page. The Store ID and Connection Secret are in your Emporiqa dashboard under Settings → Integration.

One-click connect requires HTTPS, because the connection details are exchanged through a signed handshake back to your site. If your store runs on plain HTTP, expand I'd rather paste credentials manually on the settings page and paste the Store ID and Connection Secret from your Emporiqa dashboard. Both flows land you in the same place.

Ask it for something you don't stock and it says so, instead of inventing a product. Prices, stock, variations, and policy pages come from what your site syncs, and they update via webhooks as you change them. When the chatbot can't answer with confidence, it tells the shopper and offers to bring in a person. You can read unedited conversations, refusals included, on the proof page, then open the live demo and ask it yourself.

Outside the business hours you set, the chat keeps helping and takes an email or a phone number, with the shopper's agreement, so your team can pick it up in the morning. Inside your hours it brings in a person, and whoever opens the conversation reads it from the first message, along with the summary the chat writes when it calls for help. While a person is being reached the shopper sees a banner, and can cancel it and keep talking to the chat. You choose where the alert lands in your Emporiqa dashboard.

Deactivate the plugin from your WordPress Plugins screen. The chat widget disappears from your storefront immediately. Your synced products stay on the Emporiqa side until you delete the store there, so you can reactivate later without re-syncing.

Yes. The plugin automatically detects Polylang and WPML, and syncs content in all configured languages. Languages are auto-detected on activation.

After connecting, the Sync tab shows a green welcome card with a Send my catalog button. Click it to send your products and pages. Or use the Sync All button in Settings → Emporiqa → Sync tab at any time, or run wp emporiqa sync-all via WP-CLI. After the initial sync, changes are sent automatically in real-time.

Yes. Use the emporiqa_should_sync_product filter: add_filter( 'emporiqa_should_sync_product', function( $should_sync, $product ) { if ( $product->get_price() <= 0 ) { return false; } return $should_sync; }, 10, 2 );

By default, the page post type is synced. You can configure additional public post types (posts, custom post types) in Settings → Emporiqa under "Pages and posts to include".

Yes. The plugin declares compatibility with WooCommerce High-Performance Order Storage (Custom Order Tables).

The plugin exposes a REST API endpoint that Emporiqa calls when a customer asks about their order. Requests are authenticated automatically using your connection secret.

Yes. The chatbot accepts a photo upload, describes what it sees (color, material, category, distinctive features), and searches your catalog using that description. Works best for products with photos that show the item clearly. The shopper doesn't need special tags on your products. The visual search runs through the same catalog you already sync.

Your synced store content: products, variations, prices, stock, and the pages you choose to sync, such as shipping, returns, and FAQ. Product facts come from that catalog, not from the model's training data. If something isn't in what you synced, the chatbot says so rather than filling the gap.

The plugin is free. This WooCommerce chatbot is pay-as-you-go: you pay only when it talks to a shopper. $0/month base + $0.25/conversation. New accounts get $25 of signup credit (about 100 conversations on us), no card required at signup. There is no monthly plan and no free trial. The $59 figure is a spending cap, not a fee: it is the default ceiling on what you can be charged in a month, and you raise, lower, or remove it from the billing dashboard. A month with 40 conversations costs $10, not $59. Enterprise option for catalogs over 100,000 products. Full pricing at emporiqa.com/pricing/.

Good fit if your shoppers have to choose between similar products on size, fit, compatibility, or specs, if the same pre-sales questions keep arriving by email, or if you sell across borders and need answers in the shopper's own language. Less good if you sell impulse items at low order values, or if a shopper can already pick the right product without asking anything. If your main goal is ticket routing with CRM sync and agent workflows, a helpdesk product suits you better than this one.

Cost follows traffic, not revenue. Multiply the conversations you expect in a month by $0.25. The share of visitors who open a chat varies by store and by where the widget sits, so you will find your own figure in the first weeks. As an illustration, if 3 in 100 visitors opened the chat, 40,000 monthly visitors would come to roughly 1,200 conversations, about $300, and you would raise the $59 default cap to keep the chat live all month. The $25 signup credit covers about 100 conversations, enough to get a rate of your own to budget from. Budget from the per-conversation rate rather than from the default cap. A browse-heavy store with low conversion pays the most and gains the least.

Billing starts when a shopper writes, so widget loads and ignored pop-ups cost nothing. You can block a visitor from future conversations, and the block applies before the next one is billed. You can limit the chat to the countries you sell to. If one connection keeps starting conversations, the chat asks for a human check before it starts another. None of that is a wall: someone determined, on a VPN or signed out, gets through. What it does is take the worst case from one address from about 60 conversation starts a day down to 20. The cap is still a hard ceiling behind all of it, spending stops when you reach it, and raising it is your decision. If you think abuse hit your account, email rosen@emporiqa.com.

Partly, and you should know the limit before you rely on the number. The dashboard shows revenue from shoppers who used the chat and then bought. Those shoppers were already more interested than average, so the figure shows a correlation and not proven lift. There is no built-in holdout mode yet. If you want a defensible number, run the chat on part of your traffic and compare against the rest in your own analytics.

Not yet. There is no topic blocklist and no way to pin an exact answer. What does constrain it: it answers from your synced catalog and pages, and it declines what it cannot ground there instead of filling the gap. You can watch that behavior and try to break it at emporiqa.com/proof/.

Simple, variable, grouped, and external products. Subscription, booking, and composite or bundle types added by third-party extensions are not specially supported.

No. On pay-as-you-go there is no service level agreement, and there is no SOC 2 or ISO 27001 certification. What does exist: webhooks signed with HMAC-SHA256, PKCE on the connect handshake, encryption at rest, rate limits, publicly listed subprocessors, an EU company under GDPR, and no training on your data. An SLA and dedicated support are Enterprise terms. On pay-as-you-go the founder answers support email himself, normally within one business day.

Deactivate the plugin and the widget is gone from your storefront immediately. Chat history is deleted after 90 days on a rolling basis. There is no conversation export yet, so save any transcripts you need before they age out. Your catalog was never ours: it stays in WooCommerce.

Fair question, and the install count is public, so there is no point arguing with it. Two things reduce the risk. The plugin runs no customer-facing logic of its own: if Emporiqa is unreachable, the chat bubble does not appear and your storefront and checkout carry on as normal. And the source is GPL, so you can read it before you install it. For answer quality, read the unedited demo transcripts and rerun any of them yourself at emporiqa.com/proof/.

The widget script loads asynchronously in the footer, so it does not block your page from rendering. The chat interface itself downloads only when a shopper opens the bubble. No language-model call runs inside your server: that all happens on Emporiqa's side.