Give support the order context it needs from Shopify and WooCommerce
Support agents need a small, reliable view of the customer's order before they reply. That view starts with the customer and current order, then adds the facts that change the answer: items, payment and refund state, delivery state, and any entitlement that matters to the question.
The goal is not to copy your whole store into FreeScout. It is to give the person handling the conversation enough context to verify the answer without switching between tabs or asking the customer for an order number they may not have.
Start with the decisions your team makes
Build the order view around decisions, not around every field the commerce platform can return.
| Support question | Context that changes the answer | What the agent can do |
|---|---|---|
| "Where is my order?" | Order number, date, order status, fulfilment state, and a tracking link where your store supplies one | Confirm the right order and give a grounded delivery update |
| "Why was I charged this amount?" | Items, quantities, discounts, shipping, tax, total, payment state, and refunds | Explain the total without reconstructing it by hand |
| "Can I return this?" | Items bought, order date, delivery state, return window, and earlier return activity | Check the policy against the correct purchase |
| "Will this work with what I bought?" | Product names, variants, quantities, and ownership or entitlement | Answer from the customer's actual purchase, then verify any compatibility detail |
| "Can you change my order?" | Current order state, payment state, fulfilment state, and the store's change policy | Tell the customer what remains possible and route exceptions safely |
Keep the matching rule simple
For email support, the customer email on the FreeScout conversation is the practical starting point. Use it to find matching orders, then ask the agent to confirm the customer and order before discussing a payment, refund, address, or delivery detail.
That confirmation matters for shared inboxes, guest checkouts, changed email addresses, and conversations where a customer writes from a different address. A connection can find likely matches quickly. It cannot replace an agent's judgement when the stakes are high.
The minimum useful order view
A useful sidebar or internal summary normally includes:
- Customer name and the email used for the match.
- Order number, date, current status, and total.
- Line items, variants, quantities, discounts, shipping, tax, and refund amounts.
- Fulfilment or delivery information when the support request is about arrival.
- Product ownership or entitlement where it changes what support can offer.
- A direct way to open the source order when the agent needs to verify a detail.
Do not make the agent hunt for the part that answers the ticket. Put the current order first, then show the fields that explain it. Keep older orders available for repeat-purchase, subscription, and warranty questions without making the active ticket hard to scan.
Make Shopify and WooCommerce data useful in FreeScout
The Shopify connector matches a FreeScout conversation to Shopify orders by customer email and displays order history, line items, financial totals, CLV, AOV, and product-ownership context. It uses a read-only Shopify custom app token.
The WooCommerce connector follows the same support pattern through the WooCommerce REST API. It uses a read-only REST API key and displays matched order history, line items, financial totals, CLV, AOV, and product-ownership context.
In both cases, use the sidebar as evidence for a response, not as permission to guess. An order status can tell an agent where to start. A delivery promise, a stock commitment, or a refund decision may still require checking the store record or your policy.
Give AI only the context that improves the draft
Order context can make a draft more useful because it can name the purchased product and avoid asking for facts that are already known. It also makes a bad draft more convincing if the data is wrong or irrelevant.
Before adding order data to an AI context, decide:
1. Which fields actually improve the replies your team sends. 2. Which fields must stay in the agent's view only. 3. Which provider processes the draft context. 4. When an agent must check the source order before sending.
Product ownership can help with questions about compatibility, renewals, downloads, and plan access. It does not prove the customer's intent, eligibility for an exception, or the outcome of a payment dispute. Keep those decisions with the person handling the ticket.
Use read-only access and keep the data path clear
Support order context needs access to customer and order information, so the integration deserves the same care as any other production connection.
- Grant the minimum read-only Shopify scopes or WooCommerce REST API permission.
- Store credentials in the connector settings, not in saved reply templates or internal notes.
- Use HTTPS and remove connections you no longer need.
- Tell agents which information comes from the store and which information still needs a policy check.
- Review what is sent to an AI provider when AI context is enabled.
The Shopify and WooCommerce connectors use read-only credentials. They do not write to the connected store. See the Shopify connector privacy notes and WooCommerce connector privacy notes before connecting a mailbox.
Test the support workflow, not only the connection
After you connect a store, run a few safe tests from a training mailbox or test orders:
1. Open a conversation that matches one known customer and confirm the correct order appears. 2. Check a customer with two orders to make sure the current order is easy to identify. 3. Check an order with a discount, shipping charge, tax, and a partial refund. 4. Check a conversation where the sender's email does not match the order email. 5. Review a drafted reply and remove any detail the agent could not verify from the ticket or the order.
This test catches the practical problems that a successful connection test misses: ambiguous matches, hard-to-read totals, missing state, and agents trusting a summary beyond what it proves.
Next steps
- Set up the Shopify connector for a Shopify mailbox.
- Set up the WooCommerce connector for a WooCommerce mailbox.
- Use How to set up ReplyRabbit to choose what ReplyRabbit can use when it drafts support replies.