Helm AI agents are autonomous staff that execute professional services work: running projects, managing accounts, chasing invoices, qualifying leads, and drafting client deliverables. Each agent has a defined role, scoped tool access, and an autonomy level you control. Every agent operates on the same records as your human team.
Three decisions build an agent. Customize further, or deploy the defaults and refine over time.
Step 1
Start from a pre-built role like Project Manager or Account Manager. Or define a custom role with your own name, color, and defaults.
Step 2
Enable the tool groups the agent needs. Toggle read or read-write per group. Add 1000+ external integrations to extend reach.
Step 3
Observe (watch), Suggest (propose + approve), or Auto (execute). Override per channel so email can still require approval.
Chat, email, Slack, or on a schedule. Each channel has its own permissioning and autonomy override.
Open the chat panel in Helm and talk to any agent. Page context comes along for free.
Reach agents on any mailbox the workspace connects. Replies route back through the agent.
@mention an agent in any channel it's invited to, or DM the workspace DM handler.
Run agents on a daily, weekly, or monthly cadence. Output to Slack, notifications, or a task comment.
Agents don't work in isolation. Give each one a place in your org chart, then let them hand work to each other the way a real team would.
Put an agent in a real seat on the org chart, with a title, responsibilities, and a department. The agent carries that identity into every task it works.
Roles report to roles, so the chart shows who answers to whom. People and AI agents sit on the same structure, in the same departments.
An agent can hand a task to a peer agent by name, with handoff instructions. The specialist picks it up and starts working automatically.
A research agent gathers, then hands off to a copywriter agent to draft. Each agent does the part it does best, without you relaying between them.
Deploy a template on day one. Customize the instructions, tools, skills, and autonomy as you learn what your team needs.
Reviews your Klaviyo flows, campaigns, and deliverability weekly, then ranks what to fix.
Drafts and publishes WordPress content, manages media and comments, and watches site health.
Recovers failed payments with personalized three-touch outreach, and escalates the high-value accounts.
Runs client check-ins, drafts recaps and QBRs, tracks account health, and flags at-risk accounts before renewal.
Plans editorial calendars, maintains brand voice, and drafts posts, case studies, and client updates from real project data.
Watches capacity, profitability, and AR, surfaces bottlenecks and at-risk projects, and runs operational summaries automatically.
Your role, your instructions, your tool scope. Skip the templates when your workflow is too specific for an off-the-shelf agent.
Hundreds of predefined skills plus custom skills. Plug domain expertise into any agent, pre-built or custom.
The full tuning surface, shared across every role. Start simple, go deep as you scale.
Start from a template. Or build a custom role with its own default instructions, tools, and autonomy.
Enable specific tool groups (tasks, projects, billing, calendar, analytics, memory, and more). Toggle read or read-write per group.
Observe (watch silently), Suggest (draft and wait), or Auto (execute directly). Flip levels as trust builds.
A fully autonomous agent can still require approval on email. Rare in AI tools, essential for client-facing work.
Layer your own instructions on top of the role's defaults. Enable skill modules for domain expertise and house style.
Agents remember past decisions, scoped to workspace, account, or project. Searchable. Optional. Disable per agent.
Run agents on a daily, weekly, or monthly cadence. Output to Slack, in-app notifications, or a task comment.
Set a monthly USD cost cap per agent. Runs pause when the budget is hit. Usage tracked per run and per month.
Every agent run is logged with the tools called, inputs, outputs, tokens, and cost. Browse history per agent.
Agents read and write to the same data your team edits by hand. No separate database. No broken sync.
Connect a tool once and it shows up as a tool group in every agent config. Toggle read or read+write per agent, exactly the same way you scope native app tools.
A chatbot answers. An agent acts. Helm agents have scoped access to real tools across the platform: creating tasks, sending invoices, drafting emails, posting to Slack. Autonomy levels let you pick how much they decide for themselves. Memory lets them get better at your business over time.
Three layers. First, tool access is scoped: agents only see tool groups you enable. Second, autonomy is configurable: start in Observe or Suggest mode and review every action before approving. Third, per-channel autonomy overrides let you be stricter on client-facing channels like email. Every action is logged.
Yes. An agent can assign a task to another agent by name and include handoff instructions. The receiving agent picks it up and starts working automatically. That's how you chain specialists: a research agent gathers, then hands off to a copywriter agent to draft. Agents also sit on your org chart with roles, departments, and reporting lines, so structure and delegation line up.
Yes. Create multiple Project Manager agents for different client tiers, each with different instructions, tool scopes, and spending limits. Or one Account Manager per major client. No unique constraint on role.
In-app chat, Slack channels and DMs, Email (Gmail connected), and scheduled runs. Each channel has its own permissioning. Invite an agent to a Slack channel with /helm invite. Assign it to a task and it runs. DM the workspace DM handler for cross-project work.
Agents are included in every Helm plan. You set a monthly USD cost cap per agent; runs pause when the budget is hit. Underlying model cost is billed to your workspace, not per-seat. Heavy usage can be tuned with lower-cost model settings per agent.