> For the complete documentation index, see [llms.txt](https://converso.gitbook.io/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://converso.gitbook.io/product-documentation/ai-agents/agent-store/choosing-your-agents.md).

# Choosing your agents

Converso gives you specialised agents rather than one generic bot. Each agent is built for a different stage of the customer relationship, works best in a different place, and performs best with a different knowledge base behind it. This page helps you decide which agent to deploy where - see each agent's own page for full capabilities.

### At a glance

|                       | [Sales Agent](https://converso.gitbook.io/product-documentation/ai-agents/agent-store/sales-agent) | [Customer Support Agent](https://converso.gitbook.io/product-documentation/ai-agents/agent-store/customer-support-agent) | [Helpdesk Agent](https://converso.gitbook.io/product-documentation/ai-agents/agent-store/helpdesk-agent) *(coming soon)* |
| --------------------- | -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| **Best deployed on**  | Marketing site, pricing and landing pages                                                          | Help centre, docs site, post-sale pages                                                                                  | Inside your product UI                                                                                                   |
| **Primary visitor**   | Prospects evaluating a purchase                                                                    | Existing users, plus visitors researching the product                                                                    | Logged-in customers with a problem                                                                                       |
| **Knowledge base**    | Sales-oriented: positioning, comparisons, case studies, pricing                                    | Factual: product documentation, feature facts, how-to guides                                                             | Troubleshooting: known issues, documented fixes, billing policy                                                          |
| **Conversation goal** | Qualify and convert - booked meetings and captured leads                                           | Answer and resolve - no sales motion                                                                                     | Resolve the issue or hand over a complete case                                                                           |
| **Hands over to**     | Your team, for custom pricing and complex requirements                                             | Your team - with buying intent flagged as a sales enquiry                                                                | Your team, with a full case summary                                                                                      |

### Choosing between them

**Support Agent vs Sales Agent** - Both answer product questions for evaluators, so the deciding factor is the conversation goal. On pages where you want conversion, deploy the Sales Agent. On pages where a sales motion would feel wrong - help centres, docs - deploy the Support Agent: it answers factually, and flags genuine buying intent to your team without running a sales conversation.

**Support Agent vs Helpdesk Agent** - Both help existing customers, so the deciding factor is depth and location. The Support Agent suits public help pages, where questions are mostly how-to and product understanding, with light issue triage. The Helpdesk Agent suits your product UI, where customers arrive with specific faults that need structured capture and a complete case handed to your team.

### Deploying more than one

You can deploy multiple agents across different workspaces, giving each agent its own knowledge base, team, and channels. A common pattern: the Sales Agent on your marketing site, the Customer Support Agent on your help centre - each grounded in the knowledge base that fits its job.