Teams learn to share work with the agent, not to click buttons
An agent is not ordinary software. It messages clients, sets tasks and scores calls on its own, so every employee needs to know what the agent has already done, what it has left for them and when to step in.
That is why the first training topic is the process map, not the interface: which steps the agent now handles, which ones stay with people, and where the handovers are. Without that map, reps either duplicate the agent or stop watching what it does. We covered both mistakes in our news piece on five reasons AI agent projects stall.
Every role has its own area of responsibility
We split the team into four roles. In a small company one person can cover two of them, but keep the responsibilities clearly separate.
| Role | Usually | What they do with the agent | What we train |
|---|---|---|---|
| Agent owner | Head of department or process owner | Decides what the agent does alone and what needs approval | Reading agent reports, changing rules, settling edge cases |
| Reviewer | Sales manager, team lead, accountant | Checks the agent's decisions in the first weeks | Where to see the agent's actions, how to flag a mistake |
| User | Sales reps, buyers, recruiters | Works with what the agent has prepared | Reading suggestions, taking over a chat, not doubling up |
| CRM admin | In-house admin or partner | Looks after access and integrations | Permissions, fields, where the agent writes its output |
MakeBiz Technologies role split for agent launches, November 2026.
Name one person who signs off on the agent's rules. If anyone can change them, within a month the agent gives clients inconsistent answers and nobody remembers who changed what. Log every change in the playbook with a date and a reason.
Ground rules are written down before launch
Verbal agreements turn into "I thought the agent would handle that" within a week. A short playbook of one or two pages clears up most questions. It should cover:
- what the agent does without approval, such as answering a standard question about delivery times or sending a meeting reminder
- what needs a human to confirm: a discount, a price change, a promised deadline, saying no to a client
- how an employee takes a conversation over from the agent and hands it back
- where to report an agent mistake and how quickly someone responds
- what data the agent must not see or forward
Write the playbook in the team's language. In Dubai that is often English and Russian at the same time, so we prepare both versions, just as we do for Bitrix24 team training.
