Almost every support conversation on a store is about an order. Where is it, what was in it, can I change it, can I send it back.
Yet on most stores the order and the conversation about it live in two places that know nothing about each other. You have the order open in one tab and the email in another, and the connection exists only in the head of whoever is looking at both.
Linking them
A ticket can be attached to an order. Once it is, two things happen on their own.
The order screen shows the ticket. A panel on the WooCommerce order edit screen with the ticket number, a colour-coded status, and a button through to it. Anyone processing that order can see there is an open support conversation before they ship it.
This works whether or not you have moved to WooCommerce’s newer order storage. It resolves the right screen either way, rather than quietly vanishing for half of stores.
The ticket carries the order. Your agent sees which order the conversation is about, without asking.
Refunds post themselves
When a refund is issued in WooCommerce against an order with a linked ticket, a note appears in that ticket recording the amount, who issued it, when, and the reason given.
It is a private note, so the customer is not emailed twice about the same refund. WooCommerce already tells them. What this does is put the fact into the support record, where the next person to open the ticket will see it.
The gap it closes is a familiar one: a refund is processed, the ticket is not updated because the person doing the refunding was in a different screen, and a week later somebody promises the customer a refund that already happened.
What the assistant can do with orders
For a logged-in customer, the AI assistant can answer questions about their own orders. Recent order summaries are available to it, so "where is my order" and "what did I order last month" work without a human.
Every lookup carries an ownership check. A customer can only ever see their own orders, and a request for somebody else’s is refused rather than answered. That check is in the code, not in the instructions given to the model.
The assistant is also told to establish which order a conversation is about before raising a ticket, so escalations arrive already linked instead of starting with "which order was this?"
Products and shipping
Two more things the assistant can look up on a store.
Product details, so questions about price, stock, variations, weight and dimensions are answered from live data rather than from whatever the product page said when it was indexed.
Shipping zones and costs, read from your actual WooCommerce configuration. It works out what applies to the customer’s country, understands the difference between a flat rate, free shipping, free over a threshold, free with a coupon, and local pickup, and knows when something is virtual and needs no shipping at all.
"How much is delivery to New Zealand" is one of the most common pre-purchase questions on any store, and it is answered from your real shipping table rather than a page somebody wrote two years ago and has not updated.
Without WooCommerce
All of this disappears cleanly. Helpie is not a WooCommerce plugin with the store parts bolted on; the order, product and shipping capabilities register only when WooCommerce is present, and the helpdesk and assistant work the same either way for a site that does not sell anything.