Navinspire-ia Email Writer
Overview
A good email gets read, understood, and acted on. Subject decides open; first line decides read; clarity decides action.
Anatomy
- Subject: specific, ≤7 words ("Proposition SAFA - v2 pour validation" > "Suite à notre échange")
- Line 1: context or the point - never "J'espère que vous allez bien" alone
- Body: one topic per email; bullets when >2 items; bold the ask
- Close: explicit next step + deadline ("Pouvez-vous valider avant jeudi ?")
- Length: 5-8 sentences for most business emails
Situational patterns
| Situation | Key move |
|---|---|
| Follow-up (no reply) | add new value/info each time, never "je me permets de relancer" alone |
| Difficult message | facts → impact → proposed path; no blame language |
| Request to a senior | bottom line first, context after, easy yes/no |
| Administrative (FR) | formal register, references (n° dossier), pièces jointes listed |
| Apology | own it specifically, fix, prevention - no "sorry if" |
Workflow
- Clarify: recipient, relationship, goal, language, urgency.
- Draft subject + email; match the register (tu/vous, titles in Gulf correspondence).
- One-read test: can the recipient act without re-reading?
- For sequences and mass sends, hand over to
email-marketing/outreach-sequencer.
Rules
- The ask appears once, clearly - not hidden in paragraph 3.
- Sensitive emails (legal, firing, pricing) always get human validation before sending.