Skip to main content
Saved prompts let you capture effective prompts and reuse them across your team. Build a shared library of the prompts that work best for your contract review workflows. Learn more about building effective saved prompts. There are two ways to save a prompt:

​
From the prompt library

  1. Open the prompt library from Composer
  2. Click New prompt
  3. Enter a name, description, tags, and the prompt text
  4. Optionally attach reference files
  5. Save

​
From a chat message

Organization admins can save any user message in the chat thread as a prompt, which is the fastest way to capture a prompt that already worked well.
1

Find the message

In the Composer chat thread, hover over the user message you want to save.
2

Click the bookmark icon

Click the bookmark icon on the message. The Save prompt drawer opens, pre-filled with the message text and any files that were attached to the chat message.
3

Add metadata and save

Add a name, description, and tags, then save. The prompt — including its attached files — becomes available to your whole organization in the prompt library.
Only organization admins see the bookmark icon on chat messages. Saved prompts are shared across the organization.

​
Using a saved prompt

  1. Open Composer in Word or the web app
  2. Click the prompts icon or type / to open the prompt picker
  3. Filter by tag or search by name
  4. Select the prompt to insert it into the chat input
When you pick a prompt that has reference files attached, those files are auto-attached to your chat so the AI has the same context the prompt’s author intended.

​
Filtering by tag

The prompt library supports multi-select tag filtering. Select multiple tags to see prompts matching any of them, or click All to clear the selection.

​
Tips for good saved prompts

  • Use a descriptive name so teammates know when to use it
  • Add tags so prompts are easy to find
  • Include reference files when the prompt depends on specific context (templates, fallback language, etc.)
  • See Create Good Saved Prompts for detailed guidance When creating or editing a prompt, click Enhance prompt to have AI improve your prompt text. You can undo the enhancement to restore your original text.

​
File attachments

You can attach files to a saved prompt. When you or a teammate selects that prompt from the library, the attached files are automatically included in the chat. This is useful for prompts that reference specific templates, precedent documents, or guidelines.

​
Finding and using saved prompts

Open the Prompt Library from Composer to see all your saved prompts. Click any prompt to insert it into the chat along with any attached files. Manage your saved prompts

​
Editing and deleting prompts

Organization admins can edit or delete saved prompts:
  • Edit — update the title, text, notes, tags, or file attachments
  • Delete — permanently remove a prompt from the library (confirmation required)
LOIS for Word official prompts are read-only and cannot be edited or deleted.

​
Using with playbooks

Saved Prompts work with playbooks:
  • Add prompts for recurring tasks like clause reviews or risk summaries
  • Share across client profiles or deal types
  • Keep your team reviewing contracts with the same language and standards

​
Best practices

  • Use actionable titles so teammates know when to use a prompt
  • Use tags to categorize prompts (e.g., Review for review workflows, Drafting for document creation)
  • Add internal notes to explain when and how to use a prompt
  • Attach reference files so they’re always included with the prompt
  • Add tone or role guidance (“cooperative negotiation style,” “outside counsel perspective”)
  • Refine and overwrite prompts as you learn what works
Learn more about building a prompt library.

​
Prompt syntax

Prompts are written in Markdown format. Markdown provides clear structure that helps the AI understand your intent. You can learn more at the Markdown Guide. Markdown basics:
  • Section headers using # symbols
  • Bulleted lists using - or *
  • Numbered lists using 1., 2., etc.
  • Code blocks using triple backticks
  • Links using [text](url)