AI agents in sales: sensible fields of use instead of AI hype

“AI agents will soon sell by themselves” is a headline that reads well and means little in the daily life of B2B companies with products that need explaining. What agents can do reliably today is less spectacular and considerably more valuable: they take over the preparatory work that costs sales teams time every day. This article describes where that works, where it does not, and which rules an agent needs for a team to actually use it.

What an AI agent is and what it is not

An AI agent is software that pursues a given goal, plans and carries out several steps for it: gathering information, querying systems, producing results, triggering actions. It works within defined rules and approvals.

Two distinctions help:

• From the chatbot: a chatbot waits for the next question. An agent works through an assignment (“prepare the conversation with company X on Thursday”) and delivers a result.
• From classic automation: rule-based automation needs structured input. An agent can handle unstructured sources such as web pages, emails, documents or conversation notes and derive intermediate steps itself.

What an agent in sales should not be: a system that communicates with customers on its own, makes commitments or negotiates terms. Not because the technology could not, but because responsibility and trust arise at those points, and a company cannot delegate them.

Field 1: account research

Researching target customers is perhaps the most obvious application and one of the most effective. The same questions come up before every outbound contact: what exactly does the company do? How big is it, how is it organised? Is there a reason for a conversation, such as growth, job postings, a system change or a regulatory requirement? Who are the relevant roles?

An agent can answer these questions systematically for a list of accounts: website, public registers, job postings, news, licensed data sources. The result lands in the CRM in a structured form, with a reason why the account fits or does not, and with the concrete trigger. The sales person starts with context instead of an empty line.

The limit: the agent assesses by criteria that humans defined. Whether an account ultimately gets priority remains a judgement that requires experience. More on preparatory work in outbound under B2B lead generation.

Field 2: conversation preparation

The same routine before every meeting: who is attending, what has happened so far, which points are open, what has changed at the company since the last contact? In practice that preparation happens five minutes before the meeting, if at all.

An agent assembles the briefing automatically: from CRM history, email threads, conversation notes and current research. It arrives an hour before the meeting as a compact summary, with the three points that matter in the conversation. That is not magic but the bringing together of information that already exists but is scattered.

Field 3: summaries and CRM enrichment

Maintaining the CRM after conversations is where many systems fail. The sales person had a good conversation, the next one is due, and the notes stay in the notebook. Three weeks later nobody remembers what was agreed.

An agent can produce a structured summary from conversation notes or, with consent, from transcripts, propose the relevant CRM fields (stage, next step, people involved, objections) and create tasks. The human checks and confirms with one click instead of typing for ten minutes. The result: a CRM that reflects the actual status, without maintenance becoming a burden.

That includes enriching existing records: adding missing fields, detecting duplicates, marking outdated entries. That is work nobody enjoys and that nevertheless decides the quality of every report.

Field 4: knowledge in the conversation

Selling products that need explaining brings questions you do not know by heart: how does the product behave in a particular scenario, which references exist in an industry, what was the answer to a similar security question at the last customer? The knowledge exists in documents, offers, tickets and wikis but is not available at the moment of the question.

An agent with access to approved sources answers such questions with a source reference. It does not replace the specialists, but it reduces the number of internal questions and speeds up answers to the customer. The prerequisite is that the sources are maintained and that the agent marks the unknown as unknown instead of guessing. How such an assistant is built is described under AI assistants.

Field 5: offer support

Offers for products that need explaining consist of building blocks: scope of services, rollout plan, terms, technical answers, references. An agent can assemble a draft from discovery notes and templates, mark gaps (“integration scope unclear”) and request a review.

The benefit is not speed alone but consistency: wording that has proven itself gets reused, and the typical transfer errors from copying together older offers become rarer. They will not disappear; even a draft made from building blocks can contain an outdated detail. That is why approval, both in substance and commercially, stays with the human, as does the negotiation.

Where agents do not belong

Four areas in which we deliberately use no agents, or only with approval before each individual step:

1. External communication. Messages to customers are approved by humans. An agent may draft, not send.
2. Commitments and terms. Anything that binds the company is decided by humans.
3. Assessing people. An agent can gather signals; judging a contact is a human task.
4. Decisions on unclear data. Contradictory sources, missing details, unexpected answers: the agent stops and hands over instead of guessing.

Approval as a design principle

The most common objection to approvals: they make the agent slow. Experience shows the opposite. An agent without approvals does not get used because nobody trusts it. An agent with sensible approvals gets used because the team knows nothing goes out without a check.

Four patterns have proven themselves:

• Proposal → approval → execution: the standard path for anything with an external effect.
• Thresholds: routine within defined limits runs automatically; deviations go to a person.
• Four-eyes principle: for contracts, payments and external communication a human always checks.
• Logging: every step is traceable. Inputs, sources, result, approval.

Where approvals get in the way of daily work, the problem is usually not the approval but the way the process was cut: the agent takes on too much at once instead of one clearly bounded step. Smaller assignments, clearer boundaries, less friction.

How to start

The first agent should be small and everyday: a process that occurs daily, whose result is easy to check and whose benefit can be measured. Conversation summaries into the CRM are a typical entry point, as is account research for outbound lists.

In our view six components belong to every agent:

1. Assignment and goal: clearly stated, with a defined result.
2. Tools: access to exactly the systems and sources needed.
3. Rules and boundaries: what may be read, written, triggered?
4. Approval points: before actions with an external effect.
5. Log: every decision traceable.
6. Measurement: time saved, quality, share of corrections.

The rest is operation: check results, sharpen rules, choose the next process. What that looks like technically is described under AI agents; the basis for it, a properly maintained CRM, in the article CRM automation: from enquiry to follow-up.

Working tool: briefing and quality check

An agent is only as good as its assignment. This briefing describes a bounded research assignment, short enough to be checked.

Example with fictitious data:

• Assignment: summarise for one target company what is relevant for a first conversation.
• Permitted sources: company website, legal notice, public job postings, our CRM.
• Output: five sentences, each with a source; separately a list of open points.
• Forbidden: estimates of revenue or budget, statements without a source, any form of contact.
• Approval: the draft goes to the responsible person, not to the customer.

Check before use. Define ten cases whose correct answer you already know and let the agent run on them. What is judged is not whether the answer sounds good, but:

• Does every statement match the source given?
• Is what is missing named as missing instead of filled in?
• Does the agent stay within the permitted sources?
• Is the result sufficiently stable when the input is the same?

That check does not replace ongoing supervision. But it shows before going live whether the assignment is worded tightly enough.

Conclusion

AI agents in sales are not a replacement for sales people but a replacement for their preparatory work. Research, preparation, summaries, enrichment, knowledge questions and offer drafts can be taken over reliably today, if rules, boundaries and approvals are part of the design. Whoever starts with that gains not speed in the first place but consistency: a CRM that is right, conversations that are prepared, and a team that has time for what only people can do.