"Please advise" sits at the bottom of countless business emails, often doing very little work. Writers reach for it when they want a response but aren't sure how to ask for one cleanly. The result is a phrase that feels polite on the surface but frequently reads as vague, demanding, or oddly cold. This article explains what "please advise" actually communicates, when it's acceptable, and how to replace it when it isn't.
What "please advise" actually means
At face value, "please advise" is a request for guidance or information. It's grammatically correct. It's been a fixture of business correspondence for decades. But the problem isn't correctness. The problem is what the phrase implies to the person receiving it.
When a reader sees "please advise" with nothing else, a few things happen. First, they're left to figure out what kind of response is wanted: a decision, an opinion, a timeline, a yes or no. Second, the phrase can feel like it's placing the burden entirely on them, without much context or effort from the sender. Third, the construction has a slightly bureaucratic ring that doesn't land well in fast-moving, informal-but-professional environments.
None of that is fatal. But it's worth knowing what you're signaling before you hit send.
When "please advise" is fine to use
The phrase works best when three conditions are met: the context is already clear, the reader has the authority or knowledge to respond, and the relationship is formal enough that a crisp sign-off fits the tone.
In legal, finance, and compliance writing, "please advise" carries an established meaning. A paralegal emailing outside counsel asking whether a clause is enforceable can end with "please advise" and the reader knows exactly what's needed. The industry context does the heavy lifting.
It also works in short reply chains where the question has already been posed and "please advise" is just the closing nudge. If the body of the email spells out the situation and the specific decision point, the closing phrase adds no confusion.
The short version: "please advise" is fine when everything around it is clear. It becomes a problem when it's used to avoid being specific.
When to avoid it
Skip "please advise" in three situations.
- When the request is actually a question. If you need a yes or no, ask for a yes or no. Don't wrap it in a vague closing phrase.
- When the email is cold or semi-cold. Sending "please advise" to someone who barely knows you reads as presumptuous. It assumes they owe you guidance without earning that assumption.
- When the relationship is warm and conversational. If you'd normally write "let me know what you think," using "please advise" instead creates unnecessary distance.
The phrase also irritates a specific kind of reader: anyone who finds it vague. Those readers will email back asking what you actually want. That's a second round-trip you didn't need.
Better alternatives, matched to what you actually need
The fix is almost always to name the specific thing you're asking for. That sounds obvious, but "please advise" persists precisely because writers skip this step. Here's how to replace it.
If you need a decision: "Could you confirm which option you'd like us to proceed with?" or "Please let me know your preferred approach by Friday."
If you need information: "Could you share the current contract number for this account?" or "I'd appreciate any guidance on the approval process."
If you need an opinion: "Does this approach work for you?" or "What's your read on this?"
If you need someone to take action: "Please review and send back your comments by end of week." Don't dress up a request for action as a request for advice.
Notice that each of these replaces one vague phrase with a specific ask. The reader knows exactly what to do. That specificity is what makes emails move faster.
The tone problem no one mentions
There's a related issue that goes beyond clarity. "Please advise" can come across as slightly passive-aggressive when used after a complaint or a problem has been laid out. Imagine an email detailing a vendor error, three paragraphs long, ending with "please advise." The reader feels accused and then handed the problem with no guidance on what a solution looks like.
In those situations, a collaborative framing works better: "I'd like to resolve this quickly. Can we set up a brief call this week?" or "Happy to discuss options. Let me know what works for your schedule." That's the same request, but it signals partnership rather than frustration.
Related to this is the broader question of how you close requests. Phrases like "thank you in advance" carry a similar risk: they sound polite, but they can feel presumptuous depending on context. Knowing when a conventional sign-off helps and when it doesn't is one of the cleaner skills in professional writing.
What about "kindly advise"?
Some writers, particularly in South Asian and Southeast Asian business English, use "kindly advise" as a common and conventional closing. In those contexts, it reads as standard courtesy, not as stiff or presumptuous. If your reader is in that tradition, "kindly advise" is fine.
Outside those contexts, "kindly" adds formality without adding warmth. It often reads as either old-fashioned or sarcastic, depending on how the rest of the email is written. When in doubt, cut it.
A note on "please see attached" and similar phrases
The "please advise" problem belongs to a family of phrases that business writers reach for when they want to sound professional but haven't committed to a specific ask. "Please see attached" has the same structure: technically correct, often a placeholder for a clearer sentence. In both cases, the fix is the same. Say what you need, and say it directly.
If you're working through a document or email and find yourself typing "please advise," pause. Ask: what do I actually want the reader to do? Write that instead. It takes five extra seconds and saves the reader from having to guess.
Vague closings don't signal professionalism. Specific ones do.