Cart Recovery Emails per Product With an AI Agent

The short answer: if a dozen products carry most of your cart value and one generic reminder speaks for all of them, let an agent draft an email per product, have a person approve each one, and run the result on Omnisend's Standard plan at $16 a month billed monthly for 500 contacts, where one workflow holds up to 20 split blocks, a branch per product (pricing, conditional split, checked on 26 October 2026). For example, writing 12 product emails by hand at 30 minutes each is 360 minutes; reviewing 12 drafts at 6 minutes each is 72, so the job shrinks by 288 minutes. Whether the new copy recovers more carts is a separate question, and the test at the end answers it. In the EU, the consent setting on the trigger matters more than any sentence the agent writes.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

A generic reminder tells a shopper they left something behind. They know. They left because of the delivery date, the sizing or the returns window, and the product page usually answers that question already. Copy per product puts the answer in the email. Writing a dozen of those is a day's work; an agent drafts them in minutes, and a person checks every fact before a shopper reads it.

What you need, in this order:

1. The sums for your volume. Omnisend's Free plan sends 500 emails a month to 250 contacts and, per its pricing FAQ, includes every paid feature (pricing). For example, 120 abandoned carts a month and a two-email flow make 120 x 2 = 240 emails, inside Free; at 300 carts the same flow needs 600, and Standard's 6,000 a month.
2. The store and the catalogue you already have. A Shopify store connected to Omnisend or Mailchimp, set up as in how to use Omnisend or how to use Mailchimp. For the agent's input, a product CSV from Shopify's Products page, which arrives by email when you export all products and leaves out images (Shopify export), or Omnisend's MCP server, which reads products and categories. Add the text of your shipping and returns page.
3. The narrowest access. Omnisend's MCP connects for the Owner, Admin, Manager or Partner role; choose read-only when the consent screen asks, and write actions then fail with "Permission denied" (MCP docs).
4. A baseline. For the last four weeks of your current cart flow, write down how many contacts entered it and how many of them ordered.

Consent before copy

Under the ePrivacy Directive, marketing email to a person needs their consent first, Article 13(1). The one exception, Article 13(2), covers a seller writing to its own customers about its own similar products, using an address collected during a sale, as long as each message offers a free and easy way to object (EUR-Lex). Someone with a full cart and no order is not yet a customer in that sense. Your counsel can tell you whether a reminder to them is direct marketing; a flow limited to subscribers makes the question moot.

Both platforms can reach shoppers who never opted in, so check one setting on each:

• Omnisend syncs shoppers who never ticked the marketing box as non-subscribed, and lists abandonment flows among what they can receive (non-subscribed contacts). The Workflow Channel Settings on the trigger block offer Subscribed; Subscribed and Non-Subscribed; or Any Subscription Status (channel settings). For EU shoppers, choose Subscribed.
• Mailchimp's first cart email reaches anyone who leaves a cart behind, subscribed or not; from the next email step on, only subscribed contacts receive anything (abandoned cart article). Use Filter who can enter this flow to let subscribed contacts in and no one else.

The workflow

1. Trigger. An identified shopper adds products and goes quiet. Omnisend knows a shopper who signed up through its form, clicked one of its emails or typed an address at checkout; anonymous visitors get nothing, and the flow waits out the Trigger Inactivity Time before it fires (cart guide).
2. The agent reads the catalogue. In Claude or ChatGPT with Omnisend's MCP on read-only, ask for the products in the categories you chose, or upload the Shopify CSV. Paste the shipping and returns text. The agent sees products and policies, never a customer record.
3. The agent decides and writes. For each product it names the one question a hesitant buyer has that the product page answers, then writes a subject line, preview text and 60 to 80 words that answer it. Rules in the prompt: facts only from the page or the policy, each fact listed beside the sentence it came from, no discount unless your policy sheet names one, no stock or urgency claims, and a flag on anything it could not source. The output is one table, one row per product.
4. The human check. Someone who knows the products reads every row against its product page: is each fact there, and can operations deliver every promise? They approve the row or rewrite it. Nothing reaches a flow before that, and nothing reaches a shopper before the consent setting above is done.
5. Into the flow. In Omnisend's Abandoned Cart workflow, add a Conditional Split on the trigger filter for the first product, put its approved email on the Yes path, and nest the next split on the No path; the last No path keeps the generic email. A split takes up to 5 rules and a workflow up to 20 split blocks (conditional split), so a collection can share a branch. In Mailchimp, build one flow per product on Abandons cart with specific products, set to Include, and a catch-all flow set to Exclude those same products (abandoned cart article). Check what a cart holding two of those products receives before you switch on.
6. Output. Each shopper gets their own cart block and the paragraph for the product that matched. Run one real cart through it from a private browser window, as the Omnisend how-to describes, then turn the workflow on.

Free first

Shopify's own abandoned checkout email costs nothing: under Apps, Messaging, Automations, you choose which visitors it goes to and after what delay, and you can edit the template (Shopify). It is one template for every product, and it is often enough. For per-product copy at no cost, the Shopify CSV goes into a free chat assistant with the same rules as step 3, and the approved rows go into splits on Omnisend's Free plan. What the paid tier adds is volume and the MCP route, which removes the copying and keeps the agent's view of your account read-only.

Monthly cost, side by side

Sources, read on 26 October 2026: the Omnisend, Mailchimp and Claude pricing pages. Mailchimp's figures are its lowest contact tier and rise with the audience. For a wider view of the two platforms, see Omnisend vs Mailchimp and the Omnisend and Mailchimp entries.

How to know it worked

• Test the copy, not the flow. Put Omnisend's A/B Test Split straight after the trigger: path A carries the per-product branches, path B the generic email. Contacts are assigned at random, Omnisend advises running until at least 100 contacts complete each path, and it does not pick a winner for you (A/B split). On Mailchimp Standard, a percentage split does the same job (automation flows).
• Count orders per contact who entered, from Shopify orders, against the baseline. A flow's own revenue line counts what followed the email; your order count per entrant shows whether path A beat path B.
• A holdout, if you want the bigger answer. A share of carts that gets no email tells you whether the flow earns its place at all. Omnisend's conditional split article requires a step on only one of a split's two paths, and the A/B split article does not say; confirm in the editor that an empty path saves before relying on it.
• Watch the cost side. Unsubscribes and spam complaints per cart email, against the four weeks before.

The setting the vendor suggests

The channel settings article files abandoned cart reminders under Subscribed and Non-Subscribed, which lets shoppers who never opted in enter the flow: more entrants, more sends, a busier workflow for the platform to show you. In the EU, Article 13 is the reason to narrow it to Subscribed, and that one click belongs before the first branch, not after the first complaint.

FAQ

Can the agent write straight into the Omnisend workflow?

The MCP server lists write operations on workflows, including replacing a workflow's blocks. With the read-only preset those calls fail with "Permission denied" (MCP docs), which is the point: a person pastes approved copy, so nothing unread reaches a shopper.

Does Omnisend's own agent do this?

Partly. Omnisend Agent writes subject lines and preheaders, inserts product recommendation blocks, applies your brand styling and picks send times; its get-started article does not describe drafting body copy per product (Omnisend Agent). Use it for the subject line once the paragraph is approved.

Should the product email carry a discount?

Only where your margin and policy sheet allow it. Omnisend's Abandoned Checkout value split shows one pattern: higher order values get an email with a discount, others an email without (cart guide).