Provision

Email per agent

An AI email agent with
a real inbox of their own.

The thing that makes an AI email agent actually work is that the email address belongs to them, not you. Replies go to their inbox. Triage happens there. Follow-ups land there. You stop being copied on every routine reply because the agent isn't in your inbox — they're in theirs. Provision provisions every agent a real address at @provisionagents.com with full deliverability handled.

Start 48h free trialSee an example ↓

Why most "AI email" tools don't actually fix the inbox

Most AI email products today fall into one of two patterns. The first is a copilot inside your inbox — Superhuman AI, Gmail's Help me write — that drafts replies for you to review and send. The second is a plug-in that triages your inbox, suggests labels, and surfaces the urgent stuff. Both keep you in the loop on every email. Both leave you doing the actual work.

The thing missing in both is autonomy at the right boundary. You don't want every customer support reply to come to your inbox for review. You don't want every outreach follow-up to wait for your sign-off. You want the routine work to disappear from your view entirely — handled by an agent, with you only looped in when judgment is genuinely required. That requires the agent to have its own inbox, not yours.

An AI email agent with their own address is structurally different. The work happens in their inbox. They reply directly. Inbound replies come back to them. Your inbox stops filling up with the agent's work — only the actually-needs-you stuff bubbles up via Slack ping or escalation.

How a Provision AI email agent works

Setup is one click. Operationally, here's what happens day to day with an agent like Echo (Inbox & Outreach) running on Provision.

  1. 1. Provision creates the inbox

    When you onboard the agent, Provision allocates an address (e.g., echo@provisionagents.com), configures SPF/DKIM/DMARC, and warms the IP reputation. You don't touch DNS or SMTP.

  2. 2. The agent sends from their address

    When you ask the agent to follow up on yesterday's signups in Slack, they draft and send the emails from their address. Recipients see "From: Echo <echo@provisionagents.com>" — not your name.

  3. 3. Replies come back to the agent

    When a recipient replies, the email lands in Echo's inbox. The agent reads it, classifies it (interested, not interested, question, objection, opt-out), and decides what to do.

  4. 4. The agent acts autonomously where appropriate

    For routine cases — answering a common question, scheduling a meeting via their calendar, sending a quick clarification — the agent replies directly. The whole exchange happens without you being copied.

  5. 5. The agent escalates when you're needed

    For ambiguous cases, the agent posts in Slack: "@you — got an interesting reply from Acme. They're asking about a custom integration; want me to draft a response or pass to sales?" Full thread context attached.

  6. 6. Daily digest in Slack

    Every morning the agent posts a Slack digest: 12 inbound replies handled, 3 follow-ups sent, 2 escalated to you, 0 opt-outs. You see what they did without seeing the work itself.

What teams use AI email agents for

Outbound SDR motion

An SDR agent (Avery) sends 30 personalized emails a day from their own inbox, handles routine replies, books meetings via their calendar, and hands engaged leads to a human AE in Slack.

Inbound triage and reply

A support or success agent (Echo) handles 60 inbound questions a day from their inbox, escalates the 3 that need a human, and posts a daily digest.

Outreach for content/PR

A marketing agent (Buzz) reaches out to 20 podcast hosts a day from their inbox, follows up twice, and books interviews on your calendar.

Operational follow-up

An ops agent (Sage) chases overdue invoices, follow-ups on stalled tasks, and routine vendor coordination — all from their address, none from yours.

Customer onboarding

An onboarding agent emails new signups, sends day-3, day-7, and day-14 nudges, replies to questions, and escalates the few who need a human call.

Recruiting outreach

A recruiting agent emails sourced candidates from their inbox, schedules screens, and replies to common questions before a recruiter touches the conversation.

Why Provision for your AI email agent

  • Real inbox per agent at @provisionagents.com (or your domain on enterprise).
  • Deliverability handled — SPF, DKIM, DMARC, IP warmup, monitoring.
  • Inbound parsing and reply routing built in.
  • Same agent across email, Slack, Telegram, Discord, and Web Chat — one identity, one memory.
  • Daily digest in Slack so you see results without seeing the work.
  • Escalation to humans on judgment calls, with full context.
  • Open source core — audit or self-host.
  • $99/mo flat. 48-hour free trial.

FAQ

What is an AI email agent?
An AI email agent is an AI worker with their own email address — they send, receive, read, draft, and reply autonomously. The crucial detail is the address: it's the agent's, not yours. Replies come back to them. They handle their own inbox.
Why does the email address need to belong to the agent?
Because half the value of an email agent is autonomous handling of inbound mail. If they send from your address, replies come to you and you're back in the loop. If they send from their own address, replies land in their inbox and they handle them. The whole point is to remove the human from the routine middle.
How does Provision provision the email inbox?
Each Provision agent automatically gets a real address at @provisionagents.com (or your custom domain on enterprise plans), with full SPF/DKIM/DMARC alignment, transactional-grade deliverability, and inbound parsing for replies. You don't configure SMTP or DNS yourself.
Can the AI email agent use my existing email address?
Yes — Provision can connect to your Gmail or Microsoft account via OAuth, in which case the agent operates inside your inbox (drafts replies for review, applies labels, etc.). Most teams prefer the dedicated agent inbox model because it keeps the agent's work separate from your own and avoids accidental sends from your account.
How does the AI email agent decide who to reply to?
It reads incoming mail, classifies by topic and urgency using your team's training (which it learns from a few weeks of work), drafts replies for routine cases, and escalates anything ambiguous to you in Slack with full context. You stay in the loop on judgment calls; the agent handles the rest.
Is the email agent a separate tool from the Slack agent?
No — same agent, multiple surfaces. The marketing agent ("Buzz") that lives in your Slack also has buzz@provisionagents.com. They're one identity with one memory across both channels. A reply that comes in via email becomes context the agent uses next time you @-mention them in Slack.
Are the agent's emails actually delivered (not spam)?
Yes. Provision handles SPF, DKIM, DMARC, IP reputation, and warmup so agent emails land in inboxes, not spam folders. This is the single hardest part of building email-for-agents yourself, and it's the main thing teams pay $99/mo to skip.
Can the AI email agent use my company domain?
On enterprise plans, yes — agents at @yourcompany.com with full deliverability. Most teams start at @provisionagents.com and migrate to a custom domain when ready.

Hire an agent. Hand them an inbox.

48 hours free. $99/mo after. Cancel anytime.

Start 48h free trial