CRM / VK integration
Integration of amoCRM with VK
We connect VK to amoCRM so that lead forms, community messages and requests from advertising do not live separately from CRM. It is important not just to get a lead, but to save the source, assign a person in charge, record the communication history and control the processing speed for each channel within VK.
Lead forms
Community Posts
History of the dialogue
Processing control
What decides Returns requests from VK to a single CRM circuit and removes manual copying of leads from forms and chats.
What you need in advance Understanding exactly which sources from VK you want to connect: forms, messages, advertising, communities.
When it's especially important If VK is a noticeable source of traffic, and managers respond to it without an overall picture of the client and without quality control.
Without integration
What usually fails
Lead forms and community messages are sent to managers manually and lose some of the source data.
The history of communication lives in VK, and in CRM only the fact of communication is reflected without context.
The manager does not see the speed of response, the quality of the response and the actual conversion through the channel.
What we are setting up
Basic scenarios
Creating a deal or contact using the lead form and the first message.
Linking the request to the desired manager and setting a task for the first response.
Saving the channel, source and communication history inside CRM for analytics and control.
What does the business get?
VK as a managed sales channel
VK no longer remains a separate “island” where half the client context is lost.
The history of requests and the reaction of managers become part of CRM and management analytics.
You can see how VK works in conjunction with the website, telephony, instant messengers and other channels.
Related Pages
What to watch next on VK and chat channels
