Deliverability

Staying out of the spam folder.

Agent-sent mail is held to the same standard as any other. What actually decides whether it arrives:

Authenticate the domain

SPF, DKIM and DMARC. On carlyemail.com this is already done. On your own domain, verification sets it up — do not skip DMARC, which is increasingly the difference between the inbox and the spam folder at the large providers.

CarlyEmail also requires TLS for outbound delivery, uses SES's optimized shared delivery for agent mail, and suppresses recipients after a permanent bounce or spam complaint. It does not add tracking pixels or rewrite links for open and click tracking.

Warm up

A new domain sending thousands of messages on day one looks exactly like a compromised one. Start with tens per day and grow over a couple of weeks.

Watch the two numbers that matter

GET /v0/metrics/events returns the raw message.sent, message.bounced and message.complained counts needed to watch each organization. SES evaluates a representative volume rather than a fixed time window, so these figures are an early warning rather than a reproduction of AWS's account-level calculation.

Passing authentication is necessary, not a guarantee of inbox placement. A new domain with almost no history can still land in spam while mailbox providers learn its reputation. A recipient replying, starring the message, or marking it "not spam" is a stronger positive signal than adding another DNS record.

Send mail people expect

The single biggest lever, and the least technical. An agent replying to someone who wrote in first will essentially never be marked as spam. An agent emailing strangers will be, no matter how well the DNS is configured.

Give people a way out

Honour unsubscribe requests immediately. A complaint costs roughly ten times what an unsubscribe does, and the person is equally gone either way.