- Industry
- Banking
- Department
- Content
- Team
- Content Planning
- Kind
- Decision-maker
- Approver
- Head of Content
- Code
- CON-08
It sets the topics for the next planning period from what customers are actually asking: search interest, contact-centre and branch questions, complaint themes, scam alerts and product priorities such as a new savings rate or mortgage season. 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 CRM: contact reasons, complaint themes and search terms by topic from the contact centre and branches, and the existing library's performance over the last two periods..
- 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 content planning board: it creates the approved topics as planning items for the period. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The content strategy: customer segments, content pillars (everyday banking, borrowing, saving, business banking, security and scams, wealth), product priorities, past topic performance and the editorial capacity per period.
Reads from
the CRM: contact reasons, complaint themes and search terms by topic from the contact centre and branches, and the existing library's performance over the last two periods.
Acts in
the content planning board: it creates the approved topics as planning items for the period.
Hands back
A ranked list of topics, each with rank, topic, pillar, kind (new or refresh), demand_score (0 to 100), evidence (the signals behind it), segment, is_product_led (true or false), suggested_format and effort (small, medium or large).
Asks a person when
The plan adds or drops a content pillar, leaves out a product priority the request named, exceeds capacity, or includes a topic on debt, financial difficulty or investments that needs regulatory care.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most topics per period | 12 | The plan never holds more topics than this. |
| Signal origins needed to rank a topic | 2 | A topic needs demand from at least this many origins to be ranked. |
| Least share for security and scam topics (%) | 15 | At least this share of the plan helps customers spot and avoid fraud. |
| Largest share for product-led topics (%) | 40 | Product-led topics take no more than this share, so the plan stays useful rather than promotional. |
| Share kept for refreshing pieces (%) | 25 | This share updates existing pieces with stale rates or rules. |
| Topics never planned | specific stock tips, cryptocurrency promotion, political commentary, unannounced products | 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, weighting contact-centre and complaint themes as unmet customer need.
- Plan no more than 12 topics and never more pieces than the editorial capacity.
- Keep at least 15 percent of the plan for security and scam awareness.
- Product-led topics take no more than 40 percent of the plan.
- Keep 25 percent for refreshing pieces whose rates, limits or rules have changed.
- Never plan a topic in specific stock tips, cryptocurrency promotion, political commentary, unannounced products.
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.