How to Reply to an Email with Multiple Questions: A Worked Example

A reply can sound professional and still leave half the conversation unresolved. Start by deciding what each question needs, then turn those answers into a readable email.

By MailCat · Published 8 October 2026 · Updated 9 October 2026

A complete answer does not have to promise everything

Reply in the sender's order. Answer what you know, explain what is still pending, and ask a specific question where the request is unclear. A useful reply can be complete even when not every decision is settled.

Facts supplied by the recipient: the homepage draft is ready; the agreed package covers desktop only; Thursday has not been checked; the extra-work estimate has not been prepared. These are example facts, not information an assistant independently knows.

Map each request to a sentence

The last two questions share a dependency, so the reply can connect them without hiding either one. That is different from writing “Sounds good” and appearing to approve the date, deliverable, and price at once.

Find implied requests too

Read once for context and again for action. Questions, proposed dates, approvals, and requests for work all need attention. “We were hoping to launch Friday” may need an answer even without a question mark. Check whether an older quoted request has already been resolved before treating it as current.

Choose a format that makes checking easy

For two or three connected questions, short paragraphs usually work. For a longer list, number the answers or use clear topic labels. Keep the sender's order unless another sequence makes a dependency clearer. Quote only enough of a question to remove ambiguity.

A paragraph can sound polished while omitting a point. In this example, “The draft is ready, and I will prepare a mobile estimate” does not address Thursday or ask which pages need mobile layouts. Compare the finished reply against the request map, not just its tone.

Change the answer when the facts change

If Thursday is confirmed, state the date and any real dependency. If the mobile estimate is approved, state the agreed deliverables and cost. If you cannot take on mobile work, decline it directly and explain the next useful option. These are different business decisions, not merely different tones.

For a deeper example, see responding to a scope change. If several answers are pending, use the known, pending, and clarify method.

Use MailCat to organize your chosen answers

In desktop Gmail, click Reply and review the points MailCat identifies in the visible message and relevant visible quotations. For each detected point, choose a suggested option, enter a custom answer, or select Skip. Add missing context or a request the analysis missed in “Anything else to include?”; the cards do not edit the original detected questions.

Every detected point must be answered or skipped before Compile Reply. Include at least one answer or an instruction. Compile produces an editable preview, not an email sent on your behalf. If you skip a question because its answer is unknown, add instructions to acknowledge that uncertainty when it matters; otherwise the draft may leave it out.

Review the wording, use Update draft or edit directly, then explicitly Insert reply. Check the combined Gmail draft and send it yourself. MailCat does not read attachments or know your availability or pricing. See the full Gmail walkthrough.

Before you send

• Is every important request confirmed, declined, clarified, or explicitly pending?
• Did a polished sentence accidentally promise an unapproved fee, date, or deliverable?
• Are the conditions and next action clear?
• Have you checked the original email, recipients, and attachments?