sendvia's dashboard runs Amazon SES campaigns from a browser: mailing lists, templates and a newsletter editor, no AWS SDK or code required.
Yes, once someone has set up the AWS side and verified a domain, and this part of sendvia is what that someone hands off. Composing a newsletter is a visual editor by default, built on Quill, with bold, italic, lists, headings, colour and image insertion on its toolbar; a second tab holds the raw HTML for anyone who wants to paste a template built elsewhere, and a third holds a plain-text fallback. Subject line, sender name, reply-to and a from-address picked from a dropdown of your verified domains round out the form, and open and click tracking are on by default with a toggle to turn either off per send.
Merge tags use {{name}}, {{email}} or any custom column your subscriber CSV carried in under its own header, and an unwritten tag renders as blank rather than breaking the send. An unsubscribe link goes in automatically if you never typed one, and every newsletter carries the List-Unsubscribe and List-Unsubscribe-Post headers Gmail and Yahoo look for, so the one-click unsubscribe those inboxes show is there without any extra setup.
A list takes subscribers two ways: paste them in with an email column and sendvia processes the paste immediately, or upload a CSV and a background job works through it while a progress bar updates the page every five seconds. Anyone who bounces, complains or unsubscribes anywhere on your account is cross-referenced against every list automatically, shown greyed out with its reason rather than silently vanishing.
A one-click migration path exists for Sendy.co exports specifically, and it does more than copy addresses across: it reads each subscriber's status column and decides what belongs on your blocklist and how broadly it should apply.
| Sendy status | Blocklist reason | Scope |
|---|---|---|
| unsubscribed | unsubscribed | newsletters only |
| unconfirmed | unsubscribed | newsletters only |
| bounced | bounce | newsletters only |
| hard bounced | bounce | everything, including transactional mail |
| soft bounced | bounce | newsletters only |
| complained | complaint | everything, including transactional mail |
A separate filter builder lets you write rules against email, name or any custom field, equals, not equals, contains, starts with, is empty or is not empty, chain several together, preview a count of who matches, and only then remove them. Nothing is deleted on the first click.
A template is a name, an optional URL-safe alias, a subject and an HTML or plain-text body, edited in the same dashboard the newsletters use. Once one exists, the API accepts template_alias on a send call in place of a full body, filling in {{variables}} from whatever the request passes, so a marketer can rebuild a receipt or a welcome email's wording without anyone touching the codebase that sends it.
Before anything goes to a real list, a preview renders the HTML with merge tags filled in from a chosen subscriber, or a random one from the selected lists if you leave that field blank, and a separate button sends a live test to one address of your choice. A recipient breakdown modal runs the actual maths before you commit: total subscribers across the lists you picked, minus duplicates on more than one list, minus anyone blocked, minus anyone a segment filter excludes, down to the number who will actually receive it.
Sending itself is queue, pause, resume or stop, and a newsletter that already went out can be extended to additional lists afterwards, an operation that skips everyone who received it the first time round rather than sending them a second copy.
Someone still has to do the AWS side before any of this opens up: an AWS account, an IAM user with SES and SNS permissions, and a verified sending domain, which starts inside Amazon's sandbox at 200 emails a day to addresses you have separately verified until Amazon's review clears, typically in 12 to 24 hours. That work sits on the dashboard page, not here.
Those SNS permissions are what let SES notify sendvia the moment a message bounces, is complained about, suffers a delivery delay or is rejected outright. A bounce or a complaint is also what feeds the audience cleaning described above and the blocklist behind it; a delivery delay or a rejection just shows up in your send history, without touching anyone's subscriber status.
Lists, newsletters, segments and templates are all premium features: $19 a month buys 100,000 emails a day across 10 domains, against 250 a day on the free plan, where none of this compose screen is reachable at all. A single API send still tops out at 50 recipients regardless of plan, which is why a genuine mailing list runs through the newsletter tools rather than through repeated API calls.