Saved Prompts with Variables

If you find yourself continuously pasting the same “write a delay notice for shipment X” request into Solace Agent Mesh chats, use saved prompts with variables.

Prompts live under Assets > Prompts. There are two ways to make one: Create Manually, or Build with AI, where you describe the prompt (or paste an existing one) and it drafts a reusable template.

Building one with AI

I described: “A prompt that asks an agent to draft a delay notice email to a Northwind Freight customer, given the shipment ID, the new ETA and the reason for the delay. Tone: apologetic but brief.” It came back with a name, a tag, a /delay-notice shortcut, and content with placeholders. I then asked it to “add an optional field for a discount code” in the same chat, and it updated the draft.

The placeholder syntax is {{Variable Name}}, spaces and all:

Use the following details:
- Shipment ID: {{Shipment ID}}
- New Estimated Arrival Date: {{New ETA}}
- Reason for Delay: {{Delay Reason}}
- Discount Code (optional): {{Discount Code}}

Using it in a chat

Type / in the message box and a picker opens. Search by name or shortcut.

Pick a prompt that has variables and you get a small form with one field per placeholder. Fill them in, Insert Prompt, and the finished text lands in the message box for you to tweak before sending.

Things worth noting:

  • The Chat Shortcut only takes letters, numbers, hyphens and underscores, and must be unique across your prompts.
  • In my build the grouping field is Tag with a fixed list (Development, Analysis, Documentation, Communication, Testing, Other), not a free-text category, so plan your naming around search.
  • Share is on each prompt’s actions menu. You add people by email as Viewer (can use it) or Editor (can also save new versions). Only the owner can delete or reshare, and deleting removes it for everyone. If you don’t see Share, sharing is turned off for your deployment.

Docs:

If you want to build your own prompt library, download the Solace Agent Mesh desktop app; the prompts you save there work with any agent.

Which request do you type most often that should be a saved prompt?

The one I’d save first is a weekly status rollup: “Turn these notes into three bullets for a non-technical stakeholder, flag anything blocked,” with {{Team}} and {{Week Ending}} placeholders. Second would be a customer-facing incident update with {{Incident ID}}, {{Current Status}} and {{Next Update Time}}. A small question on optional fields like the discount code: if you leave one empty at insert time, does the message box get a blank line or the literal placeholder left in? Knowing that would shape where I put optional placeholders in the template.