Which AI agent to start with in a sales team

Start with a single agent on one narrow task that repeats every day and shows up as a number. In a sales team that is almost always qualifying inbound enquiries. Not an agent that «sells», and not ten roles at once: the team of agents comes later, once the first one has run long enough to leave data in the CRM showing what success actually looks like.

Why not all of them at once

Gartner expects more than 40 percent of agentic AI projects to be cancelled before the end of 2027, and gives three reasons: rising costs, unclear business value and weak risk controls. All three show up exactly where a company launches something broad without one measurable task. Fifteen roles at once means fifteen places where something can go wrong and no single place where you can see it going right.

A narrow start removes that risk. One agent, one metric, one month of watching it. If the metric moves, widen the project. If it does not, look at the process instead of buying more roles.

What the first agent should look like

A good first task is recognisable by four signs. The work repeats dozens of times a week, otherwise the effect drowns in noise. The result can be counted without argument: first response time, share of enquiries handled, number of deals brought back into play. A mistake is cheap and visible immediately, which means a manager catches it rather than a client a month later. And the data the agent needs already sits in the CRM instead of in someone's head.

Qualifying inbound enquiries

This task fits all four. Enquiries arrive constantly, from WhatsApp, the website and ads, and some of them burn a manager's time before the first real conversation. The agent collects what is missing, asks the clarifying questions, filters out what is irrelevant, fills in the record and hands the manager a contact that already makes sense. Counting is simple: how long it takes to get from an enquiry to a first substantive reply, and what share of enquiries reach a conversation. Both numbers exist in the CRM before launch, so there is something to compare against.

If inbound is already fine

Then the first agent is the one watching deals that stopped moving. It notices that a deal has had no call, no email and no task for a week, and hands it back to the manager with a short reminder of how the last contact ended. The work repeats just as reliably, and the metric is just as clear: how many deals came back into play and how many moved on to the next stage. Mistakes stay cheap here too, because the worst case is one reminder too many.

Where not to start

Do not start with an agent that runs the negotiation and closes the deal: that is where a mistake costs the most and where the agent's work is hardest to separate from the manager's. Avoid any role without a metric of its own. And treat the word «agent» carefully: Gartner notes that products are frequently rebranded as agents without real agentic capability, and puts the number of genuine solutions at roughly 130 among thousands of vendors. What to check is not the label but whether the system has memory, access to data and the right to take an action rather than only reply with text.