unclear_brief_email
Ask targeted clarifying questions when a client brief is too vague. Prevents rework and scope creep by requesting specifics before work begins.
Instructions
Write the email sent when a client's brief is too vague to start work safely — asks targeted clarifying questions before time is spent. Lists the specific unclear points concisely, explains why each matters (to avoid rework or surprises), and offers a quick call if it's easier than written answers. Professional and collaborative in tone — not a complaint, not a lecture. Prevents scope creep and misaligned deliverables from the start. Distinct from scope_change_email (used mid-project when scope expands) and revision_response_email (used after client feedback). Does not count against your monthly draft limit.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | First name or full name of the client | |
| project_name | No | Name or description of the project | |
| unclear_points | Yes | The specific things that need clarification (e.g. 'Who is the target audience?', 'What does success look like — increased signups, revenue, engagement?'). 2–5 questions work best. | |
| suggest_call | No | Whether to offer a quick call as an alternative to written answers — defaults to true | |
| response_deadline | No | Date or timeframe by which you need answers to stay on schedule (e.g. 'by Thursday', 'before end of week') | |
| your_name | No | Your name for the sign-off |