Transactional Email is built for mail your site or app sends because someone did something: receipts, password resets, order updates, contact-form notifications. Kept to that, it lands in inboxes. Used for bulk mail, it stops doing so for everyone on the platform.
What to send, and what not to
| Send it | Not here |
|---|---|
| Receipts, invoices, confirmations | Newsletters and campaigns |
| Password resets, sign-in codes | Cold outreach of any kind |
| Order and shipping updates | Anything to a purchased or scraped list |
| Notifications the recipient asked for | Mail to people who did not sign up |
Newsletters belong with a service built for them, which will handle unsubscribes and list hygiene properly.
Reading deliverability events
Open the plan under Hosting, then Transactional Email. Each sending domain shows recent events as they happen:
- Hard bounce: the address does not exist. Stop sending to it; repeated hard bounces hurt the domain's reputation.
- Soft bounce: a temporary failure such as a full mailbox or a busy server. Delivery is retried; no action needed unless it keeps happening.
- Spam complaint: the recipient marked the mail as spam. Remove the address and ask why they received something they did not expect.
Verified domain, every time
Mail only sends from a domain whose DKIM and Return-Path records are verified. If a domain shows Setup DNS on the page, its records are missing or wrong; see Set up Transactional Email (SMTP & API).
Getting a full trace
Need to know exactly what happened to one message? Open a ticket with the sending domain, recipient address and time, and we pull the delivery log.