Draft Outreach Email

---
name: draft-outreach-email
description: >
  Writes cold outreach emails, follow-ups, LinkedIn/Zalo messages, and call openers.
  Triggered by "viết email cho [công ty]", "soạn email chào hàng", "follow-up",
  "khách chưa trả lời viết gì", "tin nhắn LinkedIn", "write an email to", "break-up email".
---

# Draft outreach email

Use when the user only needs buyer-facing copy. If they also want research, a proposal, or a next
step → `run-pipeline`.

Writing guidance: `${CLAUDE_PLUGIN_ROOT}/playbooks/messaging.md`.

## Required

**Company name** and **what the user sells**. Missing either → ask exactly one question.

Do **not** ask for: recipient name, exact job title, preferred tone, which case study to use. All of
these have safe defaults.

## The most important rule

**The email returned must be complete, with no blanks.**

Fill every gap with a reasonable assumption and list what to check below. Keep `[[EDIT: ...]]` in
the body **only for prices and numbers**.

Reason: the user came here to do less work. An email with six holes in it makes the plugin feel worse
than using nothing. See `${CLAUDE_PLUGIN_ROOT}/policies/safety-core.md` section 3.

## Message types

| Situation | Type | Length |
|---|---|---|
| Never contacted | Cold first touch | 60–110 words |
| Silent 4–7 days | Follow-up #1 | 40–80 |
| Silent after two touches | Follow-up #2, new angle | 40–80 |
| Silent after three | Break-up | 40–60 |
| Went cold after interest | Re-engagement | 50–80 |
| Just had a call | Recap | 60–90 |
| Proposal sent, no reply | Proposal follow-up | 40–80 |
| LinkedIn / Zalo | Short message | under 45 |

Subject under 50 characters.

## Output

```markdown
### Nội dung gửi
Tiêu đề:
- [Option 1]
- [Option 2]

[Complete email]

### Việc tiếp theo
- [What to check — max 2 lines]
- Gửi xong nhắn mình "khách trả lời..." hoặc "chưa thấy hồi âm" để mình cập nhật deal.
```

Headings follow the user's language.

## When data is missing

| Missing | Do this |
|---|---|
| Recipient name | Use "anh/chị" (or a persona in English), note one line |
| Nothing known about the company | General problem angle, no forced personalisation |
| No case study | Talk about method, not results |
| No clear CTA | 15-minute call |
| Weak research | Write the cautious version anyway — do not stall |

## After writing

1. Run `${CLAUDE_PLUGIN_ROOT}/workflows/verification.md`. If numbers, results, or past customers are mentioned → call
   `${CLAUDE_PLUGIN_ROOT}/agents/sales-reviewer.md`.
2. Update the deal file per `${CLAUDE_PLUGIN_ROOT}/policies/state-management.md`.

## References

Load **one**, never both:

- `references/email-templates.md` — templates by stage
- `references/objection-responses.md` — only when handling an objection

Writing Vietnamese for a buyer → `${CLAUDE_PLUGIN_ROOT}/knowledge/vietnamese-sales-language.md`.