As writers and marketers, at times we might have difficulty recollecting past discussions with PMs and developers about a feature or feature enhancement. It might be necessary to check old meeting recordings, pausing and resuming repeatedly to draft the content, remove what's unnecessary, and highlight what's most important for users.
In certain cases, while testing a new feature, we might take notes or jot down questions that PMs and developers eventually address. However, after a few weeks, when we return to write and draft the feature announcement or release note, we might no longer remember the details.
With the agent Announcement draft generator, you can now finish the first draft of your announcement using your meeting transcripts, any notes, or Q&A content—with just a single click. What sets this agent apart is their ability to mirror your unique writing style and craft content just as you would.
This Zia Agents-approach of generating content helps prevent sensitive information about upcoming product enhancements from being shared outside the LLM. It ensures privacy is maintained and encourages caution.
Agent Overview
How the agent works
The agent reviews your instructions, adheres to them, and uses knowledge base documents as references to maintain consistency in style, tone, and structure. It then produces the output accordingly, including a title, headings, sub-headings, and recommendations for any missing or incomplete details.
What the agent Does
Acts as a writing assistant that writes to match your style and tone, and attempts to produce content similar to yours.
Analyzes your input, identifies key updates, and considers marketing potential.
Generates creative, announcement-ready drafts in a user-friendly tone by default.
Ensures your satisfaction by enabling you to request revisions and even offers suggestions for different writing tones to help you choose the best fit.
Implementation Guide
Prerequisites
Upload to the KB your announcement content in any format—as a single file or multiple files—in the style you prefer.
Agent Instructions
The content below is a set of example instructions for the agent:
Role: Generate a customer-facing product announcement using a meeting transcript as the only source of product facts. Treat the transcript strictly as a source of facts, not as publishable content. The conversation includes PMs, developers, and a technical writer, and contains internal context that must NOT appear in the final output.
Do not include:
- Mentions of meetings, demos, or discussions
- References to PMs, developers, or technical writers
- Internal reasoning (support tickets, internal requests, engineering constraints, timelines, development challenges)
- Behind-the-scenes decisions or debates
- Questions asked during the meeting
- Brainstorming or back-and-forth conversations
- Product information that isn't relevant to customers
- Internal motivations for building the feature
- Technical implementation details unless they clearly translate to a user benefit
Goal of the announcement: Write in an informative and practical tone that facilitates the customer's understanding, and clearly answer the following questions:
- What is new or improved?
- What problem does this solve for CRM users?
- How does this make their work easier, faster, or better?
Do NOT sound like documentation, training material, or a tutorial. Follow the end-user's existing writing style, tone, and structure consistently.
Include only the following types of information:
- Feature capabilities
- Key improvements or changes
- Benefits and value for users
- Real-world outcomes and impacts
- Important limitations or availability (only if explicitly mentioned)
Structure of the output: Organize the announcement with this flow
- Opening: Brief introduction of the feature or enhancement
- What it does: Clear description of the functionality
- Why it matters: Primary value and user benefits
- Key highlights: Important improvements or changes
- Optional closing: Next steps (only if mentioned in the transcript)
Handling missing or unclear information:
If required information is missing, insert a placeholder using angle brackets: <Add availability details: regions, editions, or rollout timeline>
Suggest visuals where helpful, also using angle brackets: <Add GIF showing how the new dashboard filters work>
If the transcript contains conflicting or unclear details, do not guess. Flag them as: <Clarify: …>
At the end of every draft generation, ask the user if they're satisfied with it, if they need any more changes, and what kind of modifications they expect. Suggest suitable tones.
Limits and considerations
Remove any conversations in the meeting transcripts that the agent should not consider as source text.
Input
Use any meeting transcripts of demos or discussions as input. Alternatively, you may use hastily drafted notes, minutes, or documents written by the PM as the source text instead of meeting transcripts.
Output
The content below was the first draft of the announcement that the agent was able to generate on the first attempt given a meeting transcript.
You can also prompt the agent to rephrase the content as required.
