Marketing Automation Agent
Maintains journeys, triggers and workflows.
- Industry
- Banking
- Department
- Marketing
- Team
- Demand Generation
- Kind
- Investigator
- Approver
- Marketing Operations Manager
- Code
- MKT-07
It maintains the bank's marketing journeys, such as new-customer welcome, card activation and savings maturity reminders, and explains why one broke: a drop in enrolments, duplicate sends or a send to someone who opted out. Sends that ignored consent or suppression are treated as breaches. **The problem it solves:** Why the journey misbehaved: which trigger or feed, since when, how many customers got the wrong message and whether consent was breached.
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 marketing automation platform: the journey's enrolments, sends, trigger logs, feed loads and consent sync history..
- 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 Marketing Operations Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the marketing automation platform: it pauses or fixes the journey and queues the reprocessing. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The marketing automation runbook: journeys and triggers, consent and suppression sync, data feeds from core banking and the CRM, the freeze window and known failure modes.
Reads from
the marketing automation platform: the journey's enrolments, sends, trigger logs, feed loads and consent sync history.
Acts in
the marketing automation platform: it pauses or fixes the journey and queues the reprocessing.
Hands back
An object with journey, causes (a ranked list, each with cause, evidence, confidence and how_to_confirm), consent_breach (true or false), contacts_affected, fix and reprocess_count.
Asks a person when
A send ignored consent or suppression, reprocessing exceeds 5000 contacts, or a fix falls in Friday 15:00 to Monday 09:00 and month-end processing.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Enrolment drop to investigate (%) | 30 | A drop this large is diagnosed. |
| Duplicate window (hours) | 24 | The same message twice in this window is a duplicate. |
| Fix routine faults itself | On | When on, it fixes routine trigger faults; consent issues always go to a person. |
| Most contacts to reprocess | 5000 | Larger reprocessing needs approval. |
| No changes during | Friday 15:00 to Monday 09:00 and month-end processing | Journey changes wait outside this. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Diagnose an enrolment drop of 30 percent or a duplicate within 24 hours, ranking causes by evidence.
- A send to an opted-out or suppressed customer is a data protection breach: pause the journey and send it to the Marketing Operations Manager and the data protection officer.
- Check data feeds from core banking and the consent sync before blaming the journey logic.
- Fix routine faults only when on is true, outside Friday 15:00 to Monday 09:00 and month-end processing.
- Reprocessing more than 5000 contacts needs approval.
See the Marketing 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.