Email is what keeps a support desk running when nobody is watching the inbox screen. AWP Support Desk sends plain-text transactional notifications for the events that matter, through your WordPress installation’s own mailer — no external service is involved. This guide explains who receives what, how to choose the mailbox and what is never emailed.
Who receives what #
| Event | Recipient | Language |
|---|---|---|
| New ticket | Notification mailbox | Site language |
| Customer reply | Notification mailbox | Site language |
| Agent reply | The ticket’s customer | Customer’s profile language |
| Ticket closure | The ticket’s customer | Customer’s profile language |
| Ticket assignment | The assigned agent | Assignee’s profile language |
| Internal note | No email | — |
Every row is automatic: nothing to schedule, nothing to trigger by hand. A typical flow looks like this — a customer opens a ticket and the staff mailbox gets the notice; the agent replies and the customer gets the answer in their inbox; the agent assigns a colleague and that colleague gets the assignment notice.
Email sending is also fail-soft by design: if a message cannot go out, the ticket action still succeeds.
Choose the mailbox #
- Open Support Desk → Settings.
- Find the Notification mailbox field.
- Enter the address that should receive new tickets and customer replies — a shared desk address such as
support@example.comworks well. - Save. If you leave the field empty, notifications fall back to the site administration email address (set in Settings → General).
You can change the mailbox at any time; the change applies from the next event. The wizard in Support Desk → Setup sets this same field during onboarding, so if you ran the wizard you have already done this once. The messages are informational: replying to them does not reach the desk, because turning email into tickets belongs to the Pro add-on.
What the emails contain #
Every message is plain text with the ticket reference, the subject and an excerpt of the message that triggered it, followed by a link back to the portal (for customers) or to the ticket (for staff). Long customer messages arrive as an excerpt rather than the full body, so an oversized reply cannot produce an undeliverable email.
Staff mail is written in the site language; customer and assignee mail uses the language of their WordPress profile, so a multilingual team gets mail it can read.
Deliverability basics #
WordPress sends the email, so deliverability follows your site’s sending setup:
- If notifications do not arrive, check the spam folder first.
- Ask your host or mail provider about SPF and DKIM records for your domain — that is generic WordPress email setup, not a plugin setting.
- Messages go out as plain text, so there is no HTML to break in strict mail clients.
- The plugin sends through the standard WordPress mail stack; if the site struggles to send any mail at all, an SMTP plugin is the usual fix.
- Send yourself a test ticket from the portal and confirm it lands in the mailbox before going live.
What is never emailed #
- Internal notes. They are staff-only on the ticket detail screen and never reach any mailbox.
- Deactivation feedback. When an administrator deactivates the plugin from the Plugins screen, an optional screen offers to send one feedback email with a reason chosen from a closed list. It contains no site URL, no ticket content and no addresses, and it is sent only when you explicitly choose to. Bulk and WP-CLI deactivations never email anything.
- Nothing else leaves the site. While the plugin is active it makes no external calls; ticket content stays in your database.
One honest note for planning: version 1.0.0 has no switch to turn ticket notifications off — every event in the table above sends its email to its recipient. If you must block the one-off deactivation feedback email (for example on sites with strict outbound-mail policies), add this to the site:
add_filter( 'awp/feedback/send_deactivation_notice', '__return_false' );
Next steps #
The mailbox works together with the screens: agents pick tickets up in the agent inbox, and customers follow the same conversation in the customer portal. If you are still wiring things up, the installation guide sets the mailbox during the setup wizard. The product page describes what the Pro add-on adds, including email piping with multiple mailboxes.