28 Other Ways to Say “Please Let Me Know Your Thoughts” (With Examples)

The best other ways to say please let me know your thoughts are “I’d love to hear your feedback on the pricing slide” when you want useful comments, “does this work, or should I change anything?” when you want a fast reply, and “if I don’t hear back by Thursday, I’ll proceed as drafted” when the thread has gone silent.

The original is polite and almost impossible to answer, which is why so many emails ending in it never get a reply.

What Does “Please Let Me Know Your Thoughts” Mean?

It invites the reader to respond with any reaction at all to something you have sent.

Asking for comments rather than issuing a verdict is an old and respectable habit. The internet’s standards are still published as a Request for Comments, a series Steve Crocker began in 1969 with a document called Host Software. The name was chosen deliberately: early RFCs were framed as requests “to avoid sounding too declarative and to encourage discussion”.

That is exactly the instinct behind the phrase. The problem is that “thoughts” names nothing, so the reader has to decide what you want before they can give it to you — and deciding takes effort they usually postpone.

⚡ The Short Version

Swap “thoughts” for the thing you actually want: feedback on one section, a yes or no, an approval, a recommendation. Then add a date. Vague asks get silence.

When to Use “Please Let Me Know Your Thoughts”

• 📧 Circulating a draft that is genuinely still open to change
• 📧 Asking a colleague for a reaction rather than a decision
• 📧 Inviting comment from a group where no single person owns the answer
• 📧 Closing a proposal politely when you expect a conversation next
• 📧 Softening an idea you do not want to present as final

Pros and Cons of “Please Let Me Know Your Thoughts”

Pros	Cons
Polite and never offends anyone	Asks for nothing in particular
Signals the work is still open	Easy to postpone and then forget
Works for any recipient or seniority	Invites comment on trivia as readily as substance
Safe in writing and in speech	Overused to the point of sounding automated
Does not pressure the reader	Cannot produce a decision or an approval

Why Do We Need Alternatives?

Because “thoughts” is the vaguest possible request, and vague requests are the ones people answer last. A reader who has to work out what you want will almost always come back to it tomorrow. Naming the ask — one section, one question, a yes or no, a date — is what turns a polite sign-off into a reply.

28 Other Ways to Say “Please Let Me Know Your Thoughts”

Each entry leads with real examples, then explains why it works. Watch the What it actually asks for line: it is the difference between a phrase that gets you comments and one that gets you a decision.

1. I’d love to hear your feedback

Warm and points at a specific piece of work.

Examples:

• “I’d love to hear your feedback on the pricing slide.”
• “I’d love to hear your feedback before Friday’s call.”
• “Draft attached — I’d love to hear your feedback on the tone.”

Why it works: “Feedback” names a job, which is why it outperforms “thoughts”. Add the thing you want feedback on and it becomes answerable in one sitting.

Formality: Neutral  |  What it actually asks for: Specific feedback
Best for: Work you have actually drafted  |  Avoid in: Cold outreach to strangers

2. What do you think?

The plainest question in the set.

Examples:

• “I’ve gone with the shorter version. What do you think?”
• “What do you think? Happy to change it.”
• “That’s my read on the numbers. What do you think?”

Why it works: Three words, no hedging, and it reads as a genuine question rather than a formality. Its weakness is breadth — it invites comment on anything at all.

Formality: Casual  |  What it actually asks for: Open thoughts
Best for: Peers and people you message often  |  Avoid in: Formal proposals and large documents

3. I’d appreciate your input

Slightly formal, implies you will use it.

Examples:

• “I’d appreciate your input on the hiring criteria.”
• “You know this client better than I do, so I’d appreciate your input.”
• “I’d appreciate your input before I send this upward.”

Why it works: “Input” suggests contribution to something unfinished, which flatters the reader’s expertise. It also quietly commits you to acting on what they say.

Formality: Neutral to formal  |  What it actually asks for: Open thoughts
Best for: Asking a specialist or a senior colleague  |  Avoid in: Work already signed off

4. Let me know what you think

The everyday workhorse.

Examples:

• “Draft’s attached — let me know what you think.”
• “Let me know what you think and I’ll make the changes tonight.”
• “Let me know what you think, no rush.”

Why it works: It sounds like a person rather than a template, which the original phrase struggles to do. Dropping “please” makes it warmer, not ruder.

Formality: Casual to neutral  |  What it actually asks for: Open thoughts
Best for: Internal email and day-to-day work  |  Avoid in: Clients expecting formality

5. I’d value your perspective

Formal and genuinely complimentary.

Examples:

• “You’ve run three of these launches, so I’d value your perspective.”
• “I’d value your perspective on how the board will read this.”
• “I’d value your perspective before we commit to the timeline.”

Why it works: “Perspective” asks for a viewpoint rather than corrections, which suits someone senior whose judgement you want rather than their edits.

Formality: Formal  |  What it actually asks for: Open thoughts
Best for: Mentors, executives, advisers  |  Avoid in: Quick internal checks

6. Feel free to share your thoughts

Open, low-pressure and easy to ignore.

Examples:

• “Feel free to share your thoughts on the agenda before Tuesday.”
• “Feel free to share your thoughts in the comments on the doc.”
• “Nothing is fixed yet, so feel free to share your thoughts.”

Why it works: “Feel free” makes replying optional, which is perfect for a broadcast to twenty people and useless when you need one particular answer.

Formality: Neutral  |  What it actually asks for: Optional feedback
Best for: Group circulations and open drafts  |  Avoid in: When you actually need a reply

7. I’m interested in your opinion

Direct and a little formal.

Examples:

• “I’m interested in your opinion on whether we should delay.”
• “I’m interested in your opinion, even if it’s a blunt one.”
• “I’m interested in your opinion on the second option.”

Why it works: “Opinion” asks for a position rather than a reaction, which is the right ask when you want somebody to come down on one side.

Formality: Neutral to formal  |  What it actually asks for: A position
Best for: Decisions with two or three options  |  Avoid in: Requests for line-level edits

8. Could you share your thoughts?

Polite and phrased as a request.

Examples:

• “Could you share your thoughts on the revised scope?”
• “Could you share your thoughts by end of day Thursday?”
• “Could you share your thoughts on where this is weakest?”

Why it works: Turning it into a question makes it a request somebody can agree to, which gets more replies than a statement. Add a date and it gets more still.

Formality: Neutral  |  What it actually asks for: Open thoughts
Best for: Clients and colleagues outside your team  |  Avoid in: Casual group chats

9. I’d love your thoughts on this

Warm, brief and very common.

Examples:

• “I’d love your thoughts on this when you get a minute.”
• “I’d love your thoughts on this — particularly the opening.”
• “Rough draft, but I’d love your thoughts on this.”

Why it works: Friendly and light, with “on this” narrowing the request to the attachment rather than the whole project.

Formality: Casual  |  What it actually asks for: Open thoughts
Best for: Colleagues you have a rapport with  |  Avoid in: Formal client correspondence

10. What are your thoughts on this?

The neutral question form.

Examples:

• “What are your thoughts on this approach?”
• “What are your thoughts on this before I brief the team?”
• “I’ve left the old version below. What are your thoughts on this?”

Why it works: A clean, professional question that suits almost any recipient. It is the safest of the open-ended options because nothing about it can grate.

Formality: Neutral  |  What it actually asks for: Open thoughts
Best for: Almost anyone  |  Avoid in: Situations needing a yes or no

11. I’d be grateful for your feedback

Formal, warm and slightly deferential.

Examples:

• “I’d be grateful for your feedback on the attached report.”
• “I know you’re stretched, so I’d be grateful for your feedback on section three only.”
• “I’d be grateful for your feedback before the deadline on the tenth.”

Why it works: Gratitude in advance is disarming, and pairing it with a narrowed scope — one section, one question — makes a busy person far likelier to answer.

Formality: Formal  |  What it actually asks for: Specific feedback
Best for: Senior reviewers and external experts  |  Avoid in: Quick internal notes

12. I’d like to know your opinion

Straightforward and neutral.

Examples:

• “I’d like to know your opinion on the supplier change.”
• “Before we go further, I’d like to know your opinion.”
• “I’d like to know your opinion on which version reads better.”

Why it works: Plain and unfussy. It can sound flat without a specific question attached, so name the thing you want an opinion on.

Formality: Neutral  |  What it actually asks for: A position
Best for: Choices between clear options  |  Avoid in: Emotive or sensitive topics

13. Please share your feedback

Direct, slightly institutional.

Examples:

• “Please share your feedback using the form by Friday.”
• “Please share your feedback on the draft policy in the document itself.”
• “Please share your feedback — all of it is read.”

Why it works: It works for processes rather than people: surveys, review cycles, circulated policies. Sent to one colleague it reads like an automated request.

Formality: Neutral  |  What it actually asks for: Specific feedback
Best for: Surveys, forms and formal review rounds  |  Avoid in: One-to-one messages

14. I’d appreciate your thoughts

Warm, polite, extremely common.

Examples:

• “I’d appreciate your thoughts on the structure.”
• “I’d appreciate your thoughts whenever you have a moment.”
• “I’d appreciate your thoughts on whether this is too long.”

Why it works: Almost a straight swap for the original with the stiffness removed. It stays vague, so it works best with a question added behind it.

Formality: Neutral  |  What it actually asks for: Open thoughts
Best for: General professional use  |  Avoid in: When you need a decision

15. Let me know if you have any feedback

Low-pressure and easy to decline.

Examples:

• “Let me know if you have any feedback, otherwise I’ll publish Monday.”
• “Let me know if you have any feedback on the figures.”
• “It’s close to final — let me know if you have any feedback.”

Why it works: “If you have any” makes silence an acceptable answer, which is either the point or the problem. Pair it with what happens by default.

Formality: Neutral  |  What it actually asks for: Optional feedback
Best for: Near-final work needing a last check  |  Avoid in: Early drafts needing real input

16. I’d welcome your input

Formal and gracious.

Examples:

• “I’d welcome your input on the governance section.”
• “You chaired the last review, so I’d welcome your input.”
• “I’d welcome your input at any stage of this.”

Why it works: “Welcome” signals you are not being defensive, which matters when the reader might hesitate to criticise your work.

Formality: Formal  |  What it actually asks for: Open thoughts
Best for: Committees, boards and formal collaboration  |  Avoid in: Casual internal chat

17. I’m keen to hear your thoughts

Enthusiastic, and distinctly British.

Examples:

• “I’m keen to hear your thoughts on the rebrand.”
• “I’m keen to hear your thoughts before the client sees it.”
• “I’m keen to hear your thoughts, even the awkward ones.”

Why it works: “Keen” conveys genuine appetite for the answer. It reads as natural in British and Australian English and slightly bookish in American English.

Formality: Neutral  |  What it actually asks for: Open thoughts
Best for: UK and Commonwealth workplaces  |  Avoid in: US audiences wanting plain phrasing

18. Could I get your opinion?

Casual and conversational.

Examples:

• “Could I get your opinion on something quickly?”
• “Could I get your opinion on the wording here?”
• “Could I get your opinion before I reply to her?”

Why it works: It frames the ask as small, which lowers the cost of saying yes. Ideal as an opener in a chat message rather than a whole email.

Formality: Casual  |  What it actually asks for: A position
Best for: Instant messages and quick desk-side asks  |  Avoid in: Formal written requests

19. What’s your take on this?

Casual, slightly journalistic.

Examples:

• “What’s your take on this? I can’t decide.”
• “What’s your take on this pricing model?”
• “Two very different reviews came back. What’s your take on this?”

Why it works: “Take” asks for an individual read rather than a verdict, which invites candour. It is markedly informal, so it suits peers.

Formality: Casual  |  What it actually asks for: A position
Best for: Peers and people you trust  |  Avoid in: Executives and clients

20. I’d love your input on this

Warm and collaborative.

Examples:

• “I’d love your input on this before it’s locked.”
• “I’d love your input on this — you spotted the last problem.”
• “Still moving, so I’d love your input on this.”

Why it works: Combining “love” with “input” makes it friendly and unfinished at once, which encourages real suggestions rather than polite approval.

Formality: Casual  |  What it actually asks for: Open thoughts
Best for: Teams working on something jointly  |  Avoid in: Final drafts and formal sign-off

21. Please advise

Terse, formal and best avoided.

Examples:

• “The invoice remains unpaid. Please advise.”
• “Two conflicting instructions have come through. Please advise.”
• “We cannot proceed without a decision. Please advise.”

Why it works: Read the caveat below before using this. It appears on published lists of the most passive-aggressive email phrases, and it hands responsibility over without asking a question.

Formality: Formal, stiff  |  What it actually asks for: A recommendation
Best for: Almost nothing — see the warning below  |  Avoid in: Any message where you want goodwill

22. I’d appreciate your review

Formal, and asks for a process rather than an opinion.

Examples:

• “I’d appreciate your review of the contract before Thursday.”
• “I’d appreciate your review and sign-off on the final figures.”
• “I’d appreciate your review of the changes tracked in red.”

Why it works: “Review” implies checking against a standard and usually ends in approval, which makes it one of the few phrases here that moves work forward.

Formality: Formal  |  What it actually asks for: Review or approval
Best for: Contracts, reports and anything needing sign-off  |  Avoid in: Brainstorms and early ideas

23. Share your perspective when you can

Relaxed about timing.

Examples:

• “Share your perspective when you can — nothing is urgent.”
• “Share your perspective when you can, ideally before the workshop.”
• “No deadline on this one. Share your perspective when you can.”

Why it works: It explicitly removes time pressure, which is generous and also why it frequently goes unanswered. Use it when the answer genuinely is not needed soon.

Formality: Neutral  |  What it actually asks for: Open thoughts
Best for: Long-horizon work and busy recipients  |  Avoid in: Anything with a real deadline

24. I’d be interested in your feedback

Measured and professional.

Examples:

• “I’d be interested in your feedback on how this compares to last year’s.”
• “I’d be interested in your feedback, particularly on the methodology.”
• “I’d be interested in your feedback once you’ve had a chance to read it.”

Why it works: Cooler than “I’d love”, which suits correspondence with people you do not know well. The restraint reads as professional rather than distant.

Formality: Formal  |  What it actually asks for: Specific feedback
Best for: External partners and new contacts  |  Avoid in: Close colleagues, where it sounds stiff

25. Let me know your perspective

Direct and neutral.

Examples:

• “Let me know your perspective on the restructure.”
• “Let me know your perspective — you’ve seen this fail before.”
• “Let me know your perspective on whether the timing is right.”

Why it works: A close relative of the original with “thoughts” swapped for something more specific. “Perspective” suits questions of judgement rather than detail.

Formality: Neutral  |  What it actually asks for: Open thoughts
Best for: Strategy and judgement calls  |  Avoid in: Proofreading and detail checks

26. Thoughts?

One word, and everywhere in chat.

Examples:

• “Attaching the new homepage. Thoughts?”
• “Thoughts? I’m 60% on option B.”
• “Here’s the reply I drafted. Thoughts?”

Why it works: The fastest ask in the language, and it works because the context sits immediately above it. In an email with no context it reads as curt, even irritated.

Formality: Very casual  |  What it actually asks for: Open thoughts
Best for: Slack, Teams and group chats  |  Avoid in: Email, clients and anyone senior

27. Does this work, or should I change anything?

Two doors, both easy to walk through.

Examples:

• “Does this work, or should I change anything?”
• “Does this work for the Berlin office, or should I change anything?”
• “Sending Monday. Does this work, or should I change anything?”

Why it works: It offers approval and criticism as equally acceptable answers, so the reader can reply in four words. Nothing on the competitor’s list gives them that exit.

Formality: Neutral  |  What it actually asks for: Approval or a specific change
Best for: Getting a fast, definite reply  |  Avoid in: Genuinely open brainstorms

28. If I don’t hear back by Thursday, I’ll proceed as drafted

Not a question at all.

Examples:

• “If I don’t hear back by Thursday, I’ll proceed as drafted.”
• “If I don’t hear back by Thursday, I’ll proceed as drafted and send you the final.”
• “Comments welcome. If I don’t hear back by Thursday, I’ll proceed as drafted.”

Why it works: This is the line that ends stalled threads. It names a date, states the default, and makes silence a decision rather than a delay — which is why busy people reply to it.

Formality: Neutral  |  What it actually asks for: A decision by default
Best for: Unblocking work nobody is responding to  |  Avoid in: Asking a superior for permission

Detailed Comparison Table

All 28 alternatives, with formality, what each one genuinely asks the reader to do, and when to avoid it.

Phrase	Formality	What it actually asks for	Best for	Avoid in
I’d love to hear your feedback	Neutral	Specific feedback	Work you have actually drafted	Cold outreach to strangers
What do you think?	Casual	Open thoughts	Peers and people you message often	Formal proposals and large documents
I’d appreciate your input	Neutral to formal	Open thoughts	Asking a specialist or a senior colleague	Work already signed off
Let me know what you think	Casual to neutral	Open thoughts	Internal email and day-to-day work	Clients expecting formality
I’d value your perspective	Formal	Open thoughts	Mentors, executives, advisers	Quick internal checks
Feel free to share your thoughts	Neutral	Optional feedback	Group circulations and open drafts	When you actually need a reply
I’m interested in your opinion	Neutral to formal	A position	Decisions with two or three options	Requests for line-level edits
Could you share your thoughts?	Neutral	Open thoughts	Clients and colleagues outside your team	Casual group chats
I’d love your thoughts on this	Casual	Open thoughts	Colleagues you have a rapport with	Formal client correspondence
What are your thoughts on this?	Neutral	Open thoughts	Almost anyone	Situations needing a yes or no
I’d be grateful for your feedback	Formal	Specific feedback	Senior reviewers and external experts	Quick internal notes
I’d like to know your opinion	Neutral	A position	Choices between clear options	Emotive or sensitive topics
Please share your feedback	Neutral	Specific feedback	Surveys, forms and formal review rounds	One-to-one messages
I’d appreciate your thoughts	Neutral	Open thoughts	General professional use	When you need a decision
Let me know if you have any feedback	Neutral	Optional feedback	Near-final work needing a last check	Early drafts needing real input
I’d welcome your input	Formal	Open thoughts	Committees, boards and formal collaboration	Casual internal chat
I’m keen to hear your thoughts	Neutral	Open thoughts	UK and Commonwealth workplaces	US audiences wanting plain phrasing
Could I get your opinion?	Casual	A position	Instant messages and quick desk-side asks	Formal written requests
What’s your take on this?	Casual	A position	Peers and people you trust	Executives and clients
I’d love your input on this	Casual	Open thoughts	Teams working on something jointly	Final drafts and formal sign-off
Please advise	Formal, stiff	A recommendation	Almost nothing — see the warning below	Any message where you want goodwill
I’d appreciate your review	Formal	Review or approval	Contracts, reports and anything needing sign-off	Brainstorms and early ideas
Share your perspective when you can	Neutral	Open thoughts	Long-horizon work and busy recipients	Anything with a real deadline
I’d be interested in your feedback	Formal	Specific feedback	External partners and new contacts	Close colleagues, where it sounds stiff
Let me know your perspective	Neutral	Open thoughts	Strategy and judgement calls	Proofreading and detail checks
Thoughts?	Very casual	Open thoughts	Slack, Teams and group chats	Email, clients and anyone senior
Does this work, or should I change anything?	Neutral	Approval or a specific change	Getting a fast, definite reply	Genuinely open brainstorms
If I don’t hear back by Thursday, I’ll proceed as drafted	Neutral	A decision by default	Unblocking work nobody is responding to	Asking a superior for permission

Read the third column and the whole problem appears. 14 of these 28 ask only for open-ended “thoughts”, which is the same non-request as the original in fresh wording. Just 3 of them can actually produce a decision — numbers 22, 27 and 28. If your email has been ignored twice, you need one of those three, not a warmer synonym.

Ask for One Thing, Not for “Thoughts”

An open request for thoughts reliably attracts comment on the least important part of your work.

There is a name for this. The law of triviality, described by C. Northcote Parkinson in 1957, holds that “people within an organization commonly give disproportionate weight to trivial issues”. His committee spent two and a half minutes approving a £10 million nuclear reactor and forty-five minutes arguing about a £350 bicycle shed — then over an hour on £21 of annual refreshments. Complex things intimidate people into deferring; simple things everybody feels qualified to debate. The Danish developer Poul-Henning Kamp gave the effect its modern name, bikeshedding, in the BSD community in 1999.

Send a strategy document and ask for “thoughts” and you will get notes on the font. The fix is to name the bicycle shed you are not asking about:

• ✅ “Feedback on the assumptions in section two — ignore the formatting, I’ll tidy it after.”
• ✅ “One question: is the March date realistic?”
• ✅ “I’m confident about the plan and unsure about the budget. Just the budget, please.”
• ❌ “Please let me know your thoughts.”

Marta: Forty minutes on the title font and nobody mentioned the budget.

Declan: Because the budget is hard and the font isn’t.

Marta: So what do I send next time?

Declan: One question about the budget, and tell them you’ll handle the font yourself.

It happens outside work too. Ask a family group chat for “thoughts” on what to write on a welcome home banner and forty messages later the wording is undecided and somebody is arguing about the colour of the card.

Feedback, Approval, or a Decision? They Are Not the Same Ask

Most stalled email threads are one phrase used for three different jobs.

The sender means “approve this”. The reader hears “look at this when convenient”. Nobody is at fault and nothing moves for a fortnight.

What you actually need	Say this	Not this
Comments to improve the work	“Feedback on section two, particularly the assumptions.”	“Let me know your thoughts.”
Permission to proceed	“Are you happy for me to send this Thursday?”	“I’d appreciate your thoughts.”
A choice between options	“A or B? I lean B.”	“What are your thoughts on this?”
A formal sign-off	“I’d appreciate your review and sign-off.”	“Feel free to share your thoughts.”
Anything, from a silent thread	“If I don’t hear back by Thursday, I’ll proceed as drafted.”	“Just following up on my last email.”

Rafael: I’ve sent her that deck three times and she keeps saying she’ll look at it.

Priya: What did you ask for?

Rafael: Her thoughts.

Priya: Ask whether you can send it to the client on Wednesday. She can answer that in one word.

⚠️ “Please Advise” Is the One to Cut

Number 21 on this list is the only entry that can damage a working relationship, and most lists hand it over without a warning.

“Please advise” appears on published rankings of the most passive-aggressive phrases in workplace email, alongside “per my last email” and “as previously discussed”. Three things go wrong with it:

• ❌ It contains no question. The reader has to work out what you are asking, which is the opposite of advising.
• ❌ It transfers the problem. Stating a difficulty and adding “please advise” puts the whole thing in their lap without offering a route out.
• ❌ It reads as a reprimand when repeated. Two “please advise” emails in a week is a chase, and everybody reads it that way.

Replace it with the actual question, plus your own suggestion. “The invoice is still unpaid and the supplier has paused delivery. Shall I authorise it from our budget and recover it next month?” That gets answered. “Please advise” gets resented.

Asking Upward, Sideways and Outward

The same request needs different wording depending on who owes you the answer.

Who you’re asking	What works	Why
Your manager	“Are you happy with this, or would you change the framing?”	They want to spend thirty seconds, not thirty minutes. Give a narrow question and a default.
A senior expert	“I’d value your perspective on whether the board will accept the timeline.”	Asks for judgement, not proofreading, which is what their time is worth.
A peer	“What’s your take on this?” / “Thoughts?”	Informality signals you want candour rather than a polished reply.
A direct report	“Tell me where this is wrong — I won’t be offended.”	They may hesitate to criticise upward, so permission has to be explicit.
A client	“Could you share your thoughts by Thursday so we stay on schedule?”	Polite, dated, and ties their reply to something they care about.
A group of twenty	“Comments in the doc by Friday; I’ll finalise after that.”	Diffused responsibility means nobody replies unless there is a deadline and a default.

One habit outperforms every phrase here: say what happens if nobody answers. A default turns silence into consent rather than a blockage, and it is the same courtesy as naming an exact time instead of asking someone to be prompt. When somebody does drop everything to read your work properly, say what their help actually did rather than thanking them generically.

The Bottom Line

Looking for other ways to say please let me know your thoughts is usually a sign that the last few times you used it, nothing came back.

A warmer synonym will not fix that. Name the one thing you want looked at, say whether you need comments or a decision, give a date, and state what you will do if the reply never arrives. Delete “please advise” entirely.