One message, many audiences

A big announcement is coming — a strategy shift, a product launch, a policy change. There’s one decision behind it, but a dozen audiences who each need it told differently. Marketing needs an action plan. Customers need a plain-language briefing with answers to the obvious questions. Field teams need a single page they can act on. Leadership needs the version that ties it all together.

The risk is drift. By the third rewrite, the customer FAQ is quietly saying something the field one-pager contradicts, and nobody can tell which version is right. This walkthrough shows you how to start from one source of truth, generate every audience-specific version from it in a single thread, deliver each one to the right place, and keep a complete trail of what came from what — so the message stays consistent no matter how many ways you tell it.

What you’ll need

• The source briefing that everything derives from — the strategy memo, launch brief, or decision document. PDF, Word, text, or Markdown all work.
• A clear list of your audiences and where each one lives: a team Folder, a customer Channel, a field-ops group.
• A few minutes to set up a Collection and a Folder the first time. After that, generating a new audience version takes one prompt.

The flow at a glance

1. Upload your source briefing to a Knowledge Collection and share it.
2. Open a shared conversation in a Company Communications Folder and link the Collection.
3. Generate an internal action plan for one team — share it to their Folder or Channel.
4. Generate a customer-facing briefing with FAQs — share it to the customer Channel.
5. Generate a one-page field-ops version — share it to field ops.
6. Keep working in one thread so every version traces back to the same source.

---

Step 1 — Make your briefing the single source of truth

A Knowledge Collection is a curated set of documents Chat can read and cite. Putting your source briefing in a Collection — rather than pasting it into a chat — is what makes it the single source of truth: every version you generate is grounded in the same document, and each one carries citations back to it.

1. Open Knowledge in the sidebar and create a new Collection. Name it for the announcement — for example, 2026 Strategy Briefing.
2. Upload your source briefing. Drag it in or use Add Source. Chat accepts PDF, DOC/DOCX, XLS/XLSX, PPT/PPTX, CSV, TXT, Markdown, and more, up to 100 MB per file. The file is read, broken into sections, and indexed so Chat can search and cite it.
3. Add any supporting material that should stay consistent across audiences — your approved messaging, a glossary, brand do’s-and-don’ts. Every version will draw on the same set, so wording and terminology stay aligned.

Share the Collection. Open the Collection’s access settings and grant access to the people who’ll work on the rollout — specific colleagues, a group, or your whole organization. Now everyone is generating from the same approved source, not their own copies.

One source, then never edit the copies

The whole point is that the source lives in one place. When the briefing changes, update the document in the Collection — don’t patch each audience version by hand. Re-generate from the updated source and your downstream versions stay in sync automatically.

Learn more in Upload a file to work with and Chat, Notes, Channels, and Knowledge.

---

Step 2 — Open a shared conversation and link the source

You’ll generate every version inside one conversation, kept in a Folder for the rollout. Doing it all in a single thread is what gives you the audit trail: each audience version sits in sequence, derived from the same source, in order, with the prompts that produced it.

1. Create a Folder for the rollout — for example, Company Communications. A Folder is a workspace that keeps a piece of work’s conversations, Knowledge, and settings together.
2. Link your Strategy Briefing Collection to the Folder so every chat inside it can read and cite the source.
3. Start a new conversation in the Folder and share it with your rollout team, so the people drafting alongside you see the same thread update in real time as each version takes shape.

Why one thread

Each version you create stays in the same conversation, in the order you made it. Months later anyone can open this thread and see exactly which audience version came from which prompt, all tracing back to the one briefing. That sequence is your record of how the message was adapted — no separate change log to maintain.

See Find and organize your conversations for more on Folders and sharing.

---

Step 3 — Generate the internal action plan (e.g. Marketing)

With the source linked, ask for the first audience version: a functional action plan for a specific team. Be explicit about who it’s for and what they need to do.

Example prompt

“Using the 2026 Strategy Briefing, write an internal action plan for the Marketing team. Pull out what this strategy means for marketing specifically, then lay out concrete workstreams, owners-by-role, milestones, and dependencies. Keep it action-oriented — what Marketing needs to start, stop, and change.”

Chat reads the briefing from your Collection and produces a marketing-focused plan, with citations back to the parts of the source each point came from. You’ll see it work through its steps — gathering information, building context, composing the response — and then the plan appears.

Polish it without re-typing instructions. Below the response you’ll find quick action buttons:

Button	Use it when
Refine this	The plan is close but needs tighter wording or smoother flow.
Explain more	A workstream is too thin and needs more detail.
Try different approach	The framing isn’t landing and you want a fresh take.

Deliver it to Marketing. Once it reads right:

• Share this conversation, or post the plan into the Marketing Folder or Channel, so the team sees it where they already work.
• Or Copy it straight into your project tool, or Export it as PDF or Markdown.

For shaping written output, see Draft emails and documents.

---

Step 4 — Return and generate the customer-facing briefing with FAQs

Now switch audiences — in the same conversation. Don’t open a new chat; staying in this thread is what keeps every version tied to the one source and to each other.

Example prompt

“Now, from the same briefing, write a customer-facing briefing. Plain, reassuring language — no internal jargon, no roadmap specifics customers shouldn’t see. Explain what’s changing and why it’s good for them. End with an FAQ of 6–8 questions customers are likely to ask, with clear answers grounded in the briefing.”

Because the source is still linked and you’re in the same thread, Chat re-uses the exact same facts — but reshapes tone, depth, and structure for an external reader, and drafts the FAQ from the same material. The meaning doesn’t move; only the telling does.

Review it carefully — this version goes outside. Use Refine this for tone, or steer in plain language:

“Make the FAQ answers shorter and warmer. Drop anything that sounds like an internal announcement. Lead with the customer benefit, not the company decision.”

Deliver it to customers. Post the briefing into your customer Channel, or copy and export it for your support and success teams to use verbatim — so everyone gives customers the same answers.

Let Chat keep your wording consistent

If your approved messaging or a glossary is in the Collection, ask Chat to use it: “Use the product names and the positioning from the messaging guide.” That’s how the customer version and the field version end up saying the same thing in the same words.

See Search the web if a version needs current public context layered on top of your briefing.

---

Step 5 — Return and generate the one-page field-ops version

Same thread, same source, one more audience. Field teams need something they can act on at a glance — short, direct, no preamble.

Example prompt

“From the same briefing, create a one-page field-ops version. Maximum one page. Lead with the three things field teams must do differently starting now. Use short bullets and a quick reference for the most common situations they’ll hit. Skip the background — just what to do.”

Chat compresses the same source into a tight, scannable page. Push it harder if you need to:

“Cut it to half a page. Turn the ‘what to do’ into a numbered checklist.”

Deliver it to field ops. Share it to the field-ops Folder or Channel, or export it as a PDF they can keep open while they work.

---

Step 6 — The audit trail is already built

You don’t have to assemble a record — you made one as you went. Your single conversation now holds, in order:

1. The marketing action plan
2. The customer briefing and FAQ
3. The field-ops one-pager

…each one generated from the same linked briefing, each prompt visible above the response it produced, each version carrying citations back to the source. Anyone with access to the thread can see exactly how one decision became multiple audience-specific messages — and confirm that none of them drifted from the original.

To keep this as a clean reference:

• Save the thread to a Note as a “rollout pack” you can return to.
• Export the conversation as PDF or Markdown to file alongside the announcement.
• Leave the conversation shared in the Folder so the whole rollout team works from the same record.

Step-by-step download and copy options are in Export a conversation.

---

When the source changes

Plans move. When the briefing is updated, you don’t chase down every version:

1. Update the source document in your Strategy Briefing Collection.
2. Return to the same thread and re-run each version: “The briefing was updated — regenerate the customer FAQ from the latest version and tell me what changed.”
3. Re-share the refreshed versions to each audience.

One edit at the source, propagated everywhere — and the thread records the update right alongside the originals.

---

The outcome

One decision, told several ways, with zero drift. Every audience got the version built for them — the action plan, the customer briefing, the field one-pager — and every one of them traces back to the same briefing in a single, shareable thread. Next time there’s a big announcement, the setup is already done: drop the new briefing into the Collection and you’re straight into generating versions.

Related guides

• Upload a file to work with — bring your source briefing into a Knowledge Collection.
• Draft emails and documents — write and refine each version with the response actions.
• Find and organize your conversations — Folders, sharing, and keeping the rollout together.
• Chat, Notes, Channels, and Knowledge — how Collections, Folders, and Channels fit together.