Transitions within a section

CRM

CRM / integrations

Integrations amoCRM

This is a hub for all connections around amoCRM: accounting systems, instant messengers, social networks, telephony, website, email and platforms like Avito. The point is not to “connect another service,” but to ensure that all requests, statuses and client history are collected in one system and not lost between channels.

1C and documents Chats and instant messengers Website and forms Telephony and email

Commercial pages

What has already been transferred to separate connections

Below are individual pages for key links. They are needed so that a person immediately gets into the desired scenario, and does not read a general page about everything.

Step layer

If a person is looking for how to connect it himself

These requests require not only a commercial offer, but also normal instructions. They collect information traffic and convert a person from “I’ll try it myself” to a clear request for integration.

Key Principle

First the route, then the connector

  • You need to decide in advance at what event a lead or deal is created.
  • Determine who is responsible, the response SLA and the next step after the first touch.
  • Immediately think about where the communication history is stored and how the manager controls it.

Technical layer

What do we check when connecting?

  • Are incoming messages and duplicates lost?
  • Are the source, channel, responsible and stage correctly identified?
  • Do tasks, notifications, auto-movement and analytics work across the channel?

When is an integrator needed?

It is not always profitable to collect yourself

  • If the connection affects several channels at once.
  • If you need to tie it to documents, 1C, analytics or a long funnel.
  • If the cost of an error is higher than the cost of normal adjustment and testing of the circuit.