1. Access for programs, not only for people
AI integrationAI implementation. AI implementation is the path from an idea to a working solution: a company chooses a process, connects artificial intelligence to it, trains its people, and measures the result in money. with a CRM starts with access: the agent must be able to create a deal, update its status and record the message history without a person. For this the CRM needs an open interface for programs and a way to create a separate user for the agent. Bitrix24 and amoCRM, CRMs popular in Russia, have this; for custom-built systems we check during the review.
2. Deals and channels in one place
If the conversation with a customer lives in a messenger and the deal lives in the CRM, the agent has to link them itself. It helps when the CRM is already connected to messengers and telephony: the agent writes to the same place as the managers. If the channels are scattered, the first step of the pilot is to bring them together.
3. User rights
The agent has its own account with rights only for its process: create a deal, write to the record, read the status. It does not need to delete, change prices or see all deals. If the CRM cannot limit rights, that is a risk, and we discuss it before the start.
4. A pipeline with clear stages
The agent moves a deal to a stage by a rule: “new”, “qualified”, “passed to a manager”. If there are twenty stages and nobody remembers how they differ, we first simplify the pipeline and then launch the agent. This takes one conversation, not a week.
5. Where the data is stored
For Russian companies, customers’ personal data must be processed on servers in Russia under 152-FZ, Russia’s personal data law. Ask your CRM vendor where its servers are. We process our part in Russia; the CRM is your part of the responsibility.
6. What the manager sees
The pilot ends with a report on the metric: time to first reply, the share of requests in the CRM. It is convenient to take these figures from the CRM itself. If it has reports, good; if not, a management dashboard gathers them from the CRM, 1C accounting software and the bank into one window.
7. Cost and licenses
A separate user for the agent sometimes means one more license. Ask the vendor before the start, so that it does not become a surprise on the invoice.
If you have no CRM at all
A pilot is still possible: the agent answers in a messenger and saves requests to a spreadsheet that is later moved to a CRM. The effect will be half as large, because managers will still have to work by hand, but you will get the response time metric. Our advice: set up a CRM, even on a free plan, before the pilot. You will not need to change it later: the agent connects to the one you have.
What it looks like in a pilot
In the first three days we create an account for the agent in your CRM, give it rights only for its process and check on ten test requests that each deal appears with the right stage, contact and history. If any of the seven points above does not fit, you see it at once, not after a month. A fix usually takes a day: simplify the pipeline, turn on access for programs, create a user.
Then the agent works on real requests under the control of a responsible person, and at the end you get a report on the metric from the contract. The CRM stays yours, and you do not need to change it before or after.
Three questions people ask about CRM in a review
Do we need a more expensive CRM plan? Sometimes: if access for programs exists only on higher plans. We tell you this before the start, not after the invoice. Can a custom-built CRM be connected? Yes, if it has an interface for programs; we look at it during the review. What if we have two CRMs, one for sales and one for service? The agent can write to both by a rule, but in the pilot we take one, the one where the pilot’s process lives.