For the developer, the Kommo system is a relational database. The system has basic and auxiliary entities, essentially data tables, which can be linked to each other. Access to them is available through the API.
To access the system data, both through interfaces and through the API, authorization under the user’s account is required. All work through the API also takes place based on the access rights of the authorized user in the account. All methods can be used only after authorization.
Through the API you can get the necessary information about the account: name, paid period, users of the account and their rights, directories of additional fields of contacts and leads, a directory of lead statuses, a directory of note types, a reference of task types and other account parameters.
One of the main essences of the system. It consists of a predefined set of fields and additional ones created by the account administrator.
Each contact may participate in one or more leads or may not be associated with any at all.
Each contact can be attached to one company.
The contact’s email and phone are used as unique identifiers in conjunction with other systems. For example, information about completed calls and email communications is received to contact by phone number and email.
Each contact can be assigned a responsible user to differentiate access rights between account employees.
More details about contacts.
One of the main essences of the system. It consists of a predefined set of fields and additional fields created by the account administrator in the interface or via API.
Each lead can be attached to one or more contacts or not attached to any.
Each lead can only have one attached company.
Each lead can be assigned a responsible user to differentiate access rights between account employees.
The lead has a status, which indicates the position of the lead in the pipeline (business process). Each lead must be assigned a status.
The list of statuses can be modified within the account, except for the three system statuses: first one: incoming Leads, and final two: Closed – Won, Closed – Lost . For system statuses, only names can be changed.
Incoming Lead has additional functionality and different sources, and it differs from the lead in that it may not have a responsible person and contains metadata (type of unparsed and other properties).
More details about leads.
About Incoming Lead.
About pipeline and statuses.
Similar to the entity of “contact”. It consists of a predefined set of fields and additional accounts created by the administrator of the account. Each company may participate in one or more lead or may not be associated with any at all.
E-mail and phone are used as identifiers in conjunction with other systems
Each company can be assigned a responsibility to differentiate access rights between employees of the account.
More details about companies.
The essence of the “lead” is similar. It consists of a predefined set of fields and additional accounts created by the administrator of the account. Each customer can be attached to one or more contacts or not attached to any.
Each customer can be assigned a responsibility to differentiate access rights between employees of the account.
The customer has a period that indicates the position of the customer in the life cycle (business process). The list of periods can be changed within the account, except for the first and three final system periods.
More details about customers.
A transaction is an entity that describes the basic characteristics of purchase (date and amount). Is an addition for the “customer”.
The task must have a responsible user and a datetime (number and time). Also, a task can be associated with a lead or contact, but not necessarily, it may not be associated with any object. Tasks are considered to be the primary entity of the system.
You can set the result for a closed task using the notes method.
Events represent the ability to add additional structured or non-structured information to a contact or lead. Events can be system calls (calls, SMS messages, etc.) created by the user (notes, files). The events in the cards are displayed alongside the tasks because they do not have a responsible user and are not attached to a date.
Often events are used by widgets to add additional information to a lead or contact when it is not very convenient to use custom fields. Events are very convenient to use as a log because they are always displayed in chronological order in the tape, and if your information is tied to a date (chronology), then it is desirable to use events.
Read more about notes.
Custom fields allow to insert additional information into entities and can be created and deleted one at a time. Users will not be able to change these values from the interface but will be able to filter by them and view them.
Creating and deleting a field is also possible from the interface.
Read more about working with custom fields.
Calls represent the ability to add information to a contact or company. The events in the cards are displayed alongside the tasks because do not have a responsible user and are not attached to the date. If the call event has a link to the call record file, a player will be added to a note to play this record.
A new entity of the system. In the Incoming state, all calls from the integrations: mail, telephony, forms for the site, which have not yet been processed by the user a (lead or contact has been created) fall into the state. The user can accept the incoming leads, in this case, a lead will be created, as well as the contact and the company if the relevant information is in the application or reject it.
Read more about incoming leads.
Each account in Kommo has the ability to notify an external web server about various events. These “WebHooks” can be used to update information about leads in your store, send SMS notifications or automate leads. Each WebHook can be configured for a specific operation and events. The account administrator can configure the hooks in the Settings->The Integrations page.
Stages of sales
The stages of sales are the sequence of steps that a potential customer (lead) passes through the sales pipeline before buying. In Kommo, you can create multiple sales pipelines in one account and set your own milestones to track the progress of the lead in each pipeline. In Kommo, you can configure up to 10 pipelines in your account. Each pipeline can contain up to 100 stages (including successful and unsuccessful statuses). Only the administrator of the account can perform a setup of pipelines and stages of sales by going to Leads>Setup.
The digital pipeline allows you to configure the execution of various actions and automatically change the stages of leads when certain events occur.
The administrator of the account can set up the digital pipeline by clickingLeads -> Setup button.
Periodicity of customer purchases is a sequence of steps that a potential customer is taking on the customer pipeline before buying. In Kommo, you can create your own stages to track the progress of the customer.
The customer pipeline can contain 10 stages “before purchase” (including “recently bought”, “bought today” and “not bought”). The administrator of the account can configure the periods on the Digital Pipeline page.
A widget is an archive containing a set of files that will be connected to Kommo to all accounts that have enabled the widget. The widget allows you to get additional functionality if necessary:
- Display additional data in the Kommo interfaces. Special areas are provided where you can display widgets. For example, display the statistics of hits on the contact from the internal system;
- Interact with the user and the data entered by him. You can connect JS-scripts practically in any interface of the system. For example, you can show a pop-up card when you receive a call;
- In order for the administrator of the Kommo account to enter the individual settings for your service. For example, the key in your API.
You can set up widgets for an administrator account on the Settings -> Integrations.
More information about widgets.
Lists are a new section containing already familiar lists of contacts and companies, but also allows you to create lists and directories that you can use in leads and customers.
More details about lists