Mass Transactional Emails: For When You Actually Have to Reach Everyone
Mass Transactional Emails let you send important, non-marketing communications — privacy policy changes, terms of service updates, maintenance windows, system status — to every relevant Contact, bypassing their marketing unsubscribe status.
This is a small but important feature with very clear rules.
When a customer unsubscribes from your marketing emails, they're opting out of marketing. They are not — and legally cannot be — opting out of operational communications about the service they pay you for. "Our privacy policy changed" is not a newsletter.
Paminga's Mass Transactional Email mode is how you handle those communications correctly.
How It Works
Flag any Send-It! Automation, Drip Series, or Workflow as Transactional in its settings. When you do:
- The send goes to every qualifying Contact, regardless of marketing-unsubscribe status
- Contacts who are unsubscribed from marketing email still receive the message
- Bounced contacts and hard-deleted contacts are still excluded
The flag lives in the same Settings step you'd configure anyway — one checkbox.
Three Places You Can Flag It
The same model is exposed in every relevant automation:
| Automation | Where the checkbox lives |
|---|---|
| Send-It! | "Send as Transactional Email" in the Send-It setup |
| Drip Series | "This is a Transactional Drip Series" in General Settings |
| Workflow | "This is a Transactional Campaign" near the bottom of Workflow Settings |
Same effect everywhere. Pick the automation shape that fits the communication.
When to Use It
A short, opinionated list:
- Changes to terms of service or privacy policy
- Upcoming maintenance windows affecting service
- System status notifications for paid services
- Account-state changes (password reset, payment failure, etc.)
That's it. That's the list.
When NOT to Use It
❌ Don't send marketing email as transactional. Ever.
✅ Do treat the Transactional flag as a respect-the-recipient gate: would they reasonably consider this an operational communication they signed up for by being your customer?
The risks of getting this wrong are not abstract:
- Spam reports
- Domain reputation damage
- Reduced overall deliverability — for all your email, marketing and otherwise
- Violation of Paminga's terms of service
If you have to think about whether something qualifies, it probably doesn't.
A Word From Paminga's Side
We added a friendly warning in the UI when you check the Transactional box — not to slow you down, but to make sure the choice is intentional. Most teams use Mass Transactional a handful of times a year, on big policy or operational moments. That's about right.
Get Started
- Pick the automation that fits your message — Send-It! for a one-shot, Drip Series for a sequence, Workflow for branching
- Build the send like any other
- In the Settings step, check the Transactional flag
- Confirm the recipient lists are what you want — everyone qualifies, including unsubscribed contacts
Read the Mass Transactional Emails docs to dig in.
