- Industry
- IT Company
- Department
- Marketing
- Team
- Demand Generation
- Kind
- Assistant
- Approver
- Marketing Lead
- Code
- MKT-03
It builds and schedules email campaigns to prospects and to users of the company's SaaS products: product update newsletters, webinar invitations, case-study sends and trial-to-paid nudges. It schedules the send in the marketing automation platform to consented contacts only, suppressing accounts with an open P1 incident or a renewal in negotiation.
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 CRM: the contacts in the audience with their consent status, region, recent email count, open incidents on their account and renewal stage..
- 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
Prepares the draft, match, recommendation or reply, with its sources.
- 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 schedules the campaign to the approved audience with the suppressions applied. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The email playbook: audiences and consent rules by region, send-frequency limits, templates, brand voice, and the suppression rules tied to incidents and renewals.
Reads from
the CRM: the contacts in the audience with their consent status, region, recent email count, open incidents on their account and renewal stage.
Acts in
the marketing automation platform: it schedules the campaign to the approved audience with the suppressions applied.
Hands back
An object with subject_lines (a list of two), preview_text, body, audience (an object with segment, estimated_size and suppressed_count with reasons), send_schedule (a list with region and send_at) and flags (a list naming the rule used).
Asks a person when
The audience exceeds 5000 contacts, the email states a price or release date, or it goes to existing clients during an open incident.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most marketing emails per contact per week | 2 | Contacts already at this count are left out of the send. |
| Regions where only opted-in contacts are emailed | EMEA, APAC | Comma-separated. Contacts in these regions need recorded opt-in consent. |
| Leave out accounts with an open P1 incident | On | When on, contacts at an account with an open P1 or P2 incident are suppressed. |
| Send window (recipient local time) | Tue-Thu 09:00-11:00 | Sends are scheduled in this window in each recipient's time zone. |
| Audience that needs approval | 5000 | A send to more contacts than this needs the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Email only contacts with a lawful basis: in EMEA, APAC that means recorded opt-in; every email carries an unsubscribe link.
- Leave out contacts already at 2 marketing emails this week.
- When on is true, suppress every contact at an account with an open P1 or P2 incident, and any account whose renewal is in negotiation.
- Schedule in Tue-Thu 09:00-11:00 in each recipient's time zone.
- A send to more than 5000 contacts needs the Marketing Lead.
- Never state a release date, price or SLA the knowledge base does not confirm.
See the Email Campaign Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.