Newsletters that arrive
as real conversations.
Most newsletters live behind a third-party ESP that owns the relationship. Replies disappear into the void. Bounces hide in dashboards. A Loomal newsletter agent owns the send identity, the inbox, and the reply loop — so subscribers can actually talk back, and the agent can act on what they say.
API Primitives used
mail_sendSend from a real address
DKIM-signed, threaded by subscriber, sent from your own newsletter identity. No mailing-list shim, no sender-pool roulette.
mail_list_messagesCatch every reply
Subscribers reply directly to the newsletter. Agent reads each one — questions, unsubscribes, feedback — and acts.
mail_replyRespond in-thread
Real questions get real answers from the agent inside the original conversation, not a no-reply black hole.
Newsletters lost the conversation.
Email newsletters started as one-to-many conversations. Then ESPs turned them into one-way broadcasts: replies bounce off no-reply addresses, every link gets wrapped, and subscribers learn that emailing back is pointless. The relationship that newsletters were supposed to build dies the moment the ESP touches it.
An agent flips the model. The newsletter ships from a real address the agent owns. Subscribers reply, the agent reads, and the agent answers — at machine scale, with human-feeling depth. That's a newsletter that earns subscribers instead of leasing them.
How to build it.
mail_sendDraft and send
Agent writes the issue (or you do) and sends from the newsletter identity. DKIM keeps it out of spam without a third-party ESP in the middle.
mail_list_messagesRead every reply
Agent polls the inbox after each send, classifies replies as question, unsubscribe, feedback, or noise, and decides what to do.
mail_replyAnswer in-thread
Real questions get real answers. Unsubscribes are honored instantly. Feedback gets routed to whoever owns the newsletter strategy.
Example prompt
“Send tomorrow's newsletter to my list at 9am Eastern. Read every reply, answer the questions inline, honor any unsubscribe requests, and forward strategy feedback to my main inbox.”
What teams build.
Founder newsletters
Solo writers run real-conversation newsletters where the agent answers most replies and escalates the interesting ones.
Product release notes
Engineering teams ship release notes from a product agent identity that fields questions in-thread.
Community digests
Curated weekly digests where subscribers can reply with picks, and the agent threads them into next week's issue.
Internal newsletters
Companies run internal updates from an agent identity that fields HR or ops questions inline.
Subscriber onboarding
New subscribers get a multi-touch onboarding sequence with real responses to any question they reply with.
Why newsletters belong in your own inbox.
ESPs make newsletter mechanics easy — and the customer relationship rented. The list belongs to the platform, the deliverability is shared, and the conversation is one-way by design. None of that fits a brand that actually wants to talk to its readers.
Loomal gives you a real identity, a real inbox, and an agent that can scale the conversational side. You keep the list, the reputation, and the audit trail — and the newsletter becomes a channel readers can actually answer.
DKIM by default
Every newsletter is cryptographically signed; deliverability is yours, not borrowed.
Per-issue audit
Sends, replies, and unsubscribe events are logged against the agent identity that ran the issue.
List stays internal
Subscriber addresses live in your vault, not a third-party ESP's database.
Make your newsletter a real conversation.
Real inbox, real replies, fully autonomous.