AI UX PlaygroundNewsletterJoin 2K+ AI designers and PMs on Substack. New teardowns, patterns, and prompts as they drop.

Chatbot

Conversation Templates

Save reusable chat starters: roles, constraints, and first prompts. Launch a proven setup in one tap instead of rebuilding the scaffolding every time.

Interactive demo

Overview

How might we design conversation templates so people can trust and act on AI output?

When to use

  • Ideal for power users, professionals, and teams who have established workflows and want to standardize their AI interactions.

When to skip

  • Completely open-ended chat with no repeating workflows.
  • Templates that go stale faster than teams will maintain them.
  • Compliance contexts where every chat must start blank for audit reasons.

Rules

  • Templates that hide the underlying prompt from the user.

  • No way to fork and customize a template.

  • Marketplace templates that request tools without disclosure.

  • Overwriting a shared template without version notes.

Evidence

ProductImplementation
ChatGPTCustom GPTs and starter prompts as reusable setups.
ClaudeProjects and prompt starters for repeat workflows.
Notion AISaved prompts and templates for recurring docs.
JasperTemplate galleries for marketing chat flows.

FAQ

What belongs in a conversation template?

System or role instructions, starter user prompt, default tools, and optional example outputs, visible to the person launching it.

How do templates differ from prompt libraries?

Prompt libraries are copy-paste strings. Conversation templates launch a full chat configuration, sometimes with tools and memory scope.

Who can edit shared templates?

Owners and admins; everyone else should fork. Show last updated and publisher.

When should a product suggest creating a template?

After a user repeats a similar opener or stars a successful thread.