WooCommerce Agent

Install the free “DomainChat — AI Sales & Support Agent for WooCommerce” plugin from your WordPress admin (Plugins → Add New), open WooCommerce → DomainChat, and click “Connect your store”. A tab opens where you sign in to DomainChat (or create an account) and confirm. The plugin creates a dedicated, revocable set of store credentials for a separate “domainchat” shop-manager user — you never copy or paste any keys, and the chat widget is placed on your storefront automatically. Disconnecting from either side revokes everything.

In your WordPress admin, go to WooCommerce → Settings → Advanced → REST API, click Add key with Read/Write permissions, and paste the Consumer Key and Secret into the DomainChat connect screen. This takes about two minutes and works from any DomainChat page that offers “Connect WooCommerce Store”.

When a customer asks about an order, the agent asks for two things — the email used at checkout and an order number (both are in their order confirmation email) — and checks that the order actually belongs to that email in your store. Only when both match is the customer verified. On the website chat the verification lasts the conversation, so they can ask about their orders freely once verified. On messaging apps (WhatsApp, Instagram, Facebook, Telegram) verification is deliberately re-done for each new request — the agent asks for both details again — so a borrowed phone never unlocks a lasting session.

The same two-piece verification (email + order number) is used everywhere — website chat, Instagram, Telegram, Facebook, and WhatsApp. On the website it lasts the conversation; on messaging apps it is re-checked for each new request, since anyone can pick up a phone.

Cart: the agent never pretends to manage the cart in conversation. On the website, every product card has an Add to Cart button that drops the item straight into your real store cart — the customer checks out on your site, with their account and their payment methods. On messaging apps the agent shares product links. Cart edits (quantities, removals) always happen on your store's cart page.

Forms vs. conversation: on the website, cancellations and returns use friendly interactive forms (item pickers, evidence upload). On messaging apps the same requests run fully conversationally — the agent asks which items and why, then submits.

Ask for “trending” or “popular” and the agent ranks products by real customer interactions in your store. Shoppers who aren't sure what they want can say “help me pick” or “quiz me” — the agent plays personal shopper with a few quick questions (occasion, style, budget) and presents curated picks with a one-line “why it matches” for each.

On your integrations page you'll find “Agent-created discount codes” with an on/off switch, a maximum discount percentage, and a daily cap on how many codes the agent may create (0 = unlimited). When it's off, the agent politely tells customers it can't create codes and only shares promotions you've already made.

Tracking numbers and carrier links appear automatically if your store runs a shipment tracking plugin(such as Advanced Shipment Tracking) or stores tracking on the order. If your store doesn't share tracking data, the agent says so honestly — it gives the order status and date and points the customer to their account page, and it never invents a carrier or a number.

On the website chat, “show my orders” renders an interactive order history card with the most recent orders and quick actions. On messaging apps, the agent directs customers to the website chat or their store account (the card needs the website).

1. The customer asks to cancel (the agent confirms their identity first).2. On a multi-item order, the customer picks the scope. On the website chat an item-picker card appears — they tap the items (or choose the whole order) and confirm right in the card, no typing needed. On messaging apps the agent asks the same question in conversation with a numbered list.3. After an explicit confirmation from the customer, the request is submitted and lands in your DC Desk dashboard as a ticket showing the order, the items, and the customer details.4. You approve or reject it in one click — approval cancels the order (or refunds just the requested items) in WooCommerce immediately, notifies the customer, and leaves a note on the order in your WordPress admin.

Customers can ask “any update on my cancellation?” anytime — the agent reports the review state (pending review, approved, or rejected with the reason). Only pre-shipment orders are cancellable; once an order has shipped, the agent guides the customer to a return instead.

The agent checks eligibility first (delivered, inside your return window, returnable products), then opens a friendly return form where the customer picks the items, chooses a reason, selects refund or replacement preference, and can attach a photo and a short video — perfect evidence for damaged or defective claims. Submitting the form creates a ticket for your team with the media attached, emails your team the details, and leaves a private note on the order in your WordPress admin.

The same request runs in plain conversation: the agent confirms which items and why, then submits. Photos can't be attached on messaging apps, so the agent tells customers your team will request evidence if it's needed.

Every return request appears in DC Desk with the items, reason, preference, and any attached evidence. You can refund and close in one click (the refund goes through your payment gateway), mark it handled if you processed it manually, or open the order directly in your WordPress admin. Approvals write a note back onto the WooCommerce order so your admin always shows the full story.

The agent deliberately does not create tickets for things customers can do faster themselves — order status questions, normal returns and cancellations, product questions, or price negotiation. For those it either answers directly or points to the fastest self-service path.

Creation: the agent confirms the customer's identity (their checkout email), creates the ticket, and shares the reference number: “I've raised this with the store team — your ticket reference is #2011. You can check its status anytime right here in the chat.”

Checking status: the customer simply asks — “what's happening with ticket 2011?” — or asks to see their tickets. In a new conversation, they re-verify with the same email first (one question), then ask. Statuses are shown in friendly language: received, in progress, waiting on you, resolved. Only the ticket's owner can see it — a wrong or foreign reference number simply returns “not found”.

Resolution: when your team resolves and closes the ticket in DC Desk, the customer receives a resolution email automatically. If they re-report the same issue while a ticket is already open, the agent recognizes it and shows the existing ticket instead of creating a duplicate.

Tracking: shipment tracking appears when your store shares tracking data (most tracking plugins do).Best sellers: “trending/popular” rankings come from real interactions in your DomainChat chat, not WooCommerce sales reports. Store logins: WooCommerce doesn't connect store accounts to chat, which is why identity uses the checkout email. Order history card: website only — messaging customers are directed to the website or their account.

No. Cancellations and returns are always requests that you approve. The only money that moves is money you release, from your dashboard or your WordPress admin.

A dedicated set of read/write store credentials. With the plugin, they're created for a separate “domainchat” shop-manager user you can revoke anytime; with the key method, you create and revoke them yourself in WooCommerce settings.

The chat widget is cache-safe. If your firewall challenges API traffic, allow “DomainChat” requests to your store's API paths — the connect screen and this guide show exactly how.

Because an email address alone can be known by others. Requiring an order number from the customer's own confirmation email matches the security bar of WooCommerce's own order tracking — and on messaging apps the check is repeated for each new request.

They reach the agent within moments via live updates, and a nightly safety re-sync catches anything missed.

Yes — your store pages (refund policy, shipping, FAQ, About) are synced into its knowledge. It answers only from what it finds and never guesses a policy.