Asking for something over email feels simple until you hit send and wait, and wait, and hear nothing back. The truth is that most ignored requests are not rejected on merit. They are unclear, badly timed, or buried under vague phrasing that makes the reader work too hard. This guide breaks down how to write a request email that earns a quick, confident yes, with structure, real examples, and follow-up tactics you can use today.

Why most request emails get ignored

A request email asks someone to do something: review a document, make an introduction, approve a budget, grant time off, or hop on a call. The person reading it is busy and scanning. If they cannot tell within a few seconds what you want and what they need to do, your email goes to the bottom of the pile.

The most common reasons requests stall:

  • The ask is buried. Three paragraphs of context come before the actual request.
  • It is vague. "Let me know your thoughts" gives the reader nothing concrete to act on.
  • It demands too much. A "quick question" that requires an hour of work is not quick.
  • There is no deadline. Without a date, your request has no place in anyone's priorities.
  • It assumes a yes. Pushy framing makes people defensive rather than cooperative.

Fixing these is mostly about respecting the reader's time and removing friction. The easier you make it to say yes, the more often you will hear one.

The anatomy of a request that works

Strong request emails follow a predictable shape. You do not need every element every time, but this order rarely fails.

  1. A subject line that states the ask. Specific and scannable.
  2. A one-line opener that gives context or reconnects.
  3. The request itself, stated plainly and early. Do not make people hunt for it.
  4. The why, kept short. One or two sentences on the reason and the benefit to them where it exists.
  5. A clear, low-friction next step, including a deadline.
  6. A warm, brief close.

Write a subject line that does the work

Your subject line should answer "what is this about?" before the email is even opened. Compare these:

Vague: Quick question

Better: Approval needed: Q3 marketing budget (by Thursday)

The second version tells the reader the type of action, the topic, and the timing. That is enough for them to prioritize it correctly. A few reliable patterns:

  • Request: [thing] by [date]
  • [Action] needed: [topic]
  • Re: [project] — your input on [specific item]

If your subject line could describe a hundred different emails, rewrite it.

Put the ask near the top

Readers decide whether to engage in the first two or three lines. Lead with a short context line, then state your request before any lengthy explanation. People can always read the background after they understand what you want from them.

Make the why short and reader-focused

Context matters, but keep it tight. The strongest reasons connect your request to something the reader cares about: a shared goal, a deadline they own, or a benefit to their team. If there is no direct benefit to them, be honest and brief rather than padding it with fake urgency.

Lower the friction on the next step

A request that requires the reader to figure out logistics is a request that gets postponed. Do the thinking for them:

  • Suggest two specific time slots instead of "when are you free?"
  • Attach the document instead of asking them to find it.
  • Offer a draft they can edit instead of asking them to write from scratch.
  • Give a clear deadline with a reason, not an arbitrary one.

A full example: asking for a favor from a busy contact

Say you want a former colleague to introduce you to someone at their company. Here is a version that respects their time and makes the yes easy:

Subject: Quick intro request — your colleague Dana on the data team

Hi Marcus,

Hope the new role is treating you well. I am exploring a move into data analytics and noticed your colleague Dana leads that team. Would you be open to a short introduction?

To make it easy, I have drafted a blurb you can forward or edit:

"Marcus here. I worked with Priya at Northwind and she is moving into analytics. She would love 15 minutes of your time to learn about your team. Connecting you both."

No pressure at all if the timing is not right. Either way, it is great to be back in touch.

Thanks, Priya

Notice what this does. It reconnects warmly, states the ask in the first paragraph, removes the work by drafting the forwardable text, and gives a graceful exit. That exit ("no pressure") is not weakness. It signals respect, which makes people more willing to help.

A workplace example: requesting a deadline extension

Internal requests need the same clarity, with a bit more accountability. When you need more time on a deliverable, acknowledge the impact and propose a solution rather than just asking for slack:

Subject: Request: 2-day extension on the onboarding deck

Hi Sara,

I want to flag this early rather than at the last minute. The onboarding deck is on track, but the legal review came back with more changes than expected, and I want to incorporate them properly rather than rush.

Could we move the due date from Friday to Tuesday? That gives me time to revise and still leaves a buffer before the team meeting on Thursday.

If Friday is firm for a reason I am missing, let me know and I will prioritize accordingly.

Thanks, Jordan

This works because it takes ownership, gives a concrete reason, proposes a specific new date, and shows awareness of the downstream deadline. The reader can approve it with a single word.

Tone: confident, warm, and not pushy

The sweet spot for a request is confident but considerate. You believe your ask is reasonable, and you also accept that the other person gets to decide.

A few small wording shifts that change how a request lands:

  • Instead of "I need you to..." try "Would you be able to..." for peers and seniors. Save direct phrasing for clear delegation.
  • Instead of "ASAP," give a real date: "by end of day Wednesday."
  • Instead of "Just checking if you got this," try "Following up in case this slipped past."
  • Instead of over-apologizing ("So sorry to bother you again"), thank them: "Thanks for taking a look."

Confidence does not mean dropping politeness. It means stating what you want clearly and trusting that a reasonable ask deserves a real answer.

How to follow up without being annoying

Silence is usually not a no. People forget, get buried, or mean to reply later. A good follow-up is short, friendly, and gives the reader an easy on-ramp back into the conversation.

  • Wait a sensible interval. Two to three business days for most requests. Sooner only if there is a genuine deadline.
  • Reply in the same thread so the original context travels with it.
  • Keep it to two lines. Restate the ask and the deadline, nothing more.
  • Make it easy to decline. A simple "no" should feel acceptable, which paradoxically gets you more yeses.

A clean follow-up looks like this:

Hi Marcus, floating this back to the top of your inbox in case it got buried. Totally fine if now is not a good time. Thanks again.

After two unanswered follow-ups, let it rest. Continuing to push past that point usually costs you goodwill without changing the outcome.

Small details that quietly raise your reply rate

A few finishing touches make your requests easier to act on and easier to trust:

  • Proofread the name. Getting the recipient's name wrong undercuts everything else.
  • Keep paragraphs short. Walls of text get skimmed and skipped.
  • One request per email when you can. Bundled asks tend to get a partial answer or none.
  • Use a clean, professional signature so the reader knows who you are and how to reach you. A consistent signature adds credibility to cold or first-time requests. If you do not have one yet, you can create a free email signature in a couple of minutes, and our email signature best practices guide covers what to include.

Frequently Asked Questions

How long should a request email be?

Short enough to read on a phone without scrolling much. Aim for a clear subject line and three or four short paragraphs at most. If your context truly needs more space, summarize the ask up top and put the detail below, or move it to an attached document. The request itself should always be obvious within the first few lines.

Should I give a deadline even for small requests?

Yes, almost always. A deadline gives your request a place in the reader's priorities. Without one, it competes with everything else and tends to lose. Frame the deadline with a brief reason so it feels collaborative rather than demanding, for example "by Thursday so I can finalize the report before our Friday review." For genuinely flexible asks, you can soften it: "no rush, but anytime this week would be ideal."

What is the best time to send a request email?

There is no perfect universal time, but mid-morning on a Tuesday, Wednesday, or Thursday tends to catch people when they are working through their inbox and not buried in Monday catch-up or Friday wind-down. More important than the exact hour is sending when the reader has time to act, not late at night or right before a holiday when your email will be buried by the time they return.

A good request email is mostly an act of empathy. You make the ask clear, you respect the reader's time, and you make saying yes the path of least resistance. Do that consistently and you will find people not only respond faster, they start to look forward to hearing from you.