Marketing Automation Agent
Maintains journeys, triggers and workflows.
- Industry
- Hotel
- Department
- Marketing
- Team
- Demand Generation
- Kind
- Investigator
- Approver
- Director of Marketing
- Code
- MKT-07
It looks after the automated guest journeys, such as pre-arrival upsell emails, check-in welcome messages, post-stay review requests, birthday offers and loyalty tier emails, and finds out why one misfires. It names the cause, such as a broken PMS field mapping, a consent sync or a trigger edited before the drop, and applies routine fixes in the guest messaging and CRM platform. **The problem it solves:** Why the guest journeys misfire: which journeys, the symptoms and figures, when they started, what changed in the PMS feed, triggers, consent or audience beforehand, and how many guests 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 guest messaging and CRM platform: the journeys' enrolment and send logs, trigger settings, field mappings, consent sync status 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 Director of Marketing with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the guest messaging and CRM platform: it applies the approved fix and re-processes the affected guests. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The journey map: each automated journey, its trigger from the PMS or booking engine, its audience and consent rules, the data fields it relies on and recent edits.
Reads from
the guest messaging and CRM platform: the journeys' enrolment and send logs, trigger settings, field mappings, consent sync status and edit history.
Acts in
the guest messaging and CRM platform: it applies the approved fix and re-processes the affected guests.
Hands back
An object with journeys (a list, each with name, symptom, figure and since), causes (a list, each with cause, evidence and likelihood), fix (steps), guests_to_reprocess, data_exposure (true or false) and prevention.
Asks a person when
A fix re-sends to more than 500 guests, a guest received another guest's details, or a change falls in Friday 15:00 to Monday 09:00.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Enrolment drop worth investigating (%) | 25 | A journey enrolling this much less than its baseline is investigated. |
| Window that makes a send a duplicate (hours) | 24 | The same message to the same guest within this is a duplicate. |
| Apply routine fixes | Off | When on, it fixes field mappings and triggers itself; when off it proposes them. |
| Most guests to re-send to | 500 | More than this needs approval. |
| No changes between | Friday 15:00 to Monday 09:00 | Weekend arrivals peak; journey changes wait. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Investigate a journey enrolling 25 percent below baseline or sending duplicates within 24 hours.
- Weigh the causes: PMS or booking engine field mapping, trigger edits, consent sync, audience rules and sending limits, with evidence for each.
- Never re-send to a guest without consent, and never send a pre-arrival message after check-out.
- Apply routine fixes only while off is true, and never in Friday 15:00 to Monday 09:00.
- Re-processing more than 500 guests needs the Director of Marketing.
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.