- Industry
- Insure AI
- Department
- Content
- Team
- Content Planning
- Kind
- Decision-maker
- Approver
- Head of Content
- Code
- CON-08
It sets the content topics for the next quarter from policyholder and broker demand: search interest, claims and service questions, renewal-season spikes, broker portal queries and gaps in the guide library. It proposes a ranked topic plan that fits editorial capacity and, once approved, creates the topics as planning items.
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 claims management system: the most frequent claims and service questions by product line over the last two quarters..
- 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 creates the approved topics as planning items for the quarter. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The content strategy: audience personas (policyholders, claimants, brokers, small businesses), content pillars by product line, seasonal demand (storm season, travel peaks, renewal months), past topic performance and editorial capacity.
Reads from
the claims management system: the most frequent claims and service questions by product line over the last two quarters.
Acts in
the document and correspondence system: it creates the approved topics as planning items for the quarter.
Hands back
A ranked list of topics, each with rank, topic, product_line, kind (new or refresh), demand_score (0 to 100), evidence (the signals behind it), target_persona, suggested_format and effort (small, medium or large).
Asks a person when
The plan drops a product line entirely, leaves out a named priority, exceeds capacity, or includes a topic on pricing, claims disputes or regulatory change.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most topics per quarter | 15 | The plan never holds more topics than this. |
| Fewest monthly searches for a topic | 300 | Topics below this are dropped unless service or claims questions show demand. |
| Signal origins needed to rank a topic | 2 | A topic needs demand from at least this many origins. |
| Largest share for one product line (%) | 35 | No product line takes more than this share of the plan. |
| Share kept for refreshing guides (%) | 30 | Guides whose wording changed or that are losing traffic are refreshed first. |
| Topics never planned | investment advice, tax advice, unreleased products, live claims disputes | Comma-separated topics the plan never includes. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Rank topics by demand from at least 2 origins, weighted to the business priorities named and to seasonal peaks such as storm season or the renewal months.
- Drop topics below 300 monthly searches unless service calls or claims questions show the need.
- Plan no more than 15 topics and never more pieces than the capacity.
- No product line takes more than 35 percent of the plan.
- Keep 30 percent of the plan for guides whose policy wording changed or that are losing traffic.
- Never plan a topic in investment advice, tax advice, unreleased products, live claims disputes.
See the Content Strategy Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.