We reply on weekdays and check the number against your own data
No first line, no ticket system, no intake bot: your request is read by the engineer who wrote the calculation. The links below open a ready-made message — the widget version and the fields we need are already in it.
Where to write
Whichever channel you choose, the request reaches the same people. A messenger is faster: a screenshot fits there.
The same number if you do not use Telegram. We reply in the same chat.
wa.me/995579151731
What to attach to a request
We store no names, phone numbers or text: we cannot find your deal by a client’s surname and cannot see your screen. The message opens with the subject, the widget version and empty fields for this list — you fill in the values and attach a screenshot.
What the message already contains
- Subject line with the widget version
- amoCRM subdomain
- Widget tab
- Period and filters
- What you expected and what you saw
Your amoCRM subdomain
The first part of the address before .amocrm.ru. It is how we find the account: we cannot search by company name because we do not store names.
Widget tab
Funnel, Managers, Data quality, Lead path — where exactly the problem shows.
Period and filters
Dates, pipeline, manager, field breakdown. Without them the number cannot be reproduced and the review turns into a day of back-and-forth.
What you expected to see
And what you saw instead. A mismatch with a specific number is resolved in one pass; “everything is calculated wrong” cannot be resolved at all.
A screenshot, if you have one
The whole widget screen, including the filter bar. No need to mask personal data — our screens do not show any.
When we reply
We do not promise a response time in hours. We reply during business hours on weekdays, usually the same business day. If the question needs a review of your account data, you first get a confirmation that the request is taken, then the review.
Priority support is included in the Developer plan. Other plans share one queue: we do not run a separate line that stays silent faster.
The widget opened empty
Three causes. You close the first two without us; the third takes one message.
Old code is cached
amoCRM caches widget files. Reload the page bypassing the cache: Cmd+Shift+R on macOS, Ctrl+F5 on Windows.
Result: the screen is rebuilt from the current widget files
The first load is still running
Right after connection there is no history in the database yet. On an account with 7 years of history the full load took 34 minutes — a measurement, not an estimate. After that the data refreshes every 5 minutes.
anonymised property developer account · 69,567 deals, 240,031 transitions · measured 25.08.2026 · docs/РЕШЕНИЯ.md, пункты 37 и 40
Result: the whole history is loaded, and from then on reports run on fresh data
Access has been revoked
An administrator may have revoked access under “Granted access”, or it was lost when the integration secret was rotated. The fix is to reconnect via OAuth — the widget will ask for it.
Result: access is restored and the accumulated history is not lost
How to connect and reconnect the widget — with the list of permissions we request and what the administrator needs to do.
Key and payment
The licence key is tied to the amoCRM account, not to a user: it will not work in another account. There is no automatic card payment yet — we issue the key manually and invoice your company. What happens when the paid period ends and why history is not lost — on the pricing page.
Questions about invoices, closing documents and renewals — at hello@klastercrm.com.
Before you write
Some questions are already answered in writing, and the written answer is more detailed than a chat can be.
FAQ
What we see in your CRM, whether we can break anything, whether a manager can see other people’s deals.
How we count
If a number does not match your expectation, the answer is usually here: median instead of mean, a threshold on deal count, refusing to build a breakdown on an empty field.
Found an error in the numbers — write to us first thing
This is the most valuable request. Send the subdomain, tab, period and the number you believe is wrong: we rerun the calculation on your data and tell you whether it is an error or a difference in metric definition. If the error is ours, we say so and report what we fixed.
We have already published a review of an error in our own heuristic: it marked a stage that closes deals into revenue as a parking stage. How it happened and what we did.