DT-PM AI Sale Assistant for WooCommerce

DT-PM AI Sale Assistant for WooCommerce (DT-PM AI Sale Assistant for short) is not a generic AI chatbot bolted onto search, and it does not just match keywords in a product’s title or description. For each product category, it builds an explicit “causal chain” – a structured model of the actual questions and criteria your customers weigh when choosing between products (e.g. intended use, must-have features, budget) – and you, the merchant, review and confirm that model before it ever talks to a shopper. Every recommendation the assistant makes is then reasoned through that confirmed, category-specific model, not generated from an unstructured prompt or a plain product search.

Main features:

• Chat widget for your storefront – a friendly assistant your customers can talk to on any page of your storefront (product pages, homepage, cart, checkout, and more), asking questions and getting personalized product suggestions, with direct “Add to cart” buttons.
• Category analysis – reviews your existing WooCommerce categories and groups them into sensible subcategories for the advisor to reason about.
• Causal chain builder – an AI-assisted, merchant-reviewable model of what actually drives a purchase decision in each subcategory (e.g. intended use, must-have features, budget), which you can review and adjust before it goes live.
• Product coverage tools – prepares your product catalog (descriptions, attributes) so the assistant can match real products to real customer needs, with an overview of what is already covered and what is outstanding.
• Customizable tone of voice – match the assistant’s writing style to your brand, either written manually or generated from example pages of your own site.
• Configurable escalation – let customers reach a human via email or a link of your choice when the assistant can’t help.
• Customer feedback loop – shoppers can rate recommendations, and negative feedback is summarized for you so the underlying model can be improved over time.
• Status tab – see your current pricing tier, catalog usage against your plan’s limit, and (on the free tier) remaining purchased conversation credit, with direct links to upgrade or top up.
• Service Agent – a second assistant mode, separate from product advice, that handles order and support questions for logged-in customers:
  • looks up a customer’s own order history, or one specific order by number, to answer status/shipping/tracking questions without asking for details it can already see;
  • when it can’t help further, drafts a short summary and – only after the customer reviews it and clicks “Yes, send” – emails it to your configured support contact;
  • answers shipping, returns, withdrawal, payment, and FAQ questions from pages you pick on your own site, kept in sync automatically;
  • reports shipment tracking numbers, including a fallback for shipping plugins that don’t use the official WooCommerce Shipment Tracking format.
• Bring your own AI model – on any tier, including free, use your own Anthropic, Mistral, or OpenAI API key and pick a specific model per provider instead of our platform default.
• MCP Bridge – optionally generate a key so an MCP-capable AI client (e.g. Claude) can read and change most of this plugin’s settings on your behalf.

How it works: this plugin is a thin WordPress/WooCommerce interface. The actual AI processing (analyzing your categories, building the causal model, generating recommendations) runs on our own hosted backend service, which this plugin talks to over HTTPS. See “External services” below for exactly what is sent and when.

Free to start, paid tiers for growing stores: every store gets a free tier with a usage allowance and a one-time trial month. Larger product catalogs or higher usage require a paid plan – see the plugin’s Status tab for your current tier, catalog usage, and an upgrade link.

Requirements: an active WooCommerce installation. An outbound HTTPS connection from your server to our backend service (see “External services”) is required for the plugin to function.

External services

This plugin relies on our own hosted backend service (“DT-PM AI Sale Assistant service”, currently reachable at https://api.dt-pm.eu) to do the actual AI work behind the recommendations. Here is exactly what is sent to that service, and when:

1. When you click “Connect this store” (shown on every DT-PM AI Sale Assistant admin page until you do, right after activating the plugin): your store’s web address and store name are sent once, to set up an account for your store on our service so the advice features can work at all. You confirm the current version of our AVV (data processing agreement) as part of this same step, and that version number is sent along with it; the agreement text itself is read from, and the version number checked against, our service beforehand (no store data sent for that check). If you connected before this confirmation step existed, a dashboard banner asks you to confirm the current AVV version afterwards in the same way. Nothing is sent automatically on activation itself – the plugin waits for this explicit action.

2. While the plugin stays active, on an ongoing schedule: the plugin automatically checks in with our service multiple times a day and once a week. These automatic check-ins send only your store’s account identifier – never any product information – and are used to keep your account up to date (for example, tracking your free trial month, keeping previously-submitted product availability current, and, if you’ve connected a dt-pm.eu license key, confirming with our service that it’s still valid). These check-ins only happen once your store is actually connected (see “Installation” below) – none of them run beforehand.

3. Only after you have actively set up the Category Analysis and Causal Chain features yourself: those same daily/weekly check-ins start additionally including real data from your product catalog (product SKUs and category names), so our service can keep its recommendations accurate. No product data is ever sent before you complete that setup step. Alongside your product data, the causal chain logic generated for your categories (the decision questions and criteria the assistant uses to advise shoppers) is also stored on our servers and used to run your chat assistant. On the free tier, an anonymized summary of that structure – just the category type and the list of decision criteria used, never product names, prices, or customer data, and with no way to trace it back to your store – is additionally used to improve causal chain generation for everyone. On paid plans, you can turn this off in the plugin’s settings.

4. Only after you have started processing your product catalog for a subcategory yourself (the Product Coverage step) and that run appears to have stopped partway through: the plugin automatically checks once an hour whether previously started catalog processing is still incomplete and, if so, resumes it by resending the full data (name, attributes, price, date last modified) for the still-missing products only – the same data already sent when you click “Process remaining products” or “Update changed products” yourself. This never starts processing for a subcategory you have not already begun yourself.

5. Every time one of your shoppers uses the chat widget: their typed messages (and, where relevant, the product page they are viewing and your store’s configured language) are sent to our service in order to generate a reply. Our service forwards that message to a third-party AI provider – by default Anthropic (Claude); if your store uses its own AI provider key (BYOK, available on every tier), your configured provider (Anthropic, Mistral AI, or OpenAI) and chosen model are used instead, under your own account with that provider. Separately, finding matching products for that reply uses Mistral AI’s embedding service on our account, regardless of your BYOK setting. This only happens while a shopper is actively using the chat widget on your site – no shopper data is sent at any other time. To identify your store for these requests without exposing a long-lived credential to every visitor’s browser, your WordPress server itself exchanges your store’s permanent credential for a short-lived access token (valid 15 minutes) right before the widget needs one – this is only ever your store’s own already-known account identifier, no new data.

6. When a logged-in customer asks about an order in the chat (their own order history, or one specific order by number): that order’s status, order date, line items, shipping method, and tracking numbers are sent to our service and on to the AI provider in use (see point 5) to generate the reply, the same way a chat message is. This only ever covers orders that already belong to the logged-in customer’s own account – never a guest, and never another customer’s order.

7. Once you assign a page to a slot in the “Service Assistant Policies” section (Shipping, Returns, Withdrawal, Payment, FAQ): that page’s text is sent to our service when you save, and again once a day for as long as the slot stays assigned, so the assistant can answer from your own wording instead of guessing. Unassigning a slot (back to “— Not configured —”) removes its stored text from our service.

8. When a customer agrees to a handover to your support team (“Yes, send”) in the chat: the conversation summary and the customer’s contact details (email, and phone if given) are not sent to our service – your own WordPress installation emails them directly to your configured support contact (via WordPress’s standard mail function), with the customer’s address set as the reply-to, so a reply goes straight back to them. Immediately beforehand, the plugin confirms with our service that a genuine handover was actually offered for that conversation – only your store’s account identifier and an internal conversation reference are sent for that check, never the summary or the customer’s details.

9. If you generate a key in the “MCP Bridge” section of the Service Agent tab: an MCP-capable AI client holding that key (entered there as a Bearer token) can read this store’s current backoffice settings (e.g. AI provider/model choice, escalation target, widget title, knowledge-pool participation) from our service, and change most of them the same way the Settings page itself would – never your AI provider API keys, which stay in the browser-based Settings form only and are not exposed through this bridge. This only works while a key exists; revoking it stops it immediately.

By using this plugin you agree to our Terms of Service.