Knowledge search
A helper that only looks things up — so answers stay grounded without cluttering the main prompt.
How it works
Specialize the hands, keep the brain clear
- 01
Pick one job
Knowledge search, datastore write, product lookup, email draft — one clear responsibility each.
- 02
Attach the tools
Give that subagent only the knowledge, tables, or connected apps it needs.
- 03
Bind it to the agent
Your main agent calls the right helper when the conversation needs that action.
- 04
Reuse across agents
The same datastore 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.
Datastore 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 datastore 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.