Why Emails Get Ignored—and How to Write for a Reply

Emails are often ignored because the recipient cannot quickly identify the purpose, required action, or deadline. A reply is more likely when the message gives enough context, asks for one specific action, and makes the next step easy.

No structure can guarantee a response. The recipient may be unavailable, uninterested, or unable to help. Good writing removes avoidable friction and makes silence less likely to result from confusion.

Put the purpose in the subject line

A useful subject describes the action or decision, not just the general topic.

Weak: Quick question
Better: Approve homepage copy by Thursday
Weak: Meeting
Better: Choose a 30-minute time for Q3 lead handoff

Use words such as “urgent” only when the deadline and consequence are genuinely urgent. Repeated urgency trains recipients to ignore it.

State the request in the opening lines

Begin with why you are writing and what you need. Background belongs after the request unless it is necessary to understand it.

Hi John,

Could you review the attached two-page proposal and approve or comment by
Thursday at 3 p.m.? The launch team needs a decision before Friday's build.

The two open questions are:
- Should the trial last 14 or 30 days?
- Can support cover the proposed launch date?

The reader can immediately see the task, deadline, reason, and two decisions.

Reduce the effort required to reply

Broad requests such as “What do you think of our strategy?” require the recipient to decide what to review and how detailed the answer should be. Narrow the request:

ask for approval, a choice, a document, or a specific type of feedback;
offer two or three feasible options when appropriate;
link directly to the file or section being discussed;
state the desired response length or format;
include a deadline and explain what happens next.

Do not force a yes/no answer when the issue genuinely needs discussion. The goal is clarity, not manipulation.

Include enough context—but no more

The recipient should not have to search old threads to understand the message. Identify the project, previous decision, and relevant constraint in one or two sentences. Move detailed evidence to an attachment or linked document and summarize the key point in the email.

When forwarding a long thread, add a short note at the top explaining why the person is included and what they should do.

Format for scanning

Keep paragraphs short.
Use bullets for multiple facts or options.
Bold a deadline or required action sparingly.
Put one primary request in each message.
Use descriptive link text rather than pasting an unexplained URL.

A short email is not automatically clear. Include the information the recipient needs to respond correctly, even if that takes another paragraph.

Before-and-after example

Vague version:

Hi John,

I wanted to follow up on our conversation last quarter about collaboration between our departments. There have been several developments, and I wondered whether we could discuss the ideas we mentioned. Please let me know your thoughts.

Clearer version:

Hi John,

Could we schedule 30 minutes next week to review a proposed marketing-to-sales lead handoff? I need your feedback on ownership and response times before I send the process to both teams.

I am available Tuesday from 2–4 p.m. or Thursday morning. If neither works, please suggest another time.

The second message names the topic, desired action, purpose, and available times without claiming that the meeting is already agreed.

Send a useful follow-up

If the deadline is approaching, reply in the same thread and restate the request in one sentence. Add new information when possible instead of writing only “Just checking in.”

Hi John—following up on the lead-handoff proposal below. Could you confirm
Option A or B by Thursday at 3 p.m.? If I do not hear back, I will move the
launch review to next week.

For non-urgent requests, allow a reasonable period based on the recipient's workload and your relationship. Repeated daily follow-ups can make a response less likely.