- Industry
- Procure AI
- Department
- Marketing
- Team
- Demand Generation
- Kind
- Assistant
- Approver
- Marketing Lead
- Code
- MKT-03
It builds email campaigns for procurement and finance leaders from a brief, such as a spend-cube benchmark report, an e-invoicing mandate briefing or a webinar on supplier risk: the segment, subject lines, body and send schedule, checked against consent, frequency and content rules. It creates the campaign in the email platform and schedules the send once the audience and content are approved.
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 email platform: the segment's contacts with consent status, recent sends and suppression lists..
- 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 email platform: it creates the campaign and schedules the send. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The email playbook: segments by role and industry, consent rules by country for business contacts, frequency caps, the rules for naming clients and for savings claims, and the content calendar.
Reads from
the email platform: the segment's contacts with consent status, recent sends and suppression lists.
Acts in
the email platform: it creates the campaign and schedules the send.
Hands back
An object with name, segment, audience_count, excluded (a list with reason and count), subject_lines (a list), body, send_at (YYYY-MM-DD HH:MM) and flags (a list).
Asks a person when
The send reaches 5000 contacts or more, includes an offer, goes to contacts whose consent is not recorded, or the content names a client or a savings figure.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Emails per contact per week | 2 | No contact gets more marketing email than this. |
| Send that needs approval (contacts) | 5000 | A send to this many contacts or more needs the approver. |
| Require double opt-in where the law asks | On | When on, contacts in countries that need it are sent only after double opt-in. |
| Longest subject line (characters) | 60 | Subject lines stay within this. |
| Exclude contacts at suppliers in live sourcing events | On | When on, supplier contacts bidding in a sourcing event we run are left out of marketing sends. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Send only to contacts with recorded consent; when on is true, honour double opt-in where the country requires it.
- No contact gets more than 2 marketing emails a week.
- When on is true, contacts at suppliers bidding in a sourcing event we run are excluded, to keep the event clean.
- Subject lines stay within 60 characters; every email has an unsubscribe and our postal address.
- A client or a savings figure appears only with the client's written approval.
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.