The AI Customer Reactivation Agent: Winning Back Dormant Customers in Odoo and MYOB Acumatica

Every ERP holds a list nobody enjoys reading: the customers who ordered every month for years and then stopped. Winning one of them back usually costs less than landing a new account, but the work is tedious enough that it rarely gets done. Someone has to trawl the sales history, work out who has gone quiet, remember why, and write something worth replying to. An agent can do the trawling. The deciding and the sending still need a person, for reasons this post gets into.

An AI customer reactivation agent reads your sales and service history, finds the accounts that have gone quiet against their own ordering rhythm, and drafts the win-back outreach with a reason attached to every name. It sends nothing. A person reviews the queue, removes the accounts the agent had no way of understanding, and approves the rest. We’ve covered the lead qualification agent that decides which new enquiries deserve attention. Reactivation is the same pattern pointed the other way, at customers you already won and then lost track of.

What an AI customer reactivation agent actually does

The agent has four jobs, and sending email is not one of them.

• Read the history you already own. Sales orders, invoices, quotes that never converted, support tickets, the meeting notes a call logging agent has been filing into the CRM. Dormancy only means something against context, and the context is sitting in your ERP.
• Measure silence against each account’s own rhythm. A cafe that ordered weekly and hasn’t for six weeks is dormant. A machinery buyer with an eighteen month cycle isn’t dormant at twelve. A fixed “no orders in 90 days” report treats both the same, which is why those reports get ignored.
• Explain each pick. Two or three lines per account: how long quiet, what they used to buy, anything in the service history that might explain the silence. If the agent can’t say why a name is on the list, the name shouldn’t be there.
• Draft the outreach. An email in your voice that refers to what the customer actually bought, not a generic “we miss you”. Every draft lands in a queue with the records it was built from, and waits.

Adoption is past the experiment stage. The Australian Bureau of Statistics reports 12% of Australian businesses now use AI, rising to 22% of medium-sized firms, and dormant-customer lists are one of the requests we hear most from wholesale and distribution clients. The appeal is obvious: the data is already there, and the downside of a bad draft that a human catches is zero.

What’s already shipped in Odoo and MYOB Acumatica

Both platforms ship the deterministic half of this pattern today, and it’s worth switching on before you add any AI to it.

Odoo 19 Enterprise includes the Marketing Automation app, which ships with a gallery of ready-made campaign templates. One of them, Create Repeat Customers, targets confirmed online orders above a set value, sends a thank-you email, then follows up a week after the first email is opened. Another, Double Opt-in, exists purely to collect provable consent. We verified both in the v19 source code this week. They’re rule-driven: fixed triggers, fixed timers, no reading of context. Notably, none of the fifteen AI modules in Odoo 19 Enterprise touches marketing or mass mailing, so the judgement layer described in this post is wiring you add through Odoo’s APIs, not a feature you switch on. If you’re weighing up the platform side first, our guide to what Odoo CRM covers for Australian businesses is the place to start.

On the Acumatica platform that MYOB Acumatica is built on, dynamic marketing lists rebuild themselves from criteria you define, including purchase history, and campaigns track actual revenue against the members of each list. These are longstanding CRM features, shipped and stable. On the AI side, MYOB’s AI Studio remains in technology preview: user-initiated, unable to create records, with general availability planned for the 2026 R1 release and no committed ANZ date. A reactivation agent over MYOB Acumatica today is external tooling reading through the API, with the CRM’s own lists and campaigns doing the deterministic work.

The split matters. The list of quiet accounts is a query. Deciding which silences are worth breaking, and how, is the part that needs either a salesperson’s time or an agent drafting for a salesperson’s approval.

What a quarterly win-back run looks like

A Queensland wholesale distributor runs the agent on the first Friday of each quarter. It pulls every account whose last order is more than twice its usual reorder gap: 61 accounts. It removes anyone with a credit hold, an open complaint in the service queue, or an unsubscribed contact, which leaves 38. For each one it writes its two lines of reasoning and a draft email that names the products the customer used to buy and asks one specific question, with no discount attached.

The sales manager works through the queue before the Friday sales meeting. She rejects six: one company went into administration in March, two are mid-dispute over a freight claim the agent could see but had no business weighing, and three are accounts she knows moved to a competitor on price, which makes them phone calls, not emails. She edits four drafts and approves 28. The agent schedules the sends, logs who approved what, and keeps her six rejections as notes for next quarter’s run. The agent found the silence. She decided which of it to break.

“Any report writer can list the customers who stopped ordering. The hard part is knowing which silences are recoverable and which ones you earned. The agent drafts that distinction for you. It never gets to decide it.”

Bill Alvarez, Practice Manager, Auboros

Consent is the hard question, not the copy

The part no reactivation vendor leads with: in Australia, a win-back email is a commercial electronic message under the Spam Act 2003, and the ACMA’s guidance is blunt about what that requires. You need consent, express or inferred, before you send. Inferred consent depends on a provable, ongoing relationship with marketing directly related to it, and the ACMA states plainly that a past purchase on its own is not enough. An account that hasn’t ordered in three years is the exact case where inferred consent is at its weakest, which makes reactivation the riskiest email in your marketing calendar, not the safest.

The practical consequences for agent design fall out of the rules. The burden of proving consent sits with you, so the agent’s first check on every account is the consent record, before a word gets drafted. Every message needs a working unsubscribe that is honoured within five business days, stays functional for 30 days, and demands no fee or login. And responsibility can’t be outsourced: the ACMA holds the business that authorised the message accountable even when someone else sends it, and an AI agent is the strongest version of “someone else” yet invented. If personal information feeds the profiling, the Australian Privacy Principles apply to that too. Our AI agent governance guide covers the approval gates and audit trails that make all of this defensible, including the automated decision-making disclosure deadline arriving in December 2026.

What goes wrong, and where to start

The failure modes here are specific, and each one shapes the design.

• Invented history. Language models make mistakes, and a draft that references an order the customer never placed is worse than no email at all. The guardrail is structural: drafts may only cite records by ID, and the approver sees those records beside the draft.
• The complaint you forgot. Some accounts went quiet because of you: a botched delivery, a pricing dispute. The agent reads the service history, but tickets don’t capture everything, and a warm “it’s been a while” to that customer reads as not listening. This is the single best argument for the human gate, because the sales manager recognises the name even when the data doesn’t.
• The contact who left. B2B contacts churn fast, and a personal note addressed to a buyer who resigned two years ago lands on their replacement’s desk as noise. Contact hygiene is a prerequisite, not an afterthought.
• Training customers to wait. Blanket win-back discounts teach your regulars that going quiet earns 15% off. Keep offers out of the first round entirely and let the approver decide, account by account, whether one is warranted.

Starting is simpler than the list above suggests. Run the agent read-only for a fortnight and compare its shortlist with what your sales team already suspects. If the reasons hold up, switch on approved sends for a small segment and watch two numbers: replies and unsubscribes. A reply rate without an unsubscribe spike means the consent judgements are sound. And if a vendor offers to skip the approval step in the name of scale, the ACMA’s position on outsourced responsibility is worth re-reading before you sign. Our AI agent services page covers how we scope this pattern: drafts-first, consent checked before drafting, role-scoped access, every send approved.

---

Wondering which of your quiet accounts are worth waking?

Auboros builds drafts-first reactivation agents over Odoo and MYOB Acumatica from Brisbane, working across Queensland and beyond, with a person approving every send. If you’d like to see your dormant list with reasons attached, book a free consultation. If your list turns out to be too small to justify an agent, that’s exactly what we’ll say.