Subagents

Give each job its own focused helper.

Search knowledge, write a record, look up a product, or draft a follow-up — without stuffing every tool into one overloaded agent. Subagents keep conversations sharp and actions reliable.

How it works

Specialize the hands, keep the brain clear

  1. 01

    Pick one job

    Knowledge search, AI Form write, product lookup, email draft — one clear responsibility each.

  2. 02

    Attach the tools

    Give that helper only the knowledge, AI Forms, or connected apps it needs.

  3. 03

    Bind it to the agent

    Your main agent calls the right helper when the conversation needs that action.

  4. 04

    Reuse across agents

    The same AI Form writer can serve support and sales agents without rebuilding it.

Capabilities

What subagents are good at

Anything that should be accurate, repeatable, and separately tunable.

Knowledge search

A helper that only looks things up — so answers stay grounded in your docs.

AI Form writes

Create leads, tickets, and feedback with the exact fields you defined.

Connected app actions

Draft email, look up Shopify products, update a CRM — one job, clear permissions.

Post-conversation review

A special kind of subagent that runs after the chat ends — extract fields and take follow-up actions.

Cheaper routing

Keep the main conversation lean; send heavy tool work to a helper built for that task.

No-code setup

Instructions, tools, and output shape — configured in the builder, not a framework.

In practice

Why teams split work this way

One mega-agent that can do everything usually does nothing reliably.

Clearer conversations

The visitor-facing agent stays focused on talking; helpers handle the mechanics.

Safer permissions

Only the email helper can touch email. Only the AI Form helper can write records.

Easier iteration

Improve product lookup without touching your support tone — and vice versa.

Shared building blocks

One well-built helper serves every agent that needs that skill.

FAQ

Common questions

Do I need subagents on day one?

No. Start with a simple agent and knowledgebase. Add focused helpers when you want reliable writes, lookups, or follow-ups.

Is a post-conversation reviewer a subagent?

Yes. Conversation intelligence uses a subagent that runs after the session ends — with its own fields and optional actions.

Can one agent use many subagents?

Yes. Bind the helpers that match that agent's job — support might get knowledge + tickets; sales might get leads + email.

7-day free trial · no credit card

Try it this week. Tell us what broke.

We’re still early. You may hit a rough edge — we’re sorry when you do, and we fix it quickly. Start a 7-day trial on any plan, put an agent on a page, and tell us what you needed that wasn’t there.