Client email, tied to the work.
Helm Email is the agent layer on top of your Gmail. Connect your mailbox, scope agents to a project, and they read inbound mail, draft replies in-context, and wait for your approval. Or let them send directly. Autonomy is yours to set. Messages send from your real address so your deliverability stays yours.
Built into the platform. No add-ons, no integrations, no per-feature pricing.
OAuth-connect Gmail or Google Workspace. No new inbox to learn, no migration to plan. You keep using Gmail for everything else.
Agents see inbound threads and draft context-aware replies, pulling from project history, CRM, deals, and invoices as needed.
Suggest mode queues every agent draft in a dedicated approval inbox. Edit it, send it, or reject it. Nothing goes out without you.
Auto mode skips the approval step. Set per agent, per channel. Use it for internal-only or low-stakes comms until you trust the output.
A fully autonomous agent can still require approval on email. Rare in AI tools. Essential for anything client-facing.
Restrict a mailbox connection to a single project. The agent only sees threads in that scope. No cross-client mixing, no accidental leaks.
Set Email up once. The rest of the platform uses it forever. One data layer, no sync, no glue scripts.
Agents with CRM access cross-reference contacts and accounts when drafting.
Scope a mailbox connection to a project so drafts stay in that project's context.
SDR agents draft outreach; sales reps respond to inbound with full deal context.
Payment Recovery agents draft dunning emails using real invoice status and payment history.
Connect your Gmail or Google Workspace mailbox and optionally scope it to a project. Agents watch inbound threads and draft replies with full context pulled from the connected project, your CRM, open deals, and outstanding invoices. You decide whether the agent writes, proposes, or sends. Helm isn't trying to replace your email client. It's the AI layer on top of the one you already use.
Every agent runs in observe, suggest, or auto mode. Observe watches silently and flags what it would say. Suggest drafts a reply and parks it in the approval inbox. Auto sends directly. Autonomy is set per agent and can be overridden per channel, so an agent you trust with Slack might still require approval on email.
Replies send through your own Gmail, so the client sees your real address. Deliverability and DMARC stay governed by your provider, not a shared sending pool. And because every draft is project-scoped, an agent running for one client can't surface or leak context from another.
Your inbox is full. AI tools live in separate apps. Every reply requires you to piece together context from Gmail, your CRM, your project tool, and memory. Automation means generic templates that clients can smell from a mile away.
Agents read your Gmail, draft with full client and project context, and wait for your approval. Or run on autopilot, your call. Every draft sends from your real address with the context a human reply would have.
A client replies to a thread you missed while traveling.
Account Manager agent drafts a context-aware response and parks it in the approval inbox. One click to send.
An invoice hits fourteen days overdue.
Payment Recovery agent drafts a dunning email referencing prior payment patterns. Sends from your address after approval, or auto if you trust it.
A cold prospect replies for the first time.
Sales Dev Rep agent drafts the follow-up with tone matched to the lead and the deal stage. Queued for your review.
You hire a new agent for a single client project.
Scope the Gmail connection to that project. The agent only sees threads in that scope. Never touches other clients' mail.
AI staff with scoped access, configurable autonomy, and the same data your team uses.
No. Helm is the AI layer on top of Gmail. You keep using Gmail for everything you do today. Helm adds agents that read inbound mail, draft replies in context, and queue them for your approval or send them directly based on autonomy level.
Not today. Gmail and Google Workspace are the supported providers currently. Outlook support is on our roadmap but no committed timeline.
Two ways. First, you can scope a mailbox connection to a specific project, so the agent only sees threads in that scope. Second, agents can call CRM, deal, invoice, and project tools during drafting, based on their configured permissions. There is no automatic thread-to-contact linking today.
Yes. Agents with autonomy set to 'auto' send directly through your connected mailbox. Agents on 'suggest' queue drafts in an approval inbox. Agents on 'observe' watch without acting. You can override the autonomy level for email specifically, so an agent that's 'auto' elsewhere can still require approval on client-facing email.
Helm sends through your Gmail account, so deliverability and DMARC are governed by your own provider. We don't route through a shared pool. Your address, your reputation.
Not today. Helm Email is purpose-built for agent-drafted 1:1 correspondence. Templates, scheduled sends, open/click tracking, and file attachments are not in scope for the current release. For bulk email and broadcasts, connect a tool like Klaviyo via Composio and let agents drive it from there.
Every app included. Agents come standard. Per-workspace pricing, no per-seat tax.
Get Early Access