I Built an Email Assistant Gem — Here's What It Actually Does

A Gemini Gems conversation interface showing an email draft being refined with tone suggestions in a clean minimal design
Part of the "My AI Team" Series — Each post covers one specific Gem I use daily. See the full series overview.

I write a lot of email. Vendor negotiations, client updates, internal escalations, requests that need a careful tone. Most of it is straightforward, but a handful of messages each week require more thought — the ones where the wrong word choice could create friction or confusion. My Email Assistant Gem helps with those.


What Is an Email Assistant Gem?

It's a Gemini assistant configured to draft, refine, and review professional email. You describe what you need to communicate, or paste in a draft, and it produces clean email copy calibrated to your relationship with the recipient and the outcome you're trying to achieve.


Why I Built This Gem

The use case isn't volume — it's judgment. A few categories of email benefit from a second opinion:

  • Escalation emails: need to be firm without burning the relationship
  • Vendor pushback: need to be direct about a problem without triggering defensiveness
  • Status updates to non-technical stakeholders: need to translate technical reality into language that lands right

For those, I describe the situation and what I want the recipient to walk away with, and the Gem drafts accordingly.


The Prompt I Use

You are my email assistant. You draft and refine professional email for different audiences and purposes. When I describe an email I need to send: - Draft it in a tone appropriate to the relationship and objective I describe - Keep it concise — get to the point by the second sentence - Avoid filler phrases and corporate-speak - Offer one alternative version if the tone could reasonably go different ways - Flag if something I'm about to say could land poorly My context: IT infrastructure professional. Regular recipients include: vendors, clients, internal stakeholders with varying technical backgrounds. Default tone: direct and professional, not formal.

Real Examples — What I Actually Ask It

  • "I need to tell a vendor that their SLA response time is unacceptable without ending the contract negotiation. Draft that."
  • "Write a project status update for a non-technical client that explains we hit a delay without making it sound like we don't know what we're doing."
  • "Here's an email I'm about to send to push back on a pricing proposal. Does the tone work or does it read as aggressive?"

For the SLA email, it produced a draft that named the problem specifically, referenced the contract terms without quoting them verbatim (which reads as adversarial), and ended with a clear ask rather than a vague complaint. I sent it with minimal changes and the vendor responded constructively.


What It's Good At (and Where It Falls Short)

Good at:

  • Drafting emails where tone judgment matters
  • Translating complex situations into clear, appropriately-toned messages
  • Reviewing drafts for unintended tone problems
  • Offering alternative framings when the right approach isn't obvious

Where it falls short:

  • It doesn't know the history of your relationship with the recipient — you need to provide that context
  • It can default to slightly too-formal language if you don't specify the relationship explicitly
  • For highly sensitive internal communications, human judgment on tone is still essential

Try It Yourself — Starter Prompt

You are my email assistant. Draft professional email in a tone I specify. Keep it concise. Avoid filler phrases. Flag anything that could land poorly. Offer an alternative version when the tone could reasonably differ. My context: [your role, typical recipients, your default communication style]

Paste this into a new Gem at gemini.google.com and test it with a message you're currently drafting.



Related Posts


Sources & Further Reading


Do you use AI to help draft professional email? What kinds of messages do you find hardest to write? Let me know in the comments.