Skip to content

AI Mailing

Verified

AI Mailing (Emailing → AI Mailing) is an autopilot: it decides who to write to, when and what, within the limits you set. You do not need to be a marketing analyst — you set the goal, frequency, allowed scenarios and message content. MitoOps picks recipients, scenario, products, text, banner and discount code.

The Overview tab has a single switch: AI Mailing on / off. While it is off, the autopilot prepares and sends nothing; you can prepare settings and content in advance.

If your account is in test mode, you see the “Test mode” badge. Messages then go only to your test addresses (Settings → Your test email addresses), never to customers. On the MitoOps trial, AI Mailing only runs in test mode. On a paid plan you switch to live operation yourself, for each store separately and with a confirmation (Settings → Stores). Your plan sets how many contacts AI writes to; when more join, nothing stops: AI writes to the first ones up to the limit and the rest wait.

setting options
Goal Sales · Balanced · Conservative
Max emails per contact in 30 days 1 to 4 (a rolling window, not a calendar month)
Minimum gap between emails 24 · 48 · 72 · 96 · 120 · 168 hours
Gap between marketing emails (all channels) 0 to 72 hours, default 3 (0 = off); applies to automations and AI Mailing, to newsletters only when the switch is on
Allowed scenarios after purchase, cross-sell, repeat purchase, reactivation, useful content, relevant product, VIP, seasonal
Products in the message on / off, 2 to 8 (useful content and the post-purchase message always go without products; cross-sell and relevant product carry only the products they were chosen for)

The autopilot counts all MitoOps marketing mail together — manual campaigns, automations and AI Mailing, across all your stores — and never adds another e-mail on top of it. Manual campaigns and automations set their own timing; the store daily and hourly caps apply to them, and automations also respect a short gap between marketing emails: an automation that would send an email sooner than 3 hours (configurable) after another marketing email to the contact waits exactly until the gap has passed. Emails of the same scenario do not delay each other; you set their spacing yourself. Newsletters are not delayed by default; you can turn the gap on for them with a switch. Order confirmations and shipping messages do not count towards the limits and are never delayed by marketing. After a transactional message the autopilot waits a few hours. Right before sending, the autopilot re-checks that the decision still holds: after a new order, when the offered product was bought, when a product is unavailable or when the right moment has passed, the message is not sent and the reason is shown in the Log. The post-purchase message goes out only once the customer actually has the goods: after the shipment is delivered according to Expedition tracking, according to the delivery date from the store, or when the order is in a status configured as closed for your store (MitoOps support sets up the status mapping on request) — a paid order on its own is not enough. A scheduled newsletter and scheduled automations take precedence: when a contact has a confirmed newsletter or a waiting scenario message within the next hours (closer than the configured spacing), the autopilot steps aside and defers — it never moves earlier; the Log shows a “Deferred” row with the reason, the time of the other message and the next safe time. Drafts, campaigns without a scheduled time and enabled scenarios without a waiting message block nothing. Reactivation goes to the same person at most once every 30 days and the same text is never sent to them twice — when no new text is available in the library, the message is skipped. A text written about a specific product goes only with a message that offers that product, and the button and the first card lead to it. Educational and post-purchase messages offer no product, so they carry general texts only. For relevant product, repeat purchase and cross-sell you can also keep a fallback text that names no product: the autopilot uses it when there is no exact text for the selected product and adds the product and the button itself. Without an available product a fallback text is not sent. When the library has no suitable text, the message is skipped at planning; in test mode the Test tab shows the reason.

The brand voice is set in AI centre → Shop heart (shared by all AI tools); AI Mailing only uses it. While the shop heart is missing something essential (the brand, customers, tone, formal or informal address, what AI must never claim), AI Mailing does not prepare new texts on its own; approved texts keep going out. For scenarios that offer a product, maintenance prepares a general fallback text (MitoOps inserts the product) as a draft that only a person switches on.

  • Texts — a library of variants (subject, preheader, headline, short intro, call to action, audience, validity period). Generate texts with MitoOps AI creates 10 to 50 variants without writing a prompt; MitoOps uses your brand voice, shop language and catalogue. Insert the customer’s name as {{first_name}}; when the name is unknown, the sentence works without it.
  • Banners — only the image address (https), a description and optionally a click target. A banner is optional and the email works even without images. “Load banners from the shop” offers product images MitoOps knows about.
  • Discount codes — you create codes in your shop admin and record them here by shop, type and period. The autopilot uses only enabled, valid codes; if none fits, it sends without a coupon. MitoOps never writes codes into your shop.

Texts, banners and codes can have a validity period (“valid from – until”), for example for Black Friday.

Colours on the left (background, content area, headings, text, links, button), a live preview on the right — the very email customers receive, with desktop / mobile and light / dark switches. Logo, signature, footer and sender are set once in Settings → Emails. Every message carries a mandatory footer with an unsubscribe link that cannot be removed.

The last 30 days: sent, conversions, revenue by currency, unsubscribes and active shops. A conversion is a qualifying order within 7 days of a human click and it is credited to a single message — the one with the last click before the order, the same as in Reports; when a customer clicked two messages, the order is not counted twice. History by day with a message preview (available for 30 days). Anything not measured shows a dash, not a zero. Business results are not counted in test mode.

Marketing goes only to addresses with consent. MitoOps takes it from three places:

  • The store’s subscriber list (for example Shoptet): read automatically.
  • The checkbox at checkout (a store that sends consent with the order, for example WooCommerce connected to MitoOps): a ticked checkbox on an order placed at checkout is consent dated with the order. An unticked checkbox changes nothing and unsubscribes nobody. Contacts shows whether your store sends the field.
  • The website popup: consent counts after the click in the confirmation e-mail.
  • The store form (for example in the footer): the same website code captures sign-ups from the form your store already has and records the contact right away, on every store. Nothing needs switching on. For a store with its own subscriber list (for example Shoptet), consent is confirmed by that list, which MitoOps reads immediately; elsewhere MitoOps sends a confirmation e-mail and consent counts after the click. It can be switched off in Newsletter popup, tab Install on website. A form where the visitor left the newsletter box unticked is not captured.

The store’s subscriber list is read every 15 minutes and again before a send if the last read is older than 5 minutes. Someone who unsubscribes directly in the store usually stops getting marketing within 5 minutes. If the list cannot be read, marketing still goes out for at most 20 minutes after the last successful read; after that the send waits and tries again. Only mail whose consent may come from that store waits, and the campaign shows which store it is waiting for. If a store stops giving access to the list (for example a token without permission), fix the access; until then, marketing to these contacts waits. You can see the status in Contacts under Consent sync from stores. For a store where consent comes with the order, it shows how many orders carried consent and how many did not.

Contacts include a list of addresses that will not receive marketing: revoked consent, unsubscribe, complaint, undeliverable address, manual block. Anyone who unsubscribes via the link in a message stops receiving marketing from every store in your account; order confirmations and other transactional mail continue. Only their own confirmed consent (a click in the confirmation e-mail) or you in the Blacklist can bring them back. You can also block an address manually — for one store or for the whole account. Mailboxes of payment gateways, carriers and automated systems never receive marketing.