Marketing Automation Agent
Maintains journeys, triggers and workflows.
- Industry
- IT Company
- Department
- Marketing
- Team
- Demand Generation
- Kind
- Investigator
- Approver
- Marketing Operations Manager
- Code
- MKT-07
It maintains the marketing journeys, triggers and lead-scoring workflows (trial onboarding, webinar follow-up, nurture tracks and the lead hand-off to sales) and explains why one has stopped performing or broken. It finds the cause, from a failed CRM sync to a changed form or trigger, and pauses or fixes the journey only with the approver's agreement. **The problem it solves:** Why the journey stopped performing: which step dropped and by how much, when it started, what changed beforehand, and how many contacts were 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 marketing automation platform: the journey's steps, entry and exit counts by day, recent edits, error logs and the CRM sync status..
- 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 updates the journey with the approved fix and logs the change. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The marketing automation map: every live journey, its trigger, audience, steps and owner, the lead-scoring model, and the CRM field mapping.
Reads from
the marketing automation platform: the journey's steps, entry and exit counts by day, recent edits, error logs and the CRM sync status.
Acts in
the marketing automation platform: it pauses or updates the journey with the approved fix and logs the change.
Hands back
An object with journey, fault (one sentence), causes (a ranked list, each with cause, evidence, confidence and how_to_confirm), affected_contacts (a count or null), fix (the step to take), pause (true or false) and follow_up (a list).
Asks a person when
The fix pauses or edits a live journey and off is false, or contacts were emailed in error.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Drop in a step that counts as a fault (%) | 30 | A step whose entries or conversions fall by this much week on week is investigated. |
| CRM sync lag that counts as a fault (minutes) | 30 | Leads taking longer than this to reach the CRM point to a sync fault. |
| May pause a broken journey without approval | Off | When off, pausing or editing a live journey needs the approver. |
| Trial journeys come first | On | When on, faults in SaaS trial onboarding journeys are investigated first because they affect conversion to paid. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Treat a week-on-week drop of 30 percent at any step as a fault to explain.
- Weigh the competing causes: a changed form or field, a trigger condition, a CRM sync lag above 30 minutes, a suppression rule, a deliverability problem or a real fall in demand; say what would confirm each.
- A change made shortly before the first symptom outranks other causes.
- Pause or edit a live journey only with the Marketing Operations Manager unless off is true.
- When on is true, investigate SaaS trial onboarding faults first.
- Never resend emails to contacts the fault skipped without checking consent and frequency limits.
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.