What Sendslay does today.

Writing and sending the message.

• HTML editor — write here or paste your own markup
• Merge tags with fallbacks — write {{firstName|there}} and an empty field renders your word, not a gap
• Preview and send a test to yourself first
• Plain-text version generated automatically
• Send now or schedule for later
• A sent campaign can no longer be edited — the record stays true

Try versions on a slice of the list; the winner goes to the rest.

• Test two versions on a slice — you choose how big that slice is
• You choose how long to wait before the winner is decided
• Winner picked by opens or by clicks — clicks is the stronger signal
• The winner then goes to everyone who was not in the test
• No opens at all? Version A goes out — the campaign never stalls
• Not yet: statistical significance, and picking the winner by revenue

Rules that decide who a campaign actually goes to.

• Rules on email, first and last name, and your own custom fields
• Status, and which groups someone is in
• Opened or clicked in the last N days — and the reverse, which is how a win-back is built
• Subscribed date; order count and total spend once your shop sends them
• Count the matches before you send
• A campaign can take a segment as its audience

A series that waits, checks and continues on its own.

• Steps: send an email, wait a while, or check a condition
• Triggers you can use today: someone is added to your audience, or joins a group
• Order and cart triggers are ready for when your shop sends us those events
• Every subscriber's run is tracked on its own
• Not yet: a report per automation, and triggers for a field changing or a date arriving

The same campaign arriving at 9 AM everywhere.

• Pick an hour; each timezone gets its own wave
• Uses the timezone stored on the subscriber record
• Not yet: working out a subscriber's timezone on our own

Collecting a list you are allowed to mail.

• A hosted page you can link from anywhere
• A confirmation email before anyone is added — double opt-in
• Consent recorded: source, date and IP
• New signups can drop straight into a group, which can start an automation

Everything about who you send to.

• Subscribers with custom fields of your own
• Groups, with a subscriber in as many as you like
• CSV and Excel import with duplicate detection
• Consent recorded on import — source, date and IP
• Suppression list that survives re-imports

Proving the mail is really from you.

• DKIM keys generated for your domain
• SPF, DMARC and custom MAIL FROM records supplied
• Re-check DNS from the dashboard the moment your records propagate
• Free mailbox providers blocked as sending domains
• Sending stays blocked until the domain verifies

The checks that run before a campaign is allowed to leave.

• Sender chosen, and its domain actually verified
• Audience not empty once suppressed addresses are removed
• Subject line and body present
• Your postal address on file — CAN-SPAM requires it in the footer
• Your own email address confirmed
• Recipients within your daily limit, and sending not paused
• Warnings for a missing preheader or a very short subject

The part most tools leave to you.

• One-click unsubscribe with RFC 8058 List-Unsubscribe headers
• Unsubscribes honoured without a login, a reason or a form
• Suppression only ever hardens — it never returns to mailable
• Postal address rendered into every footer
• Bounces and complaints suppressed automatically, and sending pauses if the rates climb
• Per-account daily send limit enforced at dispatch

How a large campaign actually goes out.

• Sent through Amazon SES from your own verified domain
• Queued and paced rather than fired all at once
• Failed sends retried without duplicating anyone
• Each recipient's state tracked individually
• Anyone who unsubscribes mid-send is skipped, not mailed

What we can tell you after you press send.

• Recipients, unsubscribes, and delivered, bounced and complaint counts
• Opens and clicks, with opens from automated scanners filtered out
• A per-recipient list showing who was delivered, opened, clicked or bounced
• CSV export of that recipient list
• Not yet: revenue attributed back to the campaign that produced it

Running it with other people.

• Team members with Admin, Manager and User roles
• Every change to senders, domains, campaigns and team recorded server-side
• Your plan and daily sending limit visible in settings
• Coming soon: viewing that audit trail yourself

Wiring Sendslay into your own systems.

• API keys with per-key scopes
• Not yet: outbound webhooks for delivery events
• Not yet: published API documentation