- Industry
- Insure AI
- Department
- Content
- Team
- Content Planning
- Kind
- Decision-maker
- Approver
- Head of Content
- Code
- CON-09
It schedules insurance content across the website, app, email, broker portal and social channels, around renewal waves, product launches and weather or catastrophe events. It holds promotional posts during a declared catastrophe, keeps review lead times for compliance and writes the approved schedule to the content calendar.
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 document and correspondence system: the items in compliance review and their approval status, and the renewal and rate-change notice dates..
- 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 Head of Content with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the document and correspondence system: it writes the approved items to the content calendar with their publish times. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The channel plan, posting limits by channel, compliance review lead times, the renewal and launch calendar, and the catastrophe communications protocol.
Reads from
the document and correspondence system: the items in compliance review and their approval status, and the renewal and rate-change notice dates.
Acts in
the document and correspondence system: it writes the approved items to the content calendar with their publish times.
Hands back
A list with one entry per item, each with title, channel, kind, publish_at (date and time), status (scheduled, held or moved) and reason.
Asks a person when
The schedule moves or holds a regulatory notice, pauses promotions for a catastrophe, or schedules an item before its compliance review closes.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most items per channel per day | 2 | No channel gets more than this many items a day. |
| Hours between items on the same product | 48 | Items about the same product line are spaced at least this far apart. |
| Compliance review lead time (days) | 5 | Promotional items are scheduled no sooner than this after they enter review. |
| Pause promotions during a declared catastrophe | On | When on, promotional items in an affected region are held while a catastrophe event is declared, and claims-help items go first. |
| Timezone | America/New_York | The timezone for all dates and times. |
| May move fixed dates | Off | When off, items with a fixed date, such as a rate-change notice, are never moved. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Schedule no more than 2 items per channel per day and space items on the same product line by at least 48 hours.
- Schedule a promotional item no sooner than 5 days after it entered compliance review, and never before it is approved.
- When on is true, hold promotional items for an affected region during a declared catastrophe and put claims-help items first.
- Rate-change and renewal notices keep their regulatory notice dates; when off is false, never move a fixed date.
- Give all dates and times in America/New_York.
See the Content Calendar Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.