Docs · Agents
The email agent.
The email agent writes the inbox. It drafts cold emails that read like you, not like a template, paces sends so spam filters don't see a robot, sequences follow-ups, and stops the moment a real reply or opt-out lands. It sends from your mailbox, not a shared sender pool, so your domain reputation belongs to you.
Quick facts
- Channel
- Email (your mailbox, SMTP/IMAP)
- Auth
- App password against your provider
- Lives at
- /dashboard/team/eli
- Day-one ceiling
- 50 sends, ramps automatically with the warmup
- Hand-off trigger
- Any reply, including auto-replies that look human
- Setup time
- About three minutes, see Email setup.
What it actually does
The email agent reads the list you give it, pulls the public signal it can find on each contact (company, title, recent funding, hiring posts), and drafts an opening that references one real thing. Sends pace themselves across the day so the mailbox doesn't look like a fire-hose, the day-one cap is 50 and the warmup ramps it up over the first two weeks. Follow-ups go on a schedule you set on the campaign, the sequence stops on the first reply or unsubscribe.
How it protects your domain
- Real warmup, not a fake one. The email agent ramps daily volume the way Google and Microsoft expect a real human to ramp, not by blasting day one then dropping.
- Bounce-aware. A bounce on a contact takes that contact out of the rest of the sequence, no second send to a dead address.
- Auth-failure pause. The moment your provider rejects the password (rotation, 2FA reset, admin policy change), the email agent flips the account to disconnected and stops sending so you don't burn deliverability on a broken auth loop.
- Plain-text by default. No HTML templates, no tracking-pixel block, no opening-rate inflation, just clean text that reads like you wrote it on a phone.
Where it fits
Single-channel work, you launch an Email campaign from the dashboard, point the email agent at a list, and walk away. Inside an omnichannel flow the email agent is the email step, and the omnichannel agent decides when it fires relative to the LinkedIn agent's message and the demo agent's demo send. Either way replies come back to your real inbox, you handle the conversation the way you always have.
How to put it to work
- Connect a mailbox, walkthrough here.
- Build or import a list on /dashboard/leads. A CSV with a work-email column is enough.
- Click
+ New campaign, pick Email, set the subject and body (or let Ciela draft them), choose the follow-up cadence, hit Launch. - Watch sends, opens, and replies on /dashboard/team/eli.
Keep reading
Need help?
Ciela can walk you through any step. Or write to support@ciela.ai and we'll jump on the connection with you.