How to implement amoCRM with messaging apps and Avito
You connect each channel through an integrator or an API, set up a pipeline for the source, merge repeat enquiries into one record and teach the team to work from one shared base. With more than three sources and 50-plus enquiries a day, the setup takes about a week.
Why you need a CRM when enquiries come from different places
When a client writes on WhatsApp, then calls from the site and two days later asks a question in an Instagram DM, the salesperson sees three different people. Without a CRM the chats sit in the messaging apps, the calls in the telephony and the Avito enquiries in the inbox. The history is lost, the client repeats themselves and the deal slips away.
A CRM gathers every touch into one record. The salesperson opens the deal and sees that this person already asked about price on Telegram, received a proposal by email and is now checking timings on WhatsApp. No need to ask again or dig through chats. The whole history is right there.
The second gain is control. An enquiry that arrives on Instagram in the evening will not be lost until morning. The CRM creates a task, assigns someone and sends a reminder. The manager sees how many enquiries were handled, how many are hanging and where nobody replied.
The third is analytics. You understand which channel brings more deals and which only eats time. You count conversion from enquiry to payment for each source. You decide where to invest and what to switch off.
How to connect messaging apps to amoCRM
Telegram, WhatsApp and other messaging apps connect through integrators — services that pass messages from the app into the CRM and back. You register with the integrator, link the number or account and point it at the amoCRM pipeline where the enquiries should land.
Once connected, every new message creates a deal or adds a comment to an existing one. The salesperson replies straight from the CRM and the client receives the answer in the app. The chat history is kept in the deal record. If the client writes again a month later, the CRM finds the old record and continues the conversation there.
Integrators are paid, and the rate depends on the number of conversations and connected channels. We will not quote prices: every service sets its own and they change — look them up on the integrator's site. What matters more is that the integrator is not part of the amoCRM price. It is a separate subscription, and it is easy to miss when working out the budget.
How to connect Instagram to amoCRM
Instagram connects through the same integrators as the messaging apps. You link your Instagram business account to the integrator and it passes direct messages and comments into the CRM. Every new enquiry creates a deal, the salesperson replies from amoCRM and the client sees the answer in their direct messages.
One important point: Instagram requires the account to be a business profile linked to a Facebook page. Without that the API does not work. If you have an ordinary account, first switch it to business mode, create a Facebook page, link them, and only then connect the integrator.
Comments under posts can also be sent to the CRM, but that is a separate setting. It is usually switched on when enquiries are often left in the comments. If the comments are mostly discussion while enquiries go to direct messages, comments are left out so as not to clog the pipeline.
How to connect Avito to amoCRM
Avito connects through an API or through an integrator. The API needs a developer: you obtain a token from Avito and write a script that fetches the messages and creates deals. An integrator does the same for you, for money.
When a client writes in an advert's chat on Avito, the message arrives in the CRM as a new deal. The record shows which advert they responded to, what they wrote and their phone number if it is in their profile. The salesperson replies from the CRM and the client receives the message in the Avito chat.
Avito does not hand over the client's contact details straight away. The phone number and name appear only if the person put them in their profile or sent them themselves. So the salesperson's first job is to ask for a contact outside the platform. Without that the conversation is tied to Avito, and if the client stops going there the link breaks.
How to connect the website to amoCRM
The site connects through a form or a chat widget. A form sends the data into the CRM via a webhook or an API. The client fills in the fields, presses the button and an enquiry is created in amoCRM. The pipeline, the owner and the deal fields are configured in advance.
If the site has several forms — on the home page, on a service page, in the footer — each can be configured separately. One form creates a deal in the “Website enquiries” pipeline, another in “Consultation requests”. That way you know at once where the client came from and what interests them.
A chat widget works differently. The client opens the window, writes a question and the salesperson answers in real time. The conversation is saved in the CRM. Widgets come built into amoCRM and from third parties. The built-in one is simple but limited; third-party ones offer more settings: auto-replies, an offline form, links to messaging apps.
How to set the pipelines up by source
A pipeline is the path of a deal from enquiry to payment. Each channel deserves its own pipeline, or at least its own entry stage. An enquiry from the site lands on “New website enquiry”, one from Instagram on “New from Instagram”. That way you see the source at once and know how to work with the client.
The stages are set to fit the process. If Avito clients usually ask about availability and price and then buy straight away, the pipeline is short: new enquiry, clarification, payment. If website clients request a proposal, clear it with their management and pay by contract, there are more stages: enquiry, proposal sent, approval, contract, payment.
Automation helps you not lose the client. When a deal moves to “Proposal sent”, the CRM automatically creates the task “Call in a day if no reply”. Nobody has to remember; the system reminds them. If a deal sits on one stage for more than three days, the manager gets a notification.
How to merge repeat enquiries into one record
A client writes first on WhatsApp, then on Telegram, then phones. Without configuration the CRM creates three separate deals. Nobody realises it is one person, the client repeats themselves and time is wasted.
The answer is deduplication by phone or email. When a new enquiry arrives, the CRM checks whether a contact with that number or address already exists. If it does, no new deal is created and the message is added to the existing one. If not, a new record appears.
Deduplication is set up through the digital pipeline or through third-party widgets. In standard amoCRM it works only partly: the system merges contacts but does not always link the deals. If you need it to be exact, additional tools are connected or automation is written against the API.
Important: deduplication works only if the client has left a phone number or an email. If they write anonymously in different channels, there is no way to merge them. So the salesperson's first job is to ask for a contact.
How to train the team to work in the CRM
The CRM is in, the channels are connected, and people open the system without knowing what to do. Without training they carry on as before: answering in the messaging apps, not writing anything into the record, losing enquiries.
Training starts with the basics: how to create a deal, add a contact, write a comment, move it to the next stage. You show the whole path from enquiry to close on one deal. People repeat it on their own deals under your eye. For the first week you check every record, correct the mistakes and explain why.
The second step is a written procedure. You set down what to do with each kind of enquiry. A website enquiry — call within the hour. The client does not answer — write in a messaging app. No answer for two days — move to “Cold”. The procedure is short, a page at most, or nobody will read it.
The third step is control. Every week you look at how many enquiries were handled, how many are hanging without an answer and where deals get stuck. You go through the problem cases with the team and praise good work. The first month control is daily, after that weekly.
How a sales robot helps when there are many channels
When enquiries come from Telegram, WhatsApp, Instagram, Avito and the site, people cannot answer quickly enough. The client writes in the evening and gets a reply in the morning, by which time the interest has gone. In a live GetGate project about 27% of enquiries arrive in the evening and at weekends — they used to wait until morning.
A sales robot answers at once. It connects to every channel through amoCRM, recognises the question, answers from the knowledge base, asks clarifying questions and books the client. If the request is complex, it hands over. Everything is recorded in the deal, and nothing is lost.
The robot works round the clock. A client wrote at two in the morning and got an answer straight away. Someone checked a price on a Sunday and the robot answered and offered to book them in. By Monday morning the salesperson sees a warm client who already has the information and is ready to discuss specifics. In the same GetGate project this freed up roughly an hour of working time a day.
The robot handles voice messages and photos. A client sent a voice description of the task — the robot transcribed it and asked clarifying questions. A client sent a photo of a product — the robot identified it and quoted the price. Our check on real correspondence showed that in a blind comparison the robot's answer was no worse than a person's in 80% of cases.
What you need to set up amoCRM with several channels
First list the channels and estimate the volume of enquiries. With two or three sources and a small flow you will manage yourself in a couple of days. With many channels, enquiries arriving by the dozen and several people on the team, expect a week for the setup and another for training.
Connect an integrator for each channel. Make sure test messages arrive in the CRM, that the team can see them and reply. Check that repeat enquiries merge into one record. If they do not, set up deduplication.
Set up the pipelines. Give each channel its own entry stage or its own pipeline. Add automation: creating tasks, reminders, notifications to the manager. Run a few deals from start to finish and make sure everything works.
Train the team. Show them how to answer clients, move deals along and record the outcome. Write a short procedure. For the first week check every deal. If people do not understand what to do, simplify the process.
If you need help connecting the channels, setting up the pipelines, automating tasks and training the team, we do CRM implementation for your sales process.
Frequently asked questions.
What do we connect first if there are several channels at once?
The one most enquiries come from, not the one that is easiest to connect. Otherwise the first channel you set up is the quietest, and nobody sees any noticeable improvement.
If you do not know how enquiries are spread across channels, that is the first task: spend a week recording where people write from. The data usually differs from what the manager expects.
An official connection or one through an intermediary service?
The official route is predictable and slower to launch: there are checks, message templates, sometimes verification of the company. The unofficial one starts in an evening and lasts until the number is first blocked.
The choice depends on what it costs to lose the channel together with its history. If money comes through it, the saving on an official connection pays for itself exactly once.
What do we do with the old correspondence when moving into a CRM?
Moving all of it is usually unnecessary and often technically impossible. A sensible minimum is to enter the active deals by hand and attach the key agreements to them.
The rest is left where it is, and the day of the move is declared the cut-off. Trying to drag the whole archive across is the commonest reason a move stretches over months and never finishes.
How do we avoid losing a client who writes from two channels at once?
Merge enquiries by contact rather than by channel. If the same person is entered twice in the CRM, two people end up working with them, and they notice.
Matching by phone number is the most reliable, where there is one. Where there is no number, a rule helps: before a new deal is created the system shows similar ones, and the salesperson decides whether this is a new client or an old one.
How long does the team need to get used to it?
Technically a week; in practice, until the first week when nobody opens the old windows. Going back to the familiar tools is the real sign that the move is not finished.
What helps is not training but switching off the old channels, and the CRM genuinely being more convenient: if replying to a client from there is harder than from a phone, people will reply from the phone.
See how it works.
Write a couple of lines about your business to our agent — it will reply and book you a free review. That is the demonstration.
Let's audit your business
Leave a request and on a free consultation we'll find where customers are being lost, suggest which service to start with and price it around your goal.