LOOMAL
AI Cold Email Outreach

Cold email that actually
lands in the inbox.

Most AI cold-email tools route through a shared sender pool or your personal Gmail — which gets you flagged, throttled, or banned. Loomal gives your outreach agent its own DKIM-signed address, its own reputation, and a real inbox that catches every reply for follow-up.

mail.sendmail.list_messagesmail.reply

API Primitives used

mail.send

Send from a real address

Each agent gets a DKIM-signed sending identity. Outbound messages pass SPF, DKIM, and DMARC — no shared pool, no spoofed headers, no spam-folder roulette.

mail.list_messages

Detect replies automatically

Poll the inbox for new threads. extractedText strips quoted history so your LLM sees only the prospect's words — clean signal for intent classification.

mail.reply

Reply in-thread

Respond inside the original conversation. Subject lines, message-ids, and threading headers are preserved — your follow-ups look human, not robotic.

Shared sender pools kill deliverability.

Cold email at scale is a deliverability problem before it's a copywriting problem. Outbound platforms route thousands of messages through shared IPs, which means one bad sender poisons everyone. Your perfectly written campaign gets dropped because someone else's spam complaint tanked the pool's reputation that morning.

The other common workaround — having an agent send from a human's Gmail — is worse. Gmail caps automated sending, flags volume spikes, and locks the account when it sees outreach patterns. You lose the campaign and the primary inbox at the same time.

How to build it.

01

Provision the outreach identity

Create a Loomal identity for the campaign. It gets its own email address, its own DKIM key, and its own sending reputation — isolated from every other agent in your org.

02mail.send

Send the first touch

The agent generates personalized copy and sends it through mail.send. DKIM headers carry the delegation chain so recipients can verify who authorized the send.

03mail.list_messages

Watch the inbox, follow up

Poll for replies. When a prospect responds, the agent reads extractedText, classifies intent, and either replies in-thread or queues a follow-up.

Example prompt

Send a 3-step cold sequence to the 50 prospects in my CSV, personalized from their LinkedIn bio. Detect replies, classify them as interested / not-now / unsubscribe, and forward the interested ones to my inbox.

What teams build.

Founder-led outbound

Solo founders run 200-prospect sequences from a dedicated agent identity. Replies route to their personal inbox; the agent handles everything else.

Multi-segment campaigns

Each ICP gets its own agent identity and sending reputation, so a low-performing segment never drags down the high-performing one.

Reply-driven nurture

Agent classifies replies into hot / warm / cold and pushes hot leads to the human rep with full thread context attached.

Re-engagement

Agent identifies stale leads in the CRM, sends a tailored re-open message, and books meetings when prospects respond.

Event-triggered outreach

Funding round, hire, product launch — agent monitors signals, drafts a relevant message, and sends from its own address within minutes.

Why agents need their own sender identity.

Cold email is regulated by reputation. Mailbox providers track who sends what, and every send either earns or burns trust. When your agent borrows a human's address, every campaign risks the human's primary inbox. When it sends through a shared pool, it inherits other senders' baggage.

Loomal gives each campaign its own identity, its own DKIM key, and its own audit trail. If a sequence underperforms, you retire the identity and spin up a new one — without touching anything else. That's the isolation outbound at scale actually requires.

DKIM, SPF, DMARC by default

Every outbound message is cryptographically signed and aligned. Recipients can verify the sender; you stay out of the spam folder.

Per-identity reputation

Sending reputation is scoped to the agent identity. One bad campaign doesn't poison your other senders.

Full delegation chain

Every message traces back to the human who authorized the agent. Compliance teams get the attribution they need.

Related use cases

Give your outreach its own inbox.

DKIM-signed sending, real reply detection, per-campaign identity isolation.