DutyTick Send

Coming soon.

Email from your own domain, at volume. Transactional messages like notices, invoices, payslips and verification codes, and campaigns like newsletters, product updates and offers, sent properly so they reach the inbox. Bounces and unsubscribe requests are handled for you.

An account and a domain are all you bring, then you are sending. Send carries mail out for you. It is not a mailbox, and if inboxes on your own domain are what you want, that is DutyTick Mail.

Transactional messages

• Invoices, payment confirmations and reminders.
• Notices, announcements and account statements.
• Payslips and verification codes.
• Anything that must reach a person reliably, in volume.

Campaigns

• Newsletters and product updates.
• Offers and launches, sent to the people who asked for them.
• Your own lists, your own schedule, no per-campaign middleman.

Getting started

1. Sign up, and your dashboard is there.
2. Add the domain you want to send from.
3. Publish the DNS records it hands you. Copy and paste, nothing to work out.
4. Wait for them to verify.
5. Collect your sending credentials, and send.

You publish those records once. Key rotation and everything else behind your domain happens on our side afterwards, so you are not back in your DNS every time something changes.

Your domain, authenticated

• SPF, DKIM and DMARC set up the way receiving providers expect, rather than left to you to work out.
• Your own signing key, generated for your domain and used for nobody else's.
• Keys rotated on a schedule, with no window where mail goes out unsigned.
• Mail leaves as you: your domain in the signature, your domain in the return path, ours nowhere in sight.
• Point your DMARC reports at us and we read them, so you find out who else is sending as you.

How you send

• SMTP, on the standard submission ports, so most software needs a host, a username and a password and nothing more.
• Or the API, for anything that would rather talk to us directly.
• More than one set of credentials per domain when you want them, so campaigns and transactional mail stay apart and a campaign cannot spend the reputation your payslips depend on.
• Parameters, examples and everything specific arrive with the API documentation when Send opens.

How long a message is worth sending

A verification code that arrives forty minutes late is worse than one that never arrives. A newsletter that goes out on Thursday instead of Tuesday is nobody's problem. Those are not the same message and they should not be retried the same way.

So each set of credentials carries its own deadline, set by you. Give the transactional one thirty seconds and anything that cannot leave in thirty seconds is reported back to you rather than delivered stale. Give the campaign one forty eight hours and it will keep working through a receiving provider's slow patch without you watching it. One domain, both behaviours, decided by which login the message came in on.

Limits that grow with you

A new domain is a stranger to Gmail, Outlook and Yahoo, and a stranger that sends a hundred thousand messages on its first day is treated as one. So we start you slow, on purpose.

• We watch what the large providers do with your mail: accepted, deferred, bounced, marked as spam.
• Send well and your ceiling rises on its own, without you asking for it.
• Send badly and it comes down here first, before a receiving provider decides for you and takes longer to forgive.
• No warm-up plan for you to run and no schedule for you to keep to.

Capacity is not the thing in short supply. Your reputation is, and that is the part worth protecting.

Delivered, not lost

• Your domain is set up properly, so mail is trusted rather than dumped in spam.
• Addresses checked before sending, so bad ones do not cost you.
• Hard bounces and complaints suppressed automatically, and those addresses never mailed again on any of your credentials.
• One-click unsubscribe honored for you, the way the large providers now require of anyone sending in bulk.

You can see it working

• Delivered, bounced and complained, live per message run.
• A domain verification walkthrough when you connect a new domain.
• Daily and weekly delivery reports.
• Webhooks into your own system for every message sent, every bounce and every complaint, so your records match ours without anyone checking by hand.

Credits

• Top up by card or by bank transfer, whichever your accounts team prefers.
• Credit is spent as you send. Nothing renews on you and there is nothing to cancel.
• A webhook and an email while you are still running, not once sending has stopped.

Ask for early access and you will hear when Send is ready: request early access.