For WooCommerce stores
Your WooCommerce store, on your own terms — your curation, your keys
Connect your store with your own API keys — no plugin, no code. Your agent answers from your synced WooCommerce catalog, offers the cross-sells you set on your own products, and builds the cart in the chat — then hands off to your own checkout to pay.
See it in motion
From first question to paid order, inside WhatsApp
Your catalog arrives as product cards, the cart lives in the chat, and the shopper pays on your own domain — no marketplace in the middle. The same flow runs on Telegram, Messenger and your website widget.
Answers from your WooCommerce catalog
A shopper asks, and in-stock products come back with live prices — read from your store, not from a copy someone keeps up to date.
The cart is built in the thread
Add to cart is a button on the product — or the shopper just asks, and adding, removing and reviewing all work in plain words. The cart belongs to that conversation, and there is nothing to install.
Checkout on your own store
Tapping through — or simply saying “checkout” — opens your WooCommerce checkout with the cart already in it; payment, tax and shipping stay exactly where they are.
The confirmed order comes back
It lands in the same WhatsApp thread the shopper started in, which is where they will ask about it later too.
Your agent answers from your own WooCommerce catalog
What it does
Your catalog, your cross-sells, your checkout
One agent connected with your own API keys and no plugin on your store — it answers from your synced catalog, offers the pairings you set yourself, and finishes on your own payment page.
Answers from your synced catalog
Descriptions, prices and stock come from your own WooCommerce products — variations included, with a variable product counted in stock while any of its variations is.
Your cross-sells come first
The upsells and cross-sells you set on the product in WooCommerce are what it reaches for first. Where you haven't set any, it falls back to related in-stock products rather than showing nothing — so the merchandising you do is the merchandising shoppers see.
Products as tappable cards
Instead of describing a product, it sends it: image, price and an add-to-cart button — as a swipeable carousel when there is more than one.
Checkout on your own domain
The cart lives in the conversation and hands over to your store's own payment page, on your own domain. No marketplace in the middle, no platform subdomain in the URL.
Order lookup, only for the right person
An order comes out only when the details match the billing contact on it. A wrong email and an order that never existed get the identical reply.
Two updates, sent only if they ask
Order placed and order shipped — that is the whole list, and each is a switch you control. A shopper who opts in gets them in the same conversation.
After the order
“Where is my order?” — checked, then answered
The agent asks who is asking before it shares anything, and a wrong email gets the same reply as an order that never existed. Once the shopper opts in, the shipping update arrives in that same chat.
It verifies the shopper first
Order number, plus the email or phone used at checkout, before a single order detail is read out.
A mismatch gets refused
Wrong details are turned away rather than guessed around — order status is customer data.
Then the real state of the order
Paid, not yet shipped, and the total — the same states WooCommerce itself reports, read at the moment of asking.
Updates without a follow-up
The shopper opts in once, and the “on its way” message arrives on its own — carrying the tracking link when your store has one.
A shop inside the chat
Your WooCommerce catalog, browsable without leaving Telegram
The catalog that answers questions is also a storefront: your products, prices and photos across collection pages, opened from the bot’s menu — and the shopper pays on your own domain. The same storefront serves a Messenger Page too.
Nothing to install
The shopper opens it from the bot’s menu and it rises over the conversation. No download, no browser tab, no outside link they have to trust first.
Stocked from your catalog
Your own products, prices and photos across collection pages that swap from the bottom tabs — and kept in step as your store changes.
Questions about any product
“Ask about this” opens a chat scoped to that one product, answering from live price and stock rather than a description written months ago.
Payment stays on your domain
Add to cart, pay on your own order page — no platform subdomain anywhere in the URL — and the confirmation lands back in the same thread.
Setup
From your store to the chat in three steps
No plugin to install, no code, nothing to configure.
- 1
Approve the connection on your own store
You approve it from your own WordPress admin, and the keys are issued by your store to you. Behind a firewall, paste your own API keys instead.
- 2
That is all you set up
No forms to fill in, no settings to choose. Your store gets an agent of its own, and every other agent in your workspace stays exactly as it was.
- 3
The rest is managed for you
Products and variations import over your store's own REST API and stay in sync, an in-bot storefront is built from them, and your agent starts selling on your connected channels.
Yours end to end
Your keys, your data, your shoppers' privacy
Order details come out only after a shopper proves the order is theirs — a wrong contact and an order that never existed get the identical reply. If they then opt in, the order-status updates land in that same conversation, on Telegram, WhatsApp, or Messenger. Your API keys are encrypted at rest, and your catalog and orders stay scoped to your workspace alone.
Ready to start
Start with your WooCommerce store
WooCommerce Store Assistant
Connect WooCommerce — order questions answered, products recommended, sales closed in the conversation. Live on your website, Telegram, WhatsApp, and Messenger.
Connect your store
Bring your WooCommerce store into the conversation
Approve the connection on your own store — no plugin, no code. WooCommerce asks for read/write because it refuses to register webhooks with a read-only key, and that same permission is what carries a full cart through to checkout: with a read-only key, a multi-item cart gets no checkout link at all. Behind a firewall, paste your own API keys instead. Your catalog syncs itself from there.