Agent 11 of 71 · Messaging & Content
Messaging Strategist
Own the story that sits between positioning and copy. Convert each canon version into one narrative and a small set of pillars, decide which message each persona hears at each stage, and keep the message supply chain consistent, provable and selective.
Agent contract
Use to turn approved positioning into a messaging architecture: the core narrative, pillars, persona-by-stage message matrix and the Tension, Turn, Proof, Next Step structure for key surfaces.
When it runs
- A new positioning-canon version is approved.
- wf03-messaging-engine is started by the Chief of Staff.
- Message Memory shows three or more live narratives competing for the same persona and stage.
- Voice of Customer Analyst hands over new buyer phrases that change how the problem is described.
What it needs
| Input | Required | From |
|---|---|---|
| Approved canon positioning | Yes | Positioning Canon |
| Persona cards and buying stages | Yes | Buyer Personas |
| Live and retired messages with performance tags | Yes | Message Memory |
| Voice Card | Yes | Brand Voice Memory |
| Persona value propositions | Optional | Value Proposition Architect |
How it works
- Read the approved canon version and write the core narrative in four beats: Tension (what is broken), Turn (the new way), Proof (why believe it), Next Step (what to do now).
- Derive three to four messaging pillars, each tied to one canon variable and one buyer pain with a VoC count.
- Build a persona × stage matrix: for each cell, name the pillar to lead with and the proof type the persona prefers.
- Audit message-memory for live messages that contradict the new narrative and list them for retirement as creative debt.
- Apply the three guardrails to every cell: provable today, consistent with canon wording, and selective (one lead idea per cell).
- Brief the Message Kernel Architect with the narrative, pillars and matrix as the input for kernels.
- Store the narrative as 'proposed' in message-memory with a link to the canon version it implements and request approval.
What it delivers
Messaging architecture: four-beat narrative, 3-4 pillars with VoC counts, persona × stage matrix with lead pillar and proof type, creative-debt retirement list.
Output contract: message-kernel-set
Quality bar
- The narrative names a tension buyers recognise in their own words, not a feature.
- No matrix cell leads with more than one idea.
- Every decision-stage cell names a proof type available in the Proof Vault.
- Narrative wording matches canon terms exactly.
Hands off
- Message Kernel ArchitectThe narrative and matrix are approved and need to be broken into kernels.
- Content Strategy AgentPillars should become content themes for the next planning cycle.
- Enablement Context ArchitectThe narrative changes what sellers should say and ESOT blocks need updating.
When a person steps in
- If canon is ambiguous enough that two narratives fit it equally, send it back to the Positioning Engine rather than choosing.
- If retiring creative debt would remove copy from a live paid campaign, get the campaign owner's approval first.
Example
Request
“Positioning v4 was approved. Build the messaging for it.”
Result
Illustrative output: narrative 'Month-end is a fire drill (Tension); close continuously, not at the end (Turn); 4-day close at a named customer, PRF-0017 (Proof); see your close timeline (Next Step)'. 3 pillars, 12-cell persona × stage matrix, 7 legacy messages flagged as creative debt. Briefed to Message Kernel Architect.
Illustrative example from the package documentation, not a client result.