Adding Prompts to the Meltwater Agent for Microsoft Teams
You can create new prompts in the Meltwater Agent for Microsoft Teams and save them either to your personal library (User Prompt Tab) or the company library (Company Prompts) for broader use. Establishing clear naming, categories, and audiences will make it easier for your team to find and use these prompts consistently.

Creating a New Prompt
Follow these steps to create and save a prompt:
-
Click + Create a Prompt
-
This opens the setup screen for adding a new prompt.
-
-
Title Box
-
Add a clear title.
-
We recommend using a naming convention that includes your team name, use case, and date created.
-
Example: “CommsTeam – Crisis Response – Feb2025”
-
-
Category
-
Click on Category box and choose or create a category.
-
To create a new category, type the category name then select +Add item.
-
-
If no categories exist yet, set up categories by use case (e.g., Crisis, Campaign, Daily Reporting).
-
This helps organize prompts into meaningful groups.
-
-
Content
-
Type the full text of the prompt.
-
Insert placeholders such as: {Brand Name}, {Competitor}, {Timeframe}, {Location}, {Topic}.
-
Placeholders make the prompt reusable across multiple scenarios.
-
Check the Example Template section (located under Category) for a suggested structure if you’re not sure where to start.
-
-
Audience
-
Select the intended audience.
-
If no audiences are listed, create one for each team that will use Copilot (e.g., LinkedIn Team, Communications Team, Marketing Team).
-
This makes prompts easier to filter and discover later.
-
-
Share Level
-
Choose whether the prompt should be:
-
User – Saved to your personal library only.
-
Company – Shared with the Company Prompt Tab so the entire organization can access it.
-
-
-
Mark as Favorite
-
Toggle this on if you’d like the prompt to appear in your Favorites tab for quicker access.
-
Prompt Governance Best Practices
To keep your Prompt Library organized and useful, we recommend setting some governance guidelines:
-
Naming conventions: Agree on a consistent format for titles (e.g., Team – Use Case – Date).
-
Categories: Define key categories up front (e.g., Campaign, Reporting, Crisis, Trend Analysis) so prompts are easy to browse.
-
Audiences: Create audience groups by function or team to avoid clutter.
-
Company vs. User level: Decide which prompts should be widely available vs. kept personal. Encourage teams to share prompts that have broad value.
-
Review process: Establish periodic reviews of the Company Prompt Tab to retire outdated prompts and maintain quality.
