This guide covers implementation, configuration, daily use and troubleshooting for Small Business Management – Transactional Email.
Small Business Transactional Email Implementation Guide
Product: Small Business Transactional Email / Small Business Management – Transactional Email
Version covered: 1.0.3
This guide covers provider setup, WordPress mail fallback, SMTP, Elastic Email, Brevo, templates, logs, retry queue and suite handoff from Forms, CRM, Accounting and Service Desk.
Purpose and separation from bulk email
Transactional Email is the operational delivery layer for business-critical messages. It should be kept separate from Bulk Email Marketing so campaign sending does not affect invoice, quote, ticket or customer notification deliverability.
| Plugin | Responsibility |
|---|---|
| Transactional Email | Invoices, quotes, statements, support tickets, CRM notifications, form confirmations and admin alerts. |
| Bulk Email | Newsletters, campaigns, promotional messages and nurture journeys. |
| CRM | Contactability, customer records and timeline context. |
| Forms | Routes notification delivery through Transactional Email when active. |
Provider setup
Version 1.0.3 supports WordPress mail, SMTP-ready settings, Elastic Email API and Brevo API options. Choose one provider for production and send test messages before enabling suite notifications.
- Use a verified sending domain.
- Configure SPF, DKIM and DMARC with your email provider.
- Store API keys securely.
- Use separate sender profiles for transactional and bulk email where possible.
- Keep a test email address available for diagnostics.
Templates and testing
- Open Transactional Email > Templates.
- Review the default template purpose.
- Use preview/test sending before live use.
- Confirm placeholders render correctly.
- Check the Email Log after sending.
Logs and retry queue
The log records what was attempted, which source plugin triggered it, the email type and the delivery result. Failed messages should be reviewed before retrying so repeated provider or recipient errors are not ignored.
Suite handoff rules
| Source plugin | Transactional email role |
|---|---|
| Forms | Admin notifications and customer confirmations. |
| CRM | Task/follow-up notifications, approved templates and sales alerts. |
| Accounting | Invoices, quotes, statements and payment notices when integrated. |
| Service Desk | Ticket creation, assignment, update and closure notifications when integrated. |
Go-live checklist
- Take a full file and database backup before installing on a production site.
- Install on a staging site first when replacing an older build or changing roles.
- Confirm the required parent plugin is active before activating a Pro or Enterprise add-on.
- Use a non-admin test user to confirm menu access and permissions.
- Create one test record, run through the full workflow, and only then import or enable real customer data.
- Send a test email through each configured provider.
- Confirm logs are created.
- Trigger one form notification and confirm it routes through Transactional Email.
- Verify failed email retry behaviour with a safe test recipient.