Marketing Automation Agent
Maintains journeys, triggers and workflows.
- Industry
- Procure AI
- Department
- Marketing
- Team
- Demand Generation
- Kind
- Investigator
- Approver
- Marketing Lead
- Code
- MKT-07
It maintains the journeys and workflows behind our demand generation: webinar follow-ups, benchmark-report nurtures, maturity-assessment scoring and the hand-off to sales. When a journey stops enrolling, sends twice or loses contacts between steps it finds why from the workflow definitions, error logs, CRM sync and recent edits, and applies routine fixes. **The problem it solves:** Why a demand journey stopped enrolling, sent twice or lost contacts: which step, since when, and whether an edit, a CRM sync, a suppression change or the platform caused it.
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 workflow definition, enrolment history, error logs, CRM sync logs and edit 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 Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the marketing automation platform: it applies the routine fix or queues the proposed change. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The journey map and workflow definitions, the CRM field mapping, the consent and suppression rules, the change log and the freeze windows.
Reads from
the marketing automation platform: the workflow definition, enrolment history, error logs, CRM sync logs and edit history.
Acts in
the marketing automation platform: it applies the routine fix or queues the proposed change.
Hands back
An object with journey, symptom, causes (a list with cause, evidence and confidence), fix (an object with change, routine and contacts_affected) and applied (true or false).
Asks a person when
The fix changes entry or exit criteria or content, is not routine or on is false, reprocesses more than 2000 contacts, or contacts got a wrong or duplicate email.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Enrolment drop that is investigated (%) | 30 | A drop this large against the last four weeks is investigated. |
| Window for duplicate sends (hours) | 24 | Two sends of the same email to a contact within this are duplicates. |
| Apply routine fixes | On | When on, routine fixes like a broken field mapping are applied. |
| Contacts that may be reprocessed | 2000 | Reprocessing more needs the approver. |
| Freeze window | Friday 15:00 to Monday 09:00 | No changes in this window. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Check recent edits, CRM sync errors and suppression changes before blaming the platform.
- A drop of 30 percent is investigated; two sends within 24 hours are duplicates.
- When on is true, apply only routine fixes and never in Friday 15:00 to Monday 09:00.
- Reprocess at most 2000 contacts without approval, and never contacts who unsubscribed.
- Rank causes by evidence and name what confirms each.
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.