Website and amoCRM integration
A form on the site hands the enquiry to amoCRM with its source, and the deal stage comes back to a status page. No enquiry ends up living only in an email.
- Buildfrom $2,150
- Timeline2–3 weeks
- Supportfrom $420/mo
Who this suits: Sites where forms send mail to a shared inbox, a manager copies the contact across by hand, and some enquiries arrive with no source.
What is in the first version
- server-side validation
- first-touch tags
- contact matching
- a status page
The figures above are the package this sits on: Integration and data pipeline. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
The enquiry is yours on submission
The enquiry lands in your database first and only then travels to amoCRM, so a CRM outage costs speed.
- 02
It lands on the right contact
Phone and email are normalised, a familiar person gets a new deal, and the first touch is never overwritten.
- 03
The stage comes back
The client opens their own enquiry by link and sees where it stands, in wording you choose.
What decides whether this works or annoys people
The enquiry never depends on amoCRM
A form posting straight to the API loses enquiries and exposes the token, so intake and forwarding are split by a queue.
Source lost on the first click
Tags read from the address bar at submission record a direct visit, so first-touch tags are stored on the device instead.
Internal stage names stay internal
Every internal stage has a public wording in a map, and a stage without one is simply not shown.
What to measure once it is live
- enquiries reaching amoCRM with none dropped
- share of enquiries with a source
- new duplicate contacts per week
- time from submission to the first touch
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- Site and formsTypeScriptReactNext.js
- Intake and queueNode.jsPostgreSQLRedisn8n
- Running it and alertsDockerGrafanaTelegram Bot API
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- the amoCRM plan and manager seats
- hosting for the intake service and status page
- an anti-spam service beyond the free tier
- email and SMS confirming the enquiry
Asked before the first call
- We already post enquiries straight into amoCRM. Why a layer in between?
- For two things a direct post cannot do: the enquiry is saved on your side first, and the token is not in your page source. Send one with a wrong token and see.
- The site is on a builder. Does this fit?
- It fits if the builder can send a submission out as a webhook, and nearly all can. If there is no webhook, replacing that one form beats moving the site.
- Will spam and bots create deals?
- The filter sits before the CRM: server-side validation, a rate limit per address and a honeypot field. Whatever gets past lands in a review list, not in the pipeline.