Shopper Journey Automation Agent
Maintains abandoned-basket, back-in-stock and post-purchase journeys.
- Industry
- Retail
- Department
- Marketing
- Team
- Demand Generation
- Kind
- Investigator
- Approver
- E-commerce Director
- Code
- MKT-07
It maintains the automated shopper journeys (welcome, abandoned basket, browse abandonment, back in stock, price drop, post-purchase review and loyalty points expiry) and, when one stops enrolling, sends twice or messages the wrong shoppers, finds out why from the journey definitions, event feeds and recent edits. It proposes the fix and applies routine ones, such as re-enabling a trigger or correcting a suppression, in the loyalty and CRM platform. **The problem it solves:** Why a shopper journey stopped enrolling, sent twice or reached the wrong shoppers: when it started, what changed, and how many shoppers are affected.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the loyalty and CRM platform: the journey's definition, enrolment and send history, error logs and recent edits, with the trigger event counts from the e-commerce platform..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to E-commerce Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the loyalty and CRM platform: it applies the approved fix to the journey and re-enrols the affected shoppers. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The journey catalogue: every live journey, its trigger event, entry and exit rules, suppressions (recent purchasers, unsubscribed, complaint open), expected weekly volume, and the change log.
Reads from
the loyalty and CRM platform: the journey's definition, enrolment and send history, error logs and recent edits, with the trigger event counts from the e-commerce platform.
Acts in
the loyalty and CRM platform: it applies the approved fix to the journey and re-enrols the affected shoppers.
Hands back
An object with causes (a ranked list, each with cause, evidence, confidence and how_to_confirm), fix (the change to make), routine (true or false), shoppers_affected and reprocess_count.
Asks a person when
The fix would re-enrol more than 10000 shoppers, a message reached unsubscribed shoppers, or the change falls in Black Friday to Cyber Monday.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Enrolment drop that is a fault (%) | 30 | Weekly enrolment this far below the expected volume is treated as broken. |
| Duplicate window (hours) | 24 | The same journey email to the same shopper within this window is a duplicate. |
| Apply routine fixes | On | When on, it re-enables triggers and fixes suppressions itself. |
| Most shoppers to re-enrol | 10000 | Re-enrolling more shoppers than this after a fix needs approval. |
| No journey edits during | Black Friday to Cyber Monday | Only urgent fixes during this window. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Check the trigger event feed from the e-commerce platform first: a site or tag change that stopped sending basket or browse events outranks a journey edit.
- An abandoned-basket or back-in-stock email must never go to a shopper who has since bought the item, or reach an unsubscribed shopper.
- Treat enrolment 30 percent below expected as a fault and the same email within 24 hours as a duplicate.
- Apply routine fixes only when on is true and outside Black Friday to Cyber Monday.
- Re-enrolling more than 10000 shoppers, or re-sending a price-drop email after the price changed, needs the E-commerce Director.
See the Shopper Journey Automation Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.