# How to bump an email politely: 12 follow-up examples > A bump email is a short reply that brings an unanswered message back to the recipient's attention. Learn when to send one, what to write, and when to close the loop. - **Category:** Email Writing - **Published:** August 7, 2026 - **Reading time:** 12 min read - **Author:** Maya Chen, Email Strategy - **Canonical page:** [https://emailbump.com/blog/how-to-bump-an-email](https://emailbump.com/blog/how-to-bump-an-email) To bump an email, reply in the original thread with a brief, useful follow-up. Remind the recipient what needs attention, make the next action easy, and give them enough time to respond. A good bump restores context without pretending that your message is the only thing in their inbox. > **The short answer** > > Wait a reasonable amount of time, reply in the same thread, and write one to three sentences: a neutral reminder, the specific action you need, and any real deadline. Add new information when you have it. If the request is no longer useful, say so and close the loop. ## What does it mean to bump an email? A bump email is a follow-up to an earlier message that has not received a response. Replying to the original thread moves the conversation back into view and keeps the request, files and prior context together. People also call it a nudge, reminder, check-in or follow-up email. The word “bump” describes the action, not the copy you have to send. Writing only “Bump” may work in a familiar internal thread, but it gives an external recipient no help. A useful follow-up says what you need now and makes room for a no, a delay or a different owner. ## How to bump an email professionally - Reply in the original thread so the recipient can see the request and attachments without searching. - Use the existing subject line unless the topic or required action has materially changed. - Assume the message was missed or deprioritized; do not imply carelessness or bad intent. - Name the decision, document or answer you need instead of writing only “following up.” - Include a real deadline only when one exists, with a date, time and time zone when timing matters. - Offer an easy response path: yes, no, a revised date, or the name of the correct person. - Add a useful detail on later follow-ups rather than repeating the same nudge word for word. - Stop when the request is no longer timely, the person declines, or further contact would be unwelcome. ### A simple bump-email formula ```text CONTEXT I'm following up on the proposal below. ACTION Could you confirm whether option B is approved? TIMING OR EXIT If possible, please reply by Thursday at 3 p.m. Eastern. If the project is paused, a quick no is helpful too. COMPLETE EMAIL Hi Jordan—I'm following up on the proposal below. Could you confirm whether option B is approved? If possible, please reply by Thursday at 3 p.m. Eastern. If the project is paused, a quick no is helpful too. Thank you, Maya ``` ## How long should you wait before bumping an email? There is no universal waiting period. Match the delay to the relationship, the size of the request and the deadline already stated. A routine internal answer may justify a reminder after one or two working days. A proposal, application or non-urgent introduction often deserves several business days. An invoice should follow the payment terms, not the sender's impatience. ### Time-sensitive operations **Same day or next working day** Appropriate when a named deadline, outage or customer impact is already understood. ### Routine internal request **After 1–2 working days** Use team norms and the actual dependency rather than an arbitrary urgency label. ### Client feedback or proposal **After 3–5 business days** Give the recipient time to review, then ask for one concrete decision. ### Application or interview **After the stated timeline—or about a week** Do not follow up before a hiring team said it would respond. ### Invoice **On or after the due date** Reference the invoice number, amount and contractual payment date. If your original message said “no rush,” do not manufacture a rush two days later. If circumstances changed, explain the new dependency plainly. The recipient should understand why the timing changed rather than experience the follow-up as pressure without context. ## 12 polite bump-email examples ### 1. Simple professional follow-up ```text Hi Jordan—following up on the note below in case it got buried. Could you let me know whether you'd like to move forward with option B? Best, Maya ``` ### 2. Internal request ```text Hi Sam—could you add your comments to the launch brief by 2 p.m. today? I need them before I send the final version to Support. If you need longer, please tell me what timing works. ``` ### 3. Approval from a manager ```text Bringing this back up before tomorrow's release window. Could you approve the revised copy below, or point me to the person who should? A yes or requested change by 11 a.m. Pacific tomorrow will keep the release on schedule. ``` ### 4. Proposal follow-up ```text Hi Alex—have you had a chance to review the proposal below? The open decision is whether to include the migration workshop. I'm happy to revise the scope, and a quick no is useful if the project is no longer moving ahead. ``` ### 5. Client feedback ```text Hi Priya—following up on the two homepage directions below. Which one should we develop for the next review? If neither is right, one sentence about what is missing will help us reset before doing more design work. ``` ### 6. Invoice reminder ```text Hi Taylor—invoice EB-1042 for $2,400 was due on August 5 and still appears open in our records. Could you confirm its payment status or let me know if Accounts Payable needs another copy or vendor detail? Thank you, Maya ``` ### 7. Job application follow-up ```text Hello Morgan—I'm following up on my application for the Product Engineer role, submitted July 28. I'm still interested and would be glad to provide any additional work samples. Could you share the expected timeline for next steps? ``` ### 8. After an interview ```text Hi Lee—thank you again for last Thursday's conversation. You mentioned the team expected to decide this week, so I wanted to check whether the timeline has changed. I'm still very interested in the role. ``` ### 9. Meeting request ```text Hi Casey—would a 20-minute conversation next week be useful, or should I close this out for now? Tuesday at 1 p.m. and Wednesday at 3 p.m. Eastern both work for me, but I'm happy to use another time. ``` ### 10. Ask for the correct owner ```text Hi Rowan—I'm not sure whether this request belongs with you. If someone else owns the security review, could you point me to them? Otherwise I'll close the request on Friday so it does not keep landing in your inbox. ``` ### 11. Second follow-up with new information ```text One useful update since my last note: the revised plan now fits within the existing budget and no longer needs a new vendor review. Does that resolve the blocker, or is there another concern I should address? ``` ### 12. Final follow-up ```text Hi Jordan—I'll close the loop after this note. If the project becomes a priority later, reply here and I can reopen the proposal with current dates and pricing. No response is needed for now. ``` ## What to write instead of “just following up” “Just following up” is not rude, but it spends the first line without restoring the decision. Keep the neutral tone and replace the vague phrase with context the recipient can act on. ### Decision **Could you confirm which option you prefer?** Names the response instead of merely announcing the reminder. ### Dependency **I need the approved total before Finance closes Friday's payment run.** Explains why the response matters now. ### Status **Has the review timeline changed?** Makes a delay easy to communicate. ### Routing **Are you the right person for this request?** Lets the recipient redirect the thread without solving it themselves. ### Exit **Should I close this for now?** Invites an honest no and ends an unproductive sequence. ## Bump-email phrases to avoid - “As I said in my last email”: often reads as blame. Restate the needed action without the commentary. - “Why haven't you responded?”: assumes intent and makes a simple delay adversarial. - “Please advise ASAP”: gives neither a usable deadline nor the reason behind it. - “I know you're busy, but…”: claims empathy and immediately discounts it. Make the request smaller instead. - “Bump” by itself: acceptable in some close internal relationships, but unhelpful almost everywhere else. - False urgency or invented scarcity: damages trust and makes later deadlines less credible. - A new subject line designed to look unrelated: separates the context and can feel manipulative. ## When to send a new email instead of bumping the thread Start a new thread when the subject has materially changed, the old recipients should no longer see the conversation, sensitive details need a different audience, or the original thread has become too long to navigate. Use a clear subject and link the new request to the old context in the opening sentence. Do not switch threads merely to disguise repeated follow-ups. ## How many times should you bump an email? For ordinary professional requests, one or two follow-ups are usually enough to learn whether the thread is moving. A third message should normally add decisive context or close the loop. The right limit can be lower when the recipient did not ask to hear from you, and higher for an active project, contractual obligation or safety issue with an established escalation path. > **A follow-up is not new permission** > > For marketing and sales email, respect consent, applicable law, organizational policy, opt-outs and suppression status. An unanswered message does not create permission for an endless automated sequence. Operational obligations such as invoices and active-project approvals should follow their documented escalation path. ## Automate the useful reminder—not the pressure Build follow-ups around real customer events, stop the flow when the person acts, and keep subscription and suppression rules attached to every send. - Event-based entry and exit - Waits and conditional branches - Unsubscribe and suppression enforcement [Learn more](https://emailbump.com/features/automations) ## Frequently asked questions ## Is it professional to say “bump” in an email? It can be acceptable in a familiar internal conversation, but it is rarely the most helpful choice. A short sentence naming the request—“Could you approve the attached draft?”—is just as brief and easier to act on. ## Should a bump email stay in the same thread? Usually yes. The original thread preserves the subject, recipients, attachments and prior context. Start a new thread only when the topic, audience or confidentiality needs have changed materially. ## What subject line should a bump email use? Keep the original subject when the request is unchanged. If the required action or deadline has changed, update the subject honestly—for example, “Approval needed by Thursday: revised launch copy”—without pretending it is a new conversation. ## How do you bump an email without sounding rude? Assume good intent, keep the reminder short, state the specific action, explain real timing, and provide an easy no or revised date. Avoid blame, sarcasm and urgency that was absent from the original request. ## Write the rest of the message - [Professional email sign-offs](https://emailbump.com/blog/professional-email-sign-offs) — Choose a closing that fits requests, follow-ups and sensitive conversations. - [COB meaning in email](https://emailbump.com/blog/cob-meaning-in-email) — Write deadlines that survive time zones, weekends and different work schedules. - [Email drip campaign examples](https://emailbump.com/blog/email-drip-campaign-examples) — Design multi-message sequences around a useful next step instead of repetition. - [Email frequency calculator](https://emailbump.com/tools/email-frequency-calculator) — Choose a defensible cadence and document the assumptions behind it.