Skip to main content
One agent is powerful. Multiple agents — each with their own specialty — can run different parts of your business. Think of it like building a team. Instead of one generalist who does everything, you can have specialists:
  • A sales agent who focuses on leads, pipeline, and closing deals
  • A support agent who handles customer questions and troubleshooting
  • A marketing agent who creates content, manages campaigns, and tracks engagement
  • An admin agent who handles scheduling, reminders, and internal operations
Each agent is its own “person” — with its own name, personality, knowledge, and rules. But they all work in the same workspace, so they share your CRM data, contacts, and deals.

​
Why Would I Want Multiple Agents?

​
Specialization Makes Agents Better

An agent that focuses on one thing can be really, really good at it. When a sales agent only needs to know about pricing, pipeline stages, and closing techniques — without also worrying about support tickets, content creation, and HR policies — it’s more accurate, faster, and more consistent.

​
Different Roles Need Different Personalities

Your sales agent should be friendly, persuasive, and proactive. Your support agent should be patient, thorough, and empathetic. Your marketing agent should be creative and brand-aware. One personality doesn’t fit all.

​
Cleaner Knowledge Management

Instead of uploading every document to one agent, you can give each agent only the knowledge it needs:
  • Sales agent gets: pricing guide, sales scripts, competitive analysis, objection handling
  • Support agent gets: troubleshooting guides, FAQ, product documentation, escalation procedures
  • Marketing agent gets: brand guidelines, content calendar, audience personas, campaign briefs
This means each agent’s answers are more focused and accurate.

​
How Multiple Agents Work

​
What’s Shared (Workspace-Level)

All agents in your workspace share:
  • CRM data — contacts, deals, tasks, and pipeline
  • Workspace-level knowledge — any knowledge files you assign to “all agents”
  • Integrations — email, calendar, and other connected services
This means if your sales agent creates a contact, your support agent can see it too. If a deal moves to “Closed Won,” all agents know about it.

​
What’s Separate (Agent-Level)

Each agent has its own:
  • Name and personality — different identity, different communication style
  • Instructions and rules — different playbook for different situations
  • Agent-specific knowledge — files assigned only to that agent
  • Memory — each agent keeps its own notes and learnings
  • Schedules — each agent runs its own automated tasks
  • Chat conversations — each agent has its own chat panel

​
Example: A Three-Agent Setup

Let’s say you run a software company. Here’s how you might set up three agents:

​
Agent 1: Sam (Sales)

  • Personality: Friendly, confident, action-oriented. Uses a warm professional tone.
  • Knowledge: Pricing guide, sales scripts, competitive comparison, case studies, ROI calculator
  • Instructions: “When a new lead comes in, calculate a quote, draft a personalized response, and add them to the pipeline. Follow up on stale deals weekly. Never discount more than 15% without flagging it.”
  • Schedules: Daily lead check at 8am, weekly pipeline review on Mondays, follow-up reminders daily at 10am

​
Agent 2: Jordan (Support)

  • Personality: Patient, empathetic, thorough. Always makes sure the customer feels heard.
  • Knowledge: Product documentation, troubleshooting guides, FAQ, known issues list, escalation procedures
  • Instructions: “When a customer reports a problem, check the troubleshooting guide first. If the issue isn’t there, log it as a new issue and escalate. Always follow up within 24 hours.”
  • Schedules: Daily unresolved ticket check at 9am, weekly support summary on Fridays

​
Agent 3: Riley (Marketing)

  • Personality: Creative, on-brand, data-driven. Writes in the company voice.
  • Knowledge: Brand guidelines, content calendar, audience personas, previous campaign performance data, social media guidelines
  • Instructions: “Create content that matches our brand voice. Always check the content calendar before suggesting posts. Track engagement metrics for all published content.”
  • Schedules: Weekly content ideas on Mondays, social media performance report on Fridays, monthly content calendar generation on the 1st
Each agent is a specialist. Together, they cover your whole operation.

​
Creating a New Agent

To add another agent to your workspace:
  1. Navigate to your workspace sidebar
  2. Click the + New Agent option (or equivalent in your workspace settings)
  3. Give it a name, title, and personality
  4. Upload knowledge files specific to this agent’s role
  5. Set up its instructions and rules
  6. Configure any schedules it should run
Or just ask an existing agent:
You: I want to create a new agent for customer support. Call it Jordan, make it patient and thorough, and I’ll upload the support docs later.
Your existing agent can help you set up the new one.

​
Assigning Knowledge to Agents

When you create or upload a knowledge file, you choose who can access it:
  • All agents — Every agent in the workspace can read this file. Use for company-wide info: team structure, general policies, company overview.
  • Specific agents — Only selected agents can access this file. Use for role-specific info: sales scripts go to the sales agent, troubleshooting guides go to the support agent.
You can change these assignments anytime. If your marketing agent suddenly needs access to the pricing guide (maybe it’s creating a marketing one-pager about pricing), just add it.

​
Managing Multiple Agents

​
The Sidebar

Each agent appears in your sidebar. Click on an agent to:
  • Open its chat panel
  • View its schedules, knowledge, and work
  • Access its settings
You can switch between agents quickly — it’s like switching between conversations with different team members.

​
Keeping Agents in Their Lane

The most common mistake with multiple agents is overlap — two agents that do the same thing, or an agent trying to handle something outside its specialty. To avoid this:
  • Give each agent a clear, specific role. “Sales” and “support” are clear. “General assistant” is not.
  • Put the role boundaries in the instructions. “You are the sales agent. If someone asks about a support issue, tell them to contact the support team or direct them to Jordan.”
  • Assign knowledge carefully. Don’t dump every file into every agent. Give each agent only what it needs.

​
When to Use One Agent vs. Multiple

Start with one agent and add more as you need them. There’s no rush to set up multiple agents on day one. Get comfortable with one agent first — learn how to teach it, correct it, and build its knowledge. Then when you notice a specific area that could benefit from a specialist, create a new agent for it.

​
Frequently Asked Questions

Not directly — agents don’t have conversations with each other. But they share CRM data, so actions one agent takes (like creating a contact or updating a deal) are visible to all agents.
Yes. CRM data (contacts, deals, tasks, pipeline) is workspace-level. All agents in the same workspace can see and work with the same data.
Yes. Each agent can use a different model. You might put your sales agent on a model that’s great at persuasive writing, and your support agent on a model that’s best at careful, step-by-step troubleshooting.
Check your workspace plan for agent limits. Most businesses do well with 1-3 agents. Having more agents than you need adds complexity without benefit.
Yes. Deleting an agent removes its personality, instructions, memory, and agent-specific knowledge. Workspace-level data (contacts, deals, shared knowledge) is not affected.