Email assistant prompts that match tone and context

Last updated April 2026

An email assistant prompt defines how an LLM drafts, replies to, or summarizes emails — matching the sender's tone, incorporating relevant context, and following organizational communication norms.

Why structured prompts for email assistant

Email prompts need to handle wildly different contexts: a reply to an angry customer needs a different tone than a follow-up to a sales prospect. Structured blocks let you separate the stable parts (brand voice, safety rules, formatting) from the dynamic parts (context, tone matching, specific instructions).

The role block sets the default communication style. The context block receives the email thread, sender relationship, and any CRM data. The instructions block handles the specific task — draft a reply, summarize a thread, or compose a new message. The guardrails block prevents sensitive information from leaking into replies.

This separation is especially important for email because the stakes are high: a poorly worded email goes directly to a customer, partner, or colleague. Guardrails like "never include pricing not approved by sales" and "never commit to timelines without checking with the team" prevent costly mistakes.

Example prompt structure
roleEmail Composer
You are an email assistant for {{user_name}} at {{company_name}}. Match the formality level of the incoming email. Default to professional-friendly tone.
contextThread & Relationship
Email thread: {{email_thread}}. Sender relationship: {{relationship}}. Previous interactions: {{interaction_history}}. Relevant context: {{additional_context}}.
instructionsDrafting Guidelines
1. Reference specific points from the incoming email to show you read it.
2. Address all questions or requests raised.
3. Keep replies under 200 words unless the topic requires more.
4. Include a clear next step or call to action.
5. Suggest a subject line if composing a new email.
guardrailsCommunication Boundaries
Never share pricing, contracts, or terms not approved by the sales team. Never commit to deadlines or deliverables on behalf of other teams. Flag when an email should be reviewed by legal before sending.
Benefits of structured email assistant prompts
  • Tone matching adapts to each email's formality level automatically
  • Context blocks inject CRM and thread history for relevant replies
  • Safety guardrails prevent unauthorized commitments or data leaks
  • Non-technical team members can update communication guidelines independently
  • Version control tracks how email guidelines evolve across the organization
Frequently asked questions
The role block instructs the LLM to match the incoming email's formality level. Combined with the context block's sender relationship data, the LLM adapts its tone — formal for executives, casual for teammates.
Yes. Create separate prompts per department with different role and guardrails blocks. Sales gets one communication style, engineering another, each managed independently in their own project.
Related use cases

Customer Support

A customer support prompt defines how an LLM-powered support agent handles user inquiries — setting the tone, enforcing escalation rules, grounding responses in product knowledge, and formatting replies consistently across channels.

Content Writing

A content writing prompt defines how an LLM generates articles, blog posts, or marketing copy — enforcing brand voice, SEO requirements, content structure, and editorial constraints through typed blocks.

Data Analysis

A data analysis prompt instructs an LLM to interpret raw data, identify patterns, generate statistical summaries, and produce actionable insights — with structured output that downstream systems can parse.

Build your email assistant prompt.

Start with this template or compose from scratch with typed blocks. Free to get started — no credit card required.

Start building freeAll use cases