"Per My Last Email": What It Signals and What to Say

People reach for 'per my last email' because following up when someone has not replied is genuinely awkward, and the phrase feels like a way to apply pressure while staying polite. Most recipients read it differently: as a rebuke dressed in professional language. This post covers what the phrase signals, why it tends to backfire even when the frustration behind it is legitimate, and what to write instead — along with the follow-up structure that makes a second chase rarely necessary.

What 'per my last email' actually signals#

On the surface, the phrase means 'as I noted in my previous message.' In practice it carries a second layer that almost every professional recognises: I already said this, I should not have to say it again, and I want you to know I noticed. The gap between those two readings is precisely what makes it difficult to use.

The recipient cannot tell which version the writer intended. The phrase can signal a genuine reminder — you believe your email was simply missed in a busy inbox — or an implicit accusation — you believe they read it and chose not to act. Because both readings are plausible, most people default to the more pointed one. A phrase that allows an accusation without stating it occupies a particular role in professional communication: it gives the writer plausible deniability, and that is exactly what gives it the passive-aggressive quality recipients respond to.

The phrase persists because following up is awkward in a specific way. Re-stating the information without any reference to the earlier message can feel like you failed to notice they ignored you, while referencing the earlier message risks the tone described above. There is no obviously clean middle ground, and 'per my last email' sits uncomfortably in that gap — which is why people reach for it and then immediately regret it.

• It sounds neutral but reads as passive-aggressive to most recipients
• The ambiguity is the core problem: the phrase functions as both a reminder and an accusation, and readers default to the second reading
• A direct re-statement of the specific ask delivers the same pressure without the subtext

Before you write that follow-up#

Before deciding what to write, it is worth spending a moment on why the reply has not arrived. The right follow-up approach differs significantly by cause, and a mismatch between your message and the actual reason often produces a second silence rather than a response.

The most common cause is volume. Your email arrived, was read, was noted as something to handle later, and later became never. This accounts for the majority of unanswered professional messages and usually has nothing to do with the importance of the request. A short, clear re-ask at the top of a new message is almost always sufficient.

The second cause is a missing clear action. If the original email did not specify exactly what you needed and by when, the path of least resistance is to do nothing until the matter resurfaces. You may have been clear in your own reading of the message. The recipient was not sure what the next step was, so they took no step at all.

The third cause is deliberate avoidance. The recipient has a reason not to respond — they disagree with the direction, they are waiting on someone else, or they are hoping the matter resolves itself. This is the least common of the three and the one most people assume first. Starting from that assumption tends to produce follow-ups that are too confrontational for what is almost always a workload or clarity issue.

The follow-up approach changes significantly depending on which cause applies. The same message sent for different underlying reasons produces different results, and using the wrong approach for the actual cause often generates a second silence rather than a resolution.

How to follow up without sounding annoyed#

1. 1

   Open with the ask, not the history

   Do not re-introduce context. Do not reference the previous email in the first sentence. Open with the specific action you need: 'Could you confirm the vendor date before Thursday?' or 'I need a decision on the proposal before we can book the slot.' The reader already received the context. What they need now is a clear ask surfaced at the top, not a reminder that they missed the first one.

2. 2

   Attach the deadline or name the consequence

   A follow-up without a deadline is a request, not pressure. Name the specific date or the downstream outcome that changes if they do not act: 'We need a confirmed date by Wednesday or the vendor will release the slot to another client.' This converts the message from a nudge into something the recipient can act on, approve, or escalate to someone who can.

3. 3

   Offer the escape hatch

   Most silences come from uncertainty rather than bad intent. A sentence like 'If the scope has changed or you are waiting on something, let me know and I will adjust' lowers the cost of responding. It also separates the overwhelmed colleague from the deliberate avoider — the person who is blocked will take the opening, and a deliberate avoider will not — which tells you what kind of problem you are actually dealing with.

4. 4

   Keep it shorter than the original

   Follow-up emails should be shorter than the first message, not longer. A long second email signals that you are expecting resistance, which puts the recipient on the defensive before they have read a word. Two to four sentences is the target. If the situation genuinely requires more than that, the right tool is a phone call rather than a longer email in a thread that is already going unanswered.

5. 5

   If a second email also fails, change the channel

   If the second attempt also goes unanswered, a direct message on whichever channel the person actually monitors — Slack, Teams, a text — is more effective than a third email. At that point you have confirmed the problem is not message volume. Something else is happening, and a different medium will surface it faster than another message in a thread they are already not responding to.

How the right approach changes by context#

The same underlying logic applies in every situation: lead with the ask, name the deadline, offer the escape hatch. But the specific language needs to match the relationship and the stakes.

One variable the table cannot capture is geography. Communication directness varies between regions and professional cultures. A message that reads as appropriately direct in one context can seem curt or evasive in another. Where a relationship spans different professional cultures, err toward shorter and more explicit: fewer words, cleaner ask, stated consequence rather than an implied one.

What to do when the polite approach does not work#

If a well-constructed follow-up also produces no reply, the issue is usually not the wording. The message arrived. The non-response has become a decision rather than an oversight, and treating it as a wording problem will produce a third email that also goes nowhere.

Change the channel. Email is asynchronous by design, which makes it easy to defer indefinitely. A direct message on Slack or Teams, or a short phone call, operates at a different urgency level. The shift in medium signals that the matter has moved from background to active without requiring a more confrontational tone in the message itself.

For anything with contractual or operational weight, one email that names the consequence of silence creates a documented record and raises the cost of continued non-response: 'If I do not hear back by Friday I will proceed with option A.' Write it once, without accusation, and follow through on what you said. A stated consequence that is honoured is more effective than any number of polite follow-ups.

If an internal colleague is blocking progress and direct contact has produced no movement, a brief note to a shared manager framed as a process observation is appropriate: 'I want to flag that approval for X is still pending before we can proceed.' Keep it factual, reserve it for when direct contact has genuinely failed, and have a record of your prior attempts ready.

A faster way to track and send follow-ups#

The steps above work. The overhead is the tracking: knowing which conversations are waiting for a reply, from whom, and since when, becomes its own problem when you are managing a dozen or more open threads simultaneously. The cognitive cost of maintaining that list grows faster than the number of threads, and most people end up either over-chasing or losing track entirely.

AI Emaily handles this at the thread level. It surfaces conversations that are waiting for a response at the right moment, then drafts a follow-up using your user-set Personal Context brain and any client-specific profile you have configured — so the tone matches the relationship rather than sounding like a generic reminder. Every draft sits in your approval queue before it sends, and every action is captured in the audit log so nothing goes out unreviewed. We build AI Emaily.

If keeping track of who owes you a reply takes more mental bandwidth than actually thinking through what to say, that is the problem it was designed for. Try it at app.aiemaily.com.