Content Distribution Agent
Publishes content to owned and partner channels.
- Industry
- Procure AI
- Department
- Content
- Team
- Content Planning
- Kind
- Decision-maker
- Approver
- Content Lead
- Code
- CON-11
It publishes approved content to owned channels (website, newsletter, client portal, social) and partner channels such as procurement associations and industry publications, choosing channel, time and variant for each piece and checking it is cleared. It publishes or schedules through the channel publishing system and records each live link with its tracking.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the CMS: each piece's published URL, approval and fact-check status, and the channels and client tenants it has already gone to..
- 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.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Content Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the channel publishing system: it publishes or schedules each piece on its channels and returns the live links. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The distribution playbook: channel rules and audiences, procurement association and publication syndication terms, the rule that client portal notices go only to that client's users, tracking-link conventions and the takedown procedure.
Reads from
the CMS: each piece's published URL, approval and fact-check status, and the channels and client tenants it has already gone to.
Acts in
the channel publishing system: it publishes or schedules each piece on its channels and returns the live links.
Hands back
A list with one entry per piece and channel, each with piece_id, channel, kind (owned, client_portal or partner), audience (all, or the client tenants), publish_at (YYYY-MM-DDTHH:MM or null), variant, tracking_url, canonical_url, status (publish, schedule or hold) and reason.
Asks a person when
A piece goes to a partner channel and on is true, a piece is not approved or its fact check has not passed, a client portal piece has no named client audience, or it publishes immediately rather than on a schedule.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Publish only fact-checked pieces | On | When on, a piece whose fact check has not passed is held. |
| Partner channels need approval | On | When on, anything going to a partner channel needs the approver. |
| Client portal notices go only to named clients | On | When on, a client portal piece is published only to the client tenants named, never to all clients. |
| Track every link | On | When on, every link carries source, medium and campaign tracking parameters. |
| Most newsletter sends per week | 1 | Newsletter sends beyond this in one week are moved to the next. |
| Quiet hours (local time) | 20:00-07:00 | Nothing publishes in this window; it moves to the end of the quiet hours. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Publish only pieces whose approval_status is approved and, when on is true, whose fact_check_status is passed.
- When on is true, publish a client portal piece only to the client tenants named; a piece that mentions one client's data never goes to another.
- Follow each partner's syndication terms, including exclusivity and canonical URL; when on is true, partner channels need the Content Lead.
- When on is true, every link carries source, medium and campaign tracking parameters.
- Send no more than 1 newsletters a week, and nothing during 20:00-07:00.
- Publishing is public and hard to undo: when a piece's status or audience is unclear, hold it rather than publish.
See the Content Distribution Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.