Buying email software is easy. Buying the right email software is the bit where your brain starts asking questions at 2am 😅
Here are the answers to the ones we get most.
✅ Clear answers. 🧠 Real-world detail. 📬 Built for WordPress people.
ASI is a standalone Newsletter + Mass Mailer plugin for WordPress built for disciplined sending, clean data, and proper reporting.
It includes campaign tools, templates, segments, sending adapters (WP Mail / SMTP / Sendmail-Exim), tracking (opens/clicks/unsubs), list hygiene, exports, PDF reports, and a built-in debug system.
Both 😄 The UI is designed so non-technical users can run campaigns safely, while power users still get the switches, logs, exports, and controls they want.
If you can build a WordPress page, you can run ASI.
ASI improves deliverability by enforcing best-practice behaviour: clean suppression, easier unsubscribes, compliance headers, list hygiene, and smarter segmentation.
But deliverability also depends on your domain reputation, content, and authentication (SPF/DKIM/DMARC).
Think of ASI as the “no silly mistakes” layer that keeps you on the rails ✅
Yes, if your server and sending setup can handle it. ASI is built for scale, batching, and safe queue-based workflows.
Your throughput will depend on your chosen sending adapter (WP Mail / SMTP / Sendmail-Exim), server resources, and warm-up strategy.
ASI won’t promise fantasy numbers… but it will help you run real-world sending properly 📬⚙️
Need serious throughput? Check out our Large Scale Email Servers for high-volume sending infrastructure.
Yes. ASI includes sending adapters so you can choose the delivery method that matches your stack:
WP Mail (simple), SMTP (common), and Sendmail/Exim (fast, server-driven).
You can switch adapters without rebuilding your campaigns.
No. ASI is built for permission-based sending.
If you send junk, you’ll burn your reputation, harm inbox placement, and create complaints.
ASI gives you the tools to do it properly, but it can’t make bad practices good.
Licenses are per-site (with options depending on your package). You’ll receive updates and support while your license is active.
If you run multiple sending sites for capacity or segmentation, choose a multi-site option that matches your setup 🧾✅
If a product is defective and we can’t fix it, we’ll make it right.
But we do not refund for misuse (spam sending, dirty lists, blacklists, “I ignored warm-up and now my domain is on fire” 🔥😅).
If you’re unsure, start with a smaller setup and prove performance step-by-step.
Yes. ASI supports modern List-Unsubscribe behaviour so mailbox providers can show native unsubscribe UI.
This reduces spam complaints and keeps your program healthier ✅
ASI helps operationalise compliance: unsubscribes, suppression hygiene, logging, and proof-ready exports where data exists.
You still need correct policies and legal notices, but ASI makes the mechanics easier and safer 🛡️📜
Yes. These are DNS-level authentication signals and are strongly recommended for deliverability.
ASI works perfectly alongside SPF/DKIM/DMARC, but it can’t replace them. ✅🔒
ASI supports queue-based sending and disciplined workflows that make warm-up easier, but warm-up is still a strategy:
start small, increase gradually, watch bounces/complaints, and keep content consistent.
ASI helps you run the process without chaos 🔥➡️✅
ASI includes hygiene tools and suppression logic so once someone unsubscribes or hard-bounces, you don’t keep emailing them.
This protects reputation and reduces “how did they get this again?” complaints 🙃
Campaign performance (opens, clicks, unsubscribes), link-level click tracking, scheduled exports, and branded PDF summaries.
You can pull clean CSVs that open properly in Excel/Sheets without “CSV archaeology” 🧑🔬📄
Yes. ASI supports link-level click exports so you can build laser-targeted follow-ups:
“clicked pricing,” “clicked demo,” “clicked checkout,” etc. 🎯🔗
Yes. ASI supports scheduled exports saved to /wp-content/uploads/reports/ so your team can grab files or feed automations.
Yes. ASI logs key operational events (exports, reports, debug capture windows, retention actions) so you can prove what happened and when 🧾✅
A built-in viewer that helps you catch issues without server file digging:
PHP errors/notices, filtered noise, cron timing, export events, and mail header context.
Toggle it on, reproduce the problem, get answers 🔎🛠️
It’s designed for short capture windows and low overhead.
Enable it, capture the issue, export what you need, disable it ✅
In your uploads folder, typically:
/wp-content/uploads/reports/ and /wp-content/uploads/reports/export-logs/
Yes. If you hit an issue, send the details and (if relevant) an exported log view.
The goal is fast diagnosis, not endless “have you tried turning it off and on again?” 😅
✅ I’m sending to people who actually opted in (no shady lists).
✅ I want clean reporting, clean exports, and fewer “why is this broken?” moments.
✅ I want sending discipline, not “hit send and hope” 😅
If something isn’t covered here, send it over.
I’d rather answer a question early than help you unpick a headache later 🧠✅
