Email & notifications
Who gets emailed on which action, when admin-bar markers show up, how to turn emails on and off, where templates live, and how delivery modes affect things. The rules are exact — if you read this page end-to-end you can predict every email the plugin will send.
Who gets emailed when a new update is created?
It depends on who created it and what was attached:
- The creator never gets emailed about their own action. They just did it — they know.
- The assignee (if one was picked when the update was created) gets an “assigned to you” email. The note body is included only if a note was written when the update was created; otherwise the email is just the basic info plus a link.
- The customer gets emailed if the update is customer-visible. Same rule on the body — only included if a customer note was attached at creation.
Why doesn’t the creator get emailed about their own actions?
Because they did the action — sending them a confirmation email about something they just did is just noise. This rule holds everywhere: post a customer note, get no email. Mark an update solved, get no email. Reassign it, get no email. The plugin assumes if you just clicked a button, you don’t need an inbox copy of it.
The one exception is the “auto-reopen on customer reply” case — if the customer’s reply reopens a solved update, your team still gets the participant email because the customer caused it, not you.
Who’s notified when I add a customer note?
Three groups, minus you (the one who posted the note):
- The customer. Always. The customer note body is the whole point of the email, so it’s included.
- Every participant on the update. Participants = creator + current assignee + everyone ever @mentioned on this update + every staff member who’s posted a note here. You (the poster) are skipped; anyone who muted the update is also skipped.
- The assignee. The assignee is always a participant, so they’re covered as part of the group above.
Who’s notified when I add an internal note?
Two groups, minus you (the one who posted the note):
- @mentioned teammates get a dedicated mention email with the note body and a link straight to the update card.
- Other participants (creator + assignee + people who already replied, minus the @mentioned in this note, minus you, minus anyone who muted the update) get a participant email with the note body.
- The customer gets nothing. Internal notes never reach the customer in any way — not by email, not in the portal, not in any export.
What’s a “participant”?
A participant is anyone who is involved in a particular update. The list is built fresh every time an email is sent: the creator, the current assignee, every staff member ever @mentioned on this update, and every staff member who has posted a note here. It grows as the thread grows — reply to a thread once and you’re a participant from then on.
The participants list also shows up in the “Participants” tab on the update card (avatar + name + role tag), so you can see at a glance who’s following the thread. Reassigning to a new person doesn’t remove the old assignee from the participant list — they stay on as a past assignee, which is useful for hand-offs.
What about status changes — do those send emails?
Yes, but the email is short — just the event line, no note body:
- Assignee gets a “status changed” email so they know things changed.
- Customer gets a “status changed” email if the update is customer-visible.
- Creator (if they changed the status themselves) gets nothing — they did it.
If you want a status change to also explain what changed, post a customer note at the same time — that’s the “here’s what changed and why” pattern.
What about assignee changes?
Both the old assignee and the new assignee get an email — the old one so they know the update is no longer theirs, the new one so they know it’s now on them. The customer gets no email; instead they see a small “reassigned” marker in their portal’s customer-notes thread, so they aren’t surprised if a new name shows up on the next reply.
What happens when I flip an update from hidden to customer-visible?
The first time an update goes from hidden to customer-visible, the customer gets one “a new update is now visible on your order” email. Later toggles (visible → hidden → visible again) don’t send the email again — the plugin remembers whether the update was ever visible, so the customer’s inbox doesn’t fill up if you toggle visibility while sorting things out.
What about when I delete an update?
You’re asked to choose: Silently delete (saves the deletion in the activity log, no email) or Notify customer (sends a short notice that the thread has been closed, then deletes). It’s a two-button dialog on purpose because either choice can be the right one depending on what happened — the plugin won’t pick for you.
Can staff mute a noisy update?
Yes. On the update card there’s a per-user Get notifications switch. Turn it off and you’ll stop getting both the email and the admin-bar markers for that one update — one switch controls both.
The mute is saved per-user-per-update (in user-meta), so it’s personal — muting an update for yourself doesn’t affect your teammates. Other emails (@mentions, assignments) still come through; only the back-and-forth chatter on the muted update is skipped.
What’s the difference between “Send immediately” and “Send in background”?
Three modes under Settings → Emails → Delivery mode:
- Automatic (recommended). The plugin checks whether your host’s Action Scheduler is working and uses background mode if it is, immediate mode if not. Best default for most stores.
- Send immediately. Every email goes out right away, inside the request that caused it. Admin pages take a bit longer (they wait for SMTP), but emails never get stuck — if SMTP is working, the email goes.
- Send in background. Emails are added to a queue and sent on the next WP cron run. Admin pages load fast. But if WP cron is broken on your host (common on cheap shared hosting), the queue just sits there. Only pick this if you’ve checked that cron works.
If customers report missing emails, the first thing to try is switching to Send immediately — that rules out the queue as the cause.
Where do I edit the email subjects, recipients, or copy?
Per-email settings live under WooCommerce → Settings → Emails — the same place where you edit every other WooCommerce email. Each of the plugin’s emails (nine of them) shows up as a row, and clicking opens the WC email editor for that one email: on/off toggle, subject line, heading, recipient (where it makes sense), and the template file to override.
The Order Updates → Emails tab is a focused list of just your emails with quick toggles and direct links into each editor — useful when you don’t want to scroll through twenty WooCommerce emails to find the four you want to change.
How do I override an email template?
The same way you override any WooCommerce template. Copy a template from plugins/order-updates-for-woo/Templates/emails/ into your-theme/woocommerce/emails/order-updates-for-woo/. WooCommerce will find your copy first and use it instead of the original.
For a step-by-step walkthrough, see Developer Guide → Email customisation. That page lists which template to copy for which email, the variables you get to use in each, and the plugin’s email-render helpers if you’re building a fully custom template.
Can I disable a specific email type entirely?
Yes — every one of the nine emails has its own on/off switch (the standard WooCommerce email switch). Common example: turn off the “customer rating follow-up” emails if you don’t want the second round of promoter / detractor messages, but keep all the regular customer-update emails on. You can switch each email on or off on its own — it isn’t all-or-nothing.
What are the promoter and detractor follow-up emails for?
After a customer rates a solved update, a second email goes out based on the score:
- Promoter follow-up (4–5 stars): a thank-you with four social-share buttons (Facebook, X, LinkedIn, WhatsApp), each pre-filled with a share message you can edit. Goal: turn a happy customer’s rating into a public mention of your store.
- Detractor follow-up (1–3 stars): a warm, helpful message with a button straight back to the update so the customer can keep talking with your team. The site admin also gets a heads-up email so a senior team member can step in quickly.
You can change the promoter / detractor cutoff under Settings → Customer → Follow-up email after rating. Either follow-up can be turned off on its own.
Does the plugin email anyone outside my install?
No. Every email is sent through your site’s own wp_mail() — the same path WordPress and WooCommerce use for every other email. No part of the plugin sends to any outside service to deliver a notification.
The only outgoing request to a non-WP destination is the newsletter subscribe form, and only if you, the admin, actually type your email and click subscribe. That request goes to a Cloudflare Worker run by the plugin author, and it sends nothing about your customers or orders — just the admin email you typed.