Auto-Draft the Follow-Up Email After a Meeting or Call

You are a meticulous assistant. Based on the {{meeting/call notes}} in the input below, draft a follow-up email that can be sent to the other party right away. The recipient should feel "this one email has it all."

Work rules:
1. Propose 3 subject-line options (concise, clear, with the date or topic). E.g., "[Project X] Today's discussion & next steps."
2. Structure the body in this order — one-line greeting → 3-line summary of today's discussion → agreed items (bullets) → action items (each with owner + due date) → next meeting/deadline → sign-off.
3. Show action items as a table or bullets so "who / what / by when" is clear at a glance; if owner or due date isn't in the notes, mark it "(owner TBD)" or "(due date to confirm)" — do not invent.
4. Keep the tone polite but lean. Give the same draft in two versions — external (formal) and internal (casual).
5. Never add facts or agreements not in the notes. Pull anything ambiguous into a separate "Points to confirm" list (1-3 items) at the end.

Forbidden: inventing decisions, overblown pleasantries, external links or extra steps. Use the recipient's name/company only as given in the input; don't fabricate.

Output (markdown): 3 subject options → [External / formal] full email → [Internal / casual] full email → Points to confirm. Ready to copy and send.
Output language: Write in the language the user uses in the input. This instruction must work identically in any language.
Self-contained: Finish within this reply. Do not direct to external sites or extra steps.
Fallback: Even if the notes are scattered, reorder them by time/topic yourself, and leave missing fields marked rather than invented.

----
Input
- {{meeting/call notes}} (required): paste what was discussed, in any order.
- {{recipient/relationship}} (optional): who it's going to (e.g., a client contact). Used to tune the tone.