WooCommerce
Set up an AI agent for WooCommerce that learns your products, orders and customers, answers shoppers in your chat bubble and helps your team.
eesel's AI agent for WooCommerce learns your store and answers shoppers in your chat bubble, your helpdesk (such as Gorgias) and Slack. It knows your products, orders and customers, so it can tell a shopper where their order is, what they bought and what is in stock.
It also helps your team run the store. Ask it in Slack or the dashboard to look into an order, leave a note for the team or update an order, and it does the work in WooCommerce and tells you what changed.

Set up eesel in WooCommerce
Ask your agent to connect WooCommerce
Open the chat in your dashboard and ask it to connect WooCommerce. It posts a link to connect your store. Prefer to click? Integrations in the left sidebar has a WooCommerce page with a Connect button.


Create a REST API key in WooCommerce
The connection needs a consumer key and secret. In your WordPress admin open WooCommerce > Settings > Advanced > REST API, click Add key, set Permissions to Read/Write, and click Generate API key. Copy both values before you leave the page.
A person signs in and does this in the WordPress admin. Every screen is on Set up WooCommerce.
Confirm the connection
Back in the chat, your agent confirms the store is connected and suggests a first thing to try, such as looking up an order.

Check it worked. Integrations > WooCommerce reads Connected, lists Products, Orders and Customers under Sources, and splits the actions into Read and Write groups. From a terminal, eesel status lists WooCommerce as connected.

Act on an order from Slack
With Slack connected, a teammate can mention @eesel in a channel and ask it to act on an order. When an action needs your OK, eesel posts an approval card straight into the thread, with Approve, Deny and Review in eesel buttons.

Approve it, and the agent adds the note and confirms in the thread.

The note appears on the order in WooCommerce as a private note, so the customer does not see it.

Put it on your storefront
The chat bubble puts your agent in front of shoppers on your store. Ask in the dashboard chat to add a chat bubble for your store. Your agent sets it up with your store's colours, a welcome message and starter questions. Then paste the snippet from your Chat Bubble page into your site, just before the closing </body> tag. The Chat Bubble page has the install steps.
Hand a shopper to your team
When a shopper asks for a person, your agent can take their details and open a ticket in your helpdesk. Tell it how in the dashboard chat, for example: "When a shopper asks to speak to a person, ask for their name and email, create a Gorgias ticket with a summary of the chat, tag it chat-bubble-handover, and tell them our team will follow up."

It saves the rule to its Instructions.

On the storefront, a shopper reports a problem and asks for a person. Your agent asks for their name and email.

The shopper gives them, and the agent opens the ticket.

The ticket lands in your helpdesk under the shopper's email, with a summary of the chat as the first message and the handover tag on it.

Whether a handover waits for your OK depends on the permissions you set for your helpdesk actions.
Sources, triggers and actions
Sources
Sources are what your agent learns from in your store. eesel copies them when you connect.
Products
Your catalogue, with SKUs, pricing, stock and variants
Any REST API key
Orders
Your orders, so your agent can find and read them
A key that can read orders
Customers
Your customer records
A key that can read customers
Orders and Customers only appear when the REST API key you created can read them. Switch any source off on Integrations > WooCommerce if this agent shouldn't learn from it. The lookup actions below still read your store live. Written content such as your shipping or returns policy is not in WooCommerce, so connect your website as well.
Triggers
WooCommerce has no triggers. Nothing in your store starts an agent run. The conversation comes from the chat bubble, your helpdesk or Slack, and your agent uses its WooCommerce actions while it handles it.
Actions
Actions are what your agent can do in your store. WooCommerce's actions come from the live connection, so you may see more than the ones below. They are listed on Integrations > WooCommerce in two groups.
Read
Look up orders
Lists orders or reads one, with its items, totals, status and notes
Look up customers
Searches customers by email or name and reads their details
Look up products and categories
Lists and reads products and product categories
Look up subscriptions
Lists and reads subscriptions, with the WooCommerce Subscriptions extension
Write
Add order note
Adds a private or customer-facing note to an order
Update order status
Moves an order to another status, such as processing or completed
Create refund
Records a refund against an order
Create order, create customer
Creates a new order or customer
Update products and categories
Creates or updates products, and creates, renames or deletes categories
Update subscription
Pauses, resumes or cancels a subscription, or moves its next payment date
Delete order
Deletes an order
You stay in control the whole way. Adjust your AI agent's access to knowledge and its action permissions to your liking. See Actions and Approvals.
Limitations
A refund in WooCommerce is not always money returned. It records the refund on the order. Whether the money moves depends on your payment gateway.
Subscriptions need the WooCommerce Subscriptions extension. Without it there are no subscription actions.
Status changes and customer notes can email the customer. Whether WooCommerce sends one depends on your store's email settings. Ask for a private note when it is only for your team.
Troubleshooting
FAQ
Related pages
Set up WooCommerce for every screen of the WooCommerce admin setup
E-commerce Sales Rep for the job your agent does on a store
Chat Bubble for putting your agent on your storefront
Actions and Approvals for choosing what your agent may do
Integrations overview for how sources, triggers and actions fit together
Last updated



