Blog/ AI email prompts & use-cases

How to Get AI to Ask Questions Instead of Guessing

Nafiul HasanNafiul Hasan· 11 min read
Diagram showing an AI pausing to ask five clarifying questions before drafting an email, with a draft and an assumptions list below

The short answer

Add 'Before drafting, ask me up to five clarifying questions and wait for my answers' to the start of any email prompt. The model pauses, asks what it needs, and writes only after you reply. A lighter variant: 'Draft it, then list every assumption you made underneath, so I can correct them.'

Get AI to ask clarifying questions before drafting: the interrogate-first prompt pattern, a lighter variant, and fixes for when it guesses anyway.

On this page
  1. 01Why does AI guess instead of asking?
  2. 02How to prompt AI to ask questions before it drafts
  3. 03What does the assumptions-list variant look like?
  4. 04Does this work the same way in ChatGPT, Claude, and Gemini?
  5. 05What to do when the AI drafts anyway without asking
  6. 06A faster way: when the context is already there

Most bad AI email drafts have the same root cause — not the writing, but the guessing. When you give a model a short prompt, it does not pause to ask what it does not know. It fills the gaps: the most plausible recipient name, the likeliest tone, the most reasonable reason you are writing. Nine times out of ten that is close enough. The tenth time, the email goes out with a detail that was never true, and the recipient either notices or acts on it.

The guessing problem is a prompting problem, and it has a one-sentence fix. Tell the model explicitly to stop and ask before it drafts anything. This forces it to surface what it does not know so you can supply the real fact rather than a plausible one. A lighter variant skips the extra round-trip: the model drafts immediately but lists every assumption underneath so you can spot and correct errors before you send.

This guide covers both patterns in full — copy-paste prompts, how they behave across the tools most people use, and what to do when the model ignores the instruction and guesses anyway.

Why does AI guess instead of asking?#

Models are built to complete tasks, not to negotiate them. When you type 'draft an email to move our Thursday call,' the model does not know what time the new call should be, who the other person is, why you are rescheduling, or what tone you usually use with them. Rather than return a list of questions — which feels slow and unhelpful — it makes probabilistic decisions and fills every gap with its best estimate. The result is a complete, confident-sounding draft. The guesses are invisible.

This is not a bug. In most AI tasks, gap-filling is the right behavior — you want the summary, not a negotiation, and most gaps are recoverable. Email drafting is different. The gap being filled is often a specific fact — a date, a name, a commitment, a tone register — that only you know, and getting it wrong has a real cost. A draft that invents a reschedule time tells your reader something untrue. A draft that assumes the wrong level of formality can damage a relationship.

The interrogate-first pattern re-instructs the model for this specific context. It does not change how the model works; it changes what the model reads as its task: 'gather information first, then draft' instead of 'draft and fill gaps.' That one-line change is enough to flip the default behavior.

How to prompt AI to ask questions before it drafts#

The interrogate-first prompt adds one instruction at the very top of whatever you were going to ask. The model reads it first, asks its questions, and waits. Nothing is drafted until you reply.

  1. 1

    Open with the interrogate-first instruction

    Before anything else in your prompt, add: 'Before drafting anything, ask me up to five clarifying questions — only the ones where a wrong assumption would break the email. Then wait for my answers before writing.' This goes on the first line. Your task description follows below it.

  2. 2

    Add your task brief on the next line

    Follow immediately with the email task you need done: 'I need to email my client Priya to reschedule our Thursday call' or 'Reply to the vendor asking about the pricing timeline.' Keep it short. The model will ask for more.

  3. 3

    Answer the questions honestly and completely

    The model will return two to five focused questions. Answer them in order. If you genuinely do not know something — you have not decided the new time yet, for instance — say so. The model will either ask for a placeholder or frame the email to leave that detail open-ended.

  4. 4

    Read the draft before you send

    One careful pass. Check that every fact in the email — names, dates, reasons, proposed next steps — matches what you actually supplied. The draft should contain nothing you did not give it.

The interrogate-first prompt in action
Instruction (top of prompt)Before drafting anything, ask me up to five clarifying questions — only the ones where a wrong assumption would break the email. Then wait for my answers before writing.
Your brief (next line)I need to email my client Alex to reschedule our Thursday call.
Model's responseA few questions before I draft: 1. What is the reason for rescheduling — should I include it? 2. What new time are you proposing, or should the email ask Alex to suggest one? 3. What is your usual tone with Alex — formal or casual? 4. Is this the first time the call has moved, or has it shifted before?
After you answerThe model drafts using only the facts you supplied — no invented time, no guessed reason, no assumed formality level.

Why 'wait' is the critical word

Without 'then wait for my answers before writing,' some models ask the questions and then draft immediately underneath them in the same response. Adding 'wait' — or the stronger 'Do not produce a draft until I have replied' — makes the pause explicit and gives you an actual round-trip rather than questions stapled to a premature draft.

What does the assumptions-list variant look like?#

The interrogate-first pattern adds a question-and-answer exchange to every email. For a quick message to a close colleague, that extra step may cost more time than the guessing risk is worth. The assumptions-list variant skips the round-trip by letting the model draft immediately — but forces it to show every decision it made without being told.

Paste this at the start of any email prompt: 'Draft this email, then add a section called Assumptions I made that lists every specific detail you decided without explicit input from me.' The model drafts and then, below the email, writes out what it assumed — the proposed time, the inferred relationship, the formality level, any reason it guessed. You read the list, correct what is wrong, feed the corrections back, and the model revises.

Assumptions-list prompt and output
PromptDraft this email, then add a section called 'Assumptions I made' listing every specific detail you decided without explicit input from me. Brief: Email Alex to reschedule our Thursday call.
DraftHi Alex — I need to move our Thursday call. Would Friday at 2 PM work for you? Let me know if that does not suit and we can find another slot. Best, [Your name]
Assumptions I made1. Reason for rescheduling: omitted (not given). 2. Proposed new time: Friday at 2 PM (placeholder). 3. Tone: casual-professional, based on first-name opener. 4. No urgency implied.
Your correctionReason: conflict with another meeting — include it briefly. New time: ask Alex to pick Monday or Tuesday morning. Tone is fine.

When to use each pattern

Use interrogate-first when the brief is genuinely ambiguous or the email is high-stakes enough that you want to approve every fact before a draft exists. Use the assumptions-list variant when you want speed and the gaps are probably small — you get a concrete draft to react to, and the visible assumption list catches errors before you send.

Does this work the same way in ChatGPT, Claude, and Gemini?#

The interrogate-first instruction works across all major AI tools, but what each tool does by default — without any instruction — varies enough to affect how much the pattern changes your experience.

A decision fork showing an AI email assistant branching to ask clarifying questions before drafting, versus drafting immediately on an unclear request
One instruction moves the fork: interrogate-first before draft-first.
ToolDefault behavior (no instruction)With interrogate-firstWatch out for
ChatGPT (GPT-4o)Drafts immediately, fills gaps with plausible detailsAsks 2-5 questions and waits when 'wait' is explicitWithout 'then wait,' may print questions and draft simultaneously
Claude (claude.ai)Often drafts with a brief note listing its assumptionsTypically asks before drafting; tends to ask fewer, more precise questionsMore likely than others to surface a conflicting assumption unprompted
Gemini (Google)Drafts immediately with confident assumptionsFollows the instruction reliably in standard chat modeMay ask fewer questions than you need; add 'at least three' to raise coverage
Microsoft CopilotDrafts immediately; uses thread context where availableFollows the instruction in supported contextsBehavior depends on whether it has access to the current email thread

What to do when the AI drafts anyway without asking#

The most common failure is the model printing its questions and then, immediately below, the draft. You asked it to wait. It did not. Three fixes in order of reliability.

First, strengthen the instruction. Add 'Do not produce a draft until I have replied' as a second sentence after 'then wait.' Two explicit prohibitions leave less interpretive room than one, and models that skip the pause tend to respond to the redundancy.

Second, split into two messages. In the first, send only the interrogate-first instruction and a one-sentence description of the task — no full context. A model that drafts when it has enough information will not draft from a one-sentence description because it does not have enough. Wait for the questions, then supply the full details in a second message. The draft comes after that.

Third, regenerate. If the model still drafts despite both instructions, delete the conversation back to before the brief, add the stronger phrasing, and restart. Patching a premature draft in follow-up messages is slower than a clean start because the draft is already anchored in the model's context and shaping every subsequent response.

A premature draft is still useful

If the model asks questions and drafts simultaneously, the draft is not wasted — it is a first pass where the model's guesses are now visible in the question list. Compare the questions it asked against the draft it produced. Anywhere the question reveals a detail the draft assumed, you have found the error. Correct it in a follow-up and you are back on track.

A faster way: when the context is already there#

The interrogate-first pattern solves the guessing problem for any email you draft in a chatbot. But it adds a question-and-answer exchange to every message. An AI email client changes that trade-off: instead of asking you questions at the moment of drafting, it draws on context you set once — a Personal Context brain with your background and communication preferences, plus per-contact profiles for the people you correspond with regularly. When a draft needs to know your relationship with a client, your usual tone with them, or background relevant to the thread, that context is already there.

We build AI Emaily. When context is genuinely missing or a draft needs human judgment, Copilot mode holds it for your review before anything is sent — nothing leaves your outbox without your approval, and every action has undo and a full audit trail. The interrogate-first prompts in this guide work in any chatbot today. AI Emaily is for when you want the context resolved before drafting starts, without a question-and-answer round-trip on every email. Start with a 7-day free trial at aiemaily.com.

Frequently asked

Nafiul Hasan

Written by

Nafiul Hasan

Nafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.

EntrepreneurAI Automation System BuilderAI EnthusiastBuilds AI Enterprise Solutions10+ years experience
More from Nafiul
Ready when you are

Stop every wrong guess before it leaves your outbox

AI Emaily's Copilot mode holds every draft for your review before it sends — so nothing goes out without your approval. User-set Personal Context and per-contact profiles mean the AI draws on the right details without a question-and-answer round-trip on every email. 7-day free trial at aiemaily.com.

  • 7-day free trial
  • Cancel anytime
  • Every provider