How to ask for something in an email (with examples)

Why How You Ask Matters More Than What You Ask

Most professional emails are requests. You are asking for a meeting, asking for information, asking for a decision, asking for help. The difference between a request that gets a response and one that gets ignored is rarely about what you are asking for. It is about how you ask.

Requests fail for predictable reasons. They are too vague ("Can we chat sometime?"), too demanding ("I need this by end of day"), too long (a five-paragraph email to ask a yes-or-no question), or too presumptuous (assuming the recipient has time, interest, or obligation to help).

Effective requests share four qualities. They state the ask clearly in the first few sentences. They explain why it matters to the recipient, not just to you. They make it easy to say yes by reducing friction. And they respect the recipient's time by keeping the email concise.

How to Structure a Request Email

Every request email should follow this structure:

Step 1: Open with Context

Start with one sentence that establishes why you are reaching out. This is not a greeting or a pleasantry. It is the bridge between "who is this person" and "what do they want."

Good context openers:

- "I am working on [project] and need your input on [specific topic]."

- "Following up on our conversation about [topic] at [event]."

- "[Mutual connection] recommended I reach out to you about [topic]."

Bad context openers:

- "I hope this email finds you well." (says nothing)

- "My name is [Name] and I am a [title] at [Company]." (self-focused)

- "I have been meaning to reach out for a while." (vague)

If you are looking for stronger ways to start your emails, our collection of alternatives to "I hope this email finds you well" covers dozens of options organized by tone and context.

Step 2: State the Request Clearly

After the context, state exactly what you need. Do not bury the request in the third paragraph. Do not hint at it and hope the recipient figures it out. Be direct.

The request should answer three questions: What do you need? Why do you need it? What is the timeline?

Good request statements:

- "Would you be available for a 20-minute call next week to discuss [topic]?"

- "Could you share the [specific document] by Friday? I need it for [specific reason]."

- "I would appreciate your feedback on [specific thing]. A few bullet points would be enough."

Bad request statements:

- "I was wondering if maybe we could potentially find some time." (too tentative)

- "It would be great to pick your brain." (vague and overused)

- "Let me know what you think." (not a clear ask)

Step 3: Reduce Friction

Make it as easy as possible for the recipient to say yes. The more effort your request requires, the less likely it is to get a response.

Ways to reduce friction:

- Suggest specific times instead of asking "when works for you"

- Attach the document you need reviewed instead of asking them to find it

- Offer multiple response options ("A quick yes/no is all I need")

- Set a short meeting length (15-20 minutes is less intimidating than 60)

- Provide context they would otherwise need to search for

Step 4: Close with a Clear Next Step

End the email with one sentence that tells the recipient exactly what happens next. This eliminates ambiguity about who does what.

Good closings:

- "If Tuesday at 2pm works, I will send a calendar invite."

- "I will follow up on Friday if I have not heard back."

- "Just reply with 'approved' or 'not yet' and I will take it from there."

Bad closings:

- "Looking forward to hearing from you." (passive, no action)

- "Thanks in advance." (assumes compliance before it is given)

- "Please do not hesitate to reach out." (cliche, no clear next step)

Request Email Examples

Asking for a Meeting

Subject: 20-minute call about [topic] next week?

Hi [Name],

I am working with [context about your company or project] and came across your work on [specific reference]. I think there is a natural overlap worth exploring.

Would you be open to a 20-minute call next Tuesday or Wednesday afternoon? I have a specific question about [topic] and can keep it focused.

If either day works, let me know and I will send a calendar invite.

Best,[Your Name]

This works because it is specific about the time commitment (20 minutes), offers concrete options (Tuesday or Wednesday), and states what the conversation will cover. For more meeting request formats, our collection of meeting request email templates provides 25+ variations for different contexts.

Asking for Information

Subject: Quick question about [specific topic]

Hi [Name],

I am putting together [deliverable] for [purpose] and need [specific information] to complete the [specific section].

Could you share [exactly what you need] by [date]? If you do not have it readily available, pointing me to the right person would be just as helpful.

Thanks,[Your Name]

This works because it explains why you need the information (not just that you need it), gives a deadline, and offers an alternative path if the recipient cannot help directly.

Asking for a Favor or Introduction

Subject: Would you be willing to introduce me to [Name]?

Hi [Name],

I noticed that you and [target person] are connected. I am reaching out to them about [specific reason], and I believe an introduction from you would carry more weight than a cold email.

If you are comfortable making the introduction, I have drafted a short blurb below that you can forward or adjust. If the timing is not right or you would prefer not to, no worries at all.

[Draft blurb: "Hi [Target Name], I wanted to introduce you to [Your Name], who is working on [relevant context]. I thought you two should connect because [specific reason]. I will let you take it from here."]

Thanks for considering it,[Your Name]

This works because it does the work for the recipient (providing a draft), gives them an easy out ("no worries at all"), and explains why the introduction matters.

Asking for Feedback

Subject: Would appreciate your feedback on [specific thing]

Hi [Name],

I have been working on [project/document/proposal] and would value your perspective before I finalize it. Your experience with [specific relevant area] is exactly the lens I need.

I have attached the [document]. The sections I am most uncertain about are [specific sections]. If you could review those and share a few thoughts by [date], it would make a significant difference.

A few bullet points or even margin comments would be enough. No need for a formal review.

Thanks,[Your Name]

This works because it narrows the scope of the feedback (specific sections, not the entire document), sets expectations for the format (bullet points), and acknowledges the effort involved. If you need to send the document securely, our guide on emailing documents securely covers the best methods.

Asking for Approval

Subject: Approval needed: [specific item] by [date]

Hi [Name],

I need your approval on [specific item] before we can proceed with [next step]. Here is a summary:

- What: [Brief description of what needs approval]

- Cost/Impact: [Relevant numbers or implications]

- Deadline: [When you need the decision by and why]

I have attached the full details for reference. If you have questions, I am available to discuss. Otherwise, a reply with "approved" will keep us on schedule.

[Your Name]

This works because it puts all relevant information in the email body (no need to open attachments for the core decision), makes the ask binary (yes or no), and explains the consequence of delay.

Asking for a Raise or Promotion

Subject: Discussion request: my role and growth path

Hi [Name],

I would like to schedule a conversation about my current role and future growth at [Company]. Over the past [timeframe], I have [specific accomplishments with measurable results], and I believe a conversation about [compensation/title/responsibilities] is appropriate.

Would you have 30 minutes in the next two weeks to discuss this? I want to approach this thoughtfully and have some specific points prepared.

Best,[Your Name]

This works because it signals the topic without making the full pitch in email (better for an in-person conversation), provides evidence (accomplishments), and is respectful of the manager's time.

Common Mistakes to Avoid

Burying the ask. If the recipient has to read four paragraphs before understanding what you want, most will stop reading before they get there. State your request within the first three sentences.

Making it about you. "I need," "I want," "I would love" places the focus on your needs. Reframe requests in terms of what matters to the recipient: "This would help the team hit the Q3 deadline" is more compelling than "I need this for my project."

Being too tentative. Excessive hedging ("I was just wondering if maybe you might possibly have time") signals low confidence and makes you easy to ignore. Be polite but direct. Strong email etiquette balances politeness with clarity.

Not specifying the format or scope. "Can you give me feedback?" could mean anything from a thumbs up to a 10-page critique. Specify what you need: "Three bullet points on whether the pricing section is clear" is actionable.

Forgetting the deadline. Without a timeline, your request has no urgency. If you need something by Friday, say so. If there is no deadline, the request will sit in their inbox indefinitely.

Sending too much context. Relevant context helps. A full history of your project, your company's mission statement, and your personal background does not. Include only the context the recipient needs to make a decision. The same principle applies to cold email length: shorter emails with clear asks consistently outperform long ones.

FAQ

How long should a request email be?

Five to eight sentences for most requests. Longer emails are appropriate for complex requests (budget approvals, project proposals), but even then, the actual ask should appear early. If the email exceeds 200 words, check whether every sentence is necessary.

Should I follow up if I do not get a response?

Yes. Wait three to five business days, then send a brief follow-up. Reference your original email, restate the ask in one sentence, and provide any new context. Most non-responses are caused by busy inboxes, not deliberate ignoring. Knowing how many follow-up emails to send helps you stay persistent without becoming annoying.

Is it appropriate to set a deadline in a request email?

Yes, and you should. A deadline communicates urgency and helps the recipient prioritize. Frame it politely: "If you could share this by Thursday, it would give me time to incorporate your feedback before the Friday review."

How do I ask for something from someone more senior?

The same principles apply, with additional emphasis on respecting their time. Be more concise, more specific about what you need, and more flexible about timing. Acknowledge their seniority without being sycophantic: "I know your schedule is tight, so I have kept this brief."

What if my request gets rejected?

Respond graciously. Thank them for considering it, ask if there is an alternative path ("Is there someone else who might be able to help?"), and leave the door open for future requests. How you handle rejection shapes whether they say yes next time.