Living Messaging Doc

The Living Messaging Doc is a routine your Townie AI assistant runs after customer and prospect calls: it reads each transcript for the jobs, pains, objections, and exact phrases customers voice, then updates a per-segment messaging doc — every insight attributed, every quote kept verbatim.

To: your Townie

Subject: Create me a Living Messaging Doc routine

Build me a routine that keeps my messaging and positioning grounded in what customers actually say — so my copy uses their language, not mine, and I never lose a great line from a call.

Run it after each customer or prospect call (when the recording/transcript is ready), plus a nightly sweep to catch anything missed.

When it runs on a call:
- First decide if it's really a customer/prospect conversation worth mining — skip internal meetings and logistics calls.
- Pull the voice-of-customer signal: the jobs they're trying to get done, their pains, the objections they raised, the exact words they use for the problem, which of my messages landed or fell flat, and short verbatim quotes worth keeping.
- Sort each customer into the right segment and fold what you learned into a living messaging doc for that segment — strengthening recurring themes rather than duplicating.
- Keep two lanes strictly separate: a messaging lane (jobs, pains, objections, what lands, proof points, quotes) and a product-feedback lane (bugs, requests, pricing gripes) logged at the bottom with attribution — never mixed.
- Attribute every insight (who, company, date) and keep a sources list linking back to the call notes.

Details that matter:
- Ask me up front for my segment list and doc format — I already run a version of this and the new one should inherit that structure, not reinvent it.
- One call is evidence, not gospel — frame single-call claims as observed; let repeated signal harden into confident statements.
- Never invent or paraphrase a quote.

Output: the updated per-segment messaging doc(s), plus a short recap of what was added where.

My default: update my messaging docs on your own, but check with me before writing to any outside system, like tagging a persona in my CRM.

Before you build this, tailor it to the tools I actually use and ask me the questions that would make it stronger — including what to do on your own vs. check with me first.

Sent when you sign up — works as-is, or edit anything.

1,960 / 2,000

Get started with this routine

It updates your internal docs — outside systems wait for your okay.

See it work: a call becomes sharper messaging

Update my positioning docs with the words customers use

Quotes stay verbatim and attributed — never invented.

How this routine works

Works with

It runs when a call wraps
As soon as a customer or prospect call's transcript is ready, your Townie decides whether it's worth mining — internal meetings and logistics calls get skipped, and a nightly sweep catches anything missed.
It reads for voice-of-customer signal
Jobs, pains, objections, the exact words buyers use, and which of your messages landed — sorted into the right segment, with product feedback logged in its own lane.
Your messaging doc stays alive
Each segment's doc absorbs the new evidence: recurring themes harden into confident statements, single calls stay marked as observed, and you get a short recap of what changed.

Living Messaging Doc FAQ

It's a routine your Townie AI assistant runs after customer and prospect calls: it reads the transcript for the jobs, pains, objections, and exact phrases customers voice, then updates a living messaging doc for that segment — quotes verbatim, every insight attributed to who said it and when. You set it up once by describing it; the message on this page is that description.

Not without asking. It updates your internal messaging docs on its own; anything outside them — like tagging a contact's persona in your CRM — waits for your approval. Read more in our security overview.

No. Quotes are kept short and faithful, never invented or paraphrased. And one call is evidence, not gospel — single-call claims stay framed as observed until repeated signal across calls hardens them.

Yes — it asks up front for your segment list and the section format you already use, then inherits that structure instead of reinventing it. New learning merges into what's there rather than duplicating it.

A meeting-notes source for call transcripts, somewhere your docs live (like Google Drive or Notion), and optionally your CRM for matching people to segments. Your assistant adapts the routine to whatever you've connected.