Agents: AI agents as the new workforce in sales
The A in REVAGO stands for Agents. What sets AI agents apart from chatbots and workflows, which tasks they can take on in sales – and why autonomy and human-in-the-loop are designed together.
The term “AI agent” is currently used for almost anything – from a simple chatbot to complex automation. For us, it has a clear meaning: An AI agent pursues a defined business goal and can select and carry out steps within an approved scope of action.
The A in REVAGO stands for these agents: effective sales needs AI agents that pursue their goals within authorised scopes. They are the core of Agentic Sales – AI agents in sales – and therefore the concrete way we help you secure and grow revenue. The scope extends beyond sales to your entire go-to-market.
Chatbot, workflow, agent – what is the difference?
A chatbot answers questions in a conversation. A workflow organizes a process made up of rules, tasks and handovers – and can certainly include decisions. An agent is given a goal and chooses, within defined limits, which steps to take to reach it.
The three are not mutually exclusive. In practice, an agentic process often combines fixed rules, language models, interfaces and human decisions. Not every step needs a language model; some tasks are handled more reliably by a clear rule.
To work effectively, an agent needs:
- a goal aligned with a business outcome,
- access to the data and tools the mandate provides for,
- the ability to assess interim results and adjust its approach,
- an approved scope of action that it cannot expand on its own.
What agents actually take on in sales
Agents are at their strongest where a lot of information has to be processed and customer relationships have to be followed through reliably. In the documented state of our system, this includes:
- Analyzing customer data and preparing briefings, based on the data connected for the mandate.
- Organizing cases and planning next steps – with status, delegation and follow-up dates.
- Reading a mailbox and classifying replies: categorizing messages and extracting information.
- Sending emails according to defined rules and drafting replies. Certain standard paths run automatically; in the documented case, individual replies within an ongoing conversation are only sent after human approval.
- Supporting follow-up through planned next steps and configured reminders.
- Opening the customer context for incoming calls, so the person on the phone immediately sees the contact and related cases. This is a context display, not a voice agent.
Which of these capabilities a mandate uses, and which integrations are set up for it, we clarify for each mandate. What matters is not how many tasks an agent takes on, but which ones contribute most to the goal – for example in Repeat Business or Customer Reactivation.
Goals instead of instruction lists
A well-designed agent is not steered by an endless list of instructions, but by a goal and criteria against which its contribution can be measured. The question then is not only “Did the agent do what it was told?” but “Did it contribute to what it is there for?” How that contribution is assessed economically is covered in the article on Value.
Autonomy and human-in-the-loop belong together
Autonomy and human-in-the-loop are not opposites you choose between once. Both are configurable parts of the same model. For each type of case, we define which action type fits:
- Prepare – the agent provides information or drafts.
- Recommend – the agent proposes a next step.
- Execute with approval – a person approves, then the agent acts.
- Act autonomously within defined limits.
Human-in-the-loop means deliberately designed points for decisions, reviews and intervention. Not every single action requires manual approval. Which action type fits depends, for example, on how large the impact is, whether a step can be reversed and how uncertain the situation is.
Governed by Design – and who is responsible for what
Agents act on behalf of your company. That is why responsibilities, permissions, limits, interventions and escalations are part of the design for us, not an afterthought. Approval paths and case states are recorded in a traceable way. Governed by Design is an architectural principle – not a certificate and not a blanket proof of legal compliance.
Responsibilities are clearly assigned:
- You, as leadership, set the goals, the mandate and the framework of responsibility – and with it, how far the scopes of action extend.
- REVAGO develops the agents, integrates them into your system landscape and runs them technically.
- People in operational roles make the agreed decisions and approvals. They can work on your side, at REVAGO or split between both.
We build your agents – and we do it in a way that ensures your organization always knows who decides what.
Your next step
If you want to see how agents work together in a specific situation, our use cases describe the four prioritized fields of application. How coaching, implementation and operations fit together is explained on our services page.
The next article covers the G in REVAGO: Go – the step from a clarified mandate to implementation.
