The most expensive lead is the one nobody saw
Lead cost is calculated on the advertising side: cost per click, form completion rate, cost per lead. That calculation has an invisible line item — the lead that never reached the system.
The usual sequence: the website form is submitted, the form sends an email, the email lands in a shared inbox. That inbox gets forty messages a day; twenty are invoices, ten are suppliers, five are spam. The enquiry is somewhere in the middle. If it arrived on Saturday it is read on Monday, and by Monday the patient is talking to someone else.
What makes this loss painful is that it never shows up in a report. The ad platform says twelve forms were submitted, the CRM holds nine records, and nobody goes looking for the other three. Unmeasured, it is never discussed.
Three routes in, one destination
There are three practical ways to move a lead from its source into the CRM. They do the same job; they differ in who builds them and how much flexibility you need.
1. The API directly
With a developer on hand this is the most flexible route. The moment the form is submitted, its backend posts to the CRM's lead endpoint and the record exists within seconds. In MetoCRM the fields are: name (required), email or phone (at least one required), free-text notes, language code, advertising channel code, ad code, patient status code and sales group.
Channel, status and language are sent as codes, and the valid codes are read from the API's own reference endpoints. Whoever builds the integration never has to log in and hunt for an ID — a small detail that decides whether the integration still works six months later.
2. Zapier
With no developer, the Zapier branch does the same job with no code. Typeform, Google Sheets, Calendly, your own CMS — anything Zapier connects to can land a record in the CRM. It has its own key and endpoint, and records are marked with their source, so "came in over the API" and "came in through Zapier" stay separable in reporting.
3. The built-in web form
The third route is to build no integration at all: use the CRM's own web form module and embed it. The record is already inside. For small teams this is the fastest answer; the limit is that you control the form's appearance only as far as the CRM allows.
What happens once the record is in
The value is not that the lead reached the CRM — it is that it joins the flow the moment it arrives. A record posted over the API does not wait in a separate queue:
- Lead distribution runs and the record lands with a consultant. No orphan records.
- Any automations you defined fire — a welcome message, a reminder, a status change.
- The record is written with the channel and ad it came from, which is what the channel report feeds on.
That last point is the one teams skip, and all measurement depends on it. Without a channel and ad code, every lead falls into one "website" pile. As the pile grows, the question of which campaign produced patients becomes unanswerable, and budget starts moving on opinion. Your cost per acquired patient rests on the same field.
The other direction: webhooks out of the CRM
Integration is usually imagined one way — outside in. Yet the bigger time sink often runs the other way: something happens in the CRM and a person tells another system about it by hand.
In MetoCRM that is an outbound webhook configured as an automation action: when the trigger fires, a GET or POST request goes to the address you provide. The ones teams build most:
- Tell accounting when a sale closes. The status change triggers your finance system, so nobody reconciles two lists at month end.
- Update your own dashboard. A specific tag drops a record into your internal reporting screen.
- Notify a partner system. An operational step completes and the partner hospital or hotel side is informed.
- Close the advertising loop. Report the closed sale back to the ad platform — when conversion data flows back, the algorithm learns who to target. That deserves an article of its own.
Four traps people fall into
- Duplicate records. The same patient writes from the web form and from WhatsApp, two records appear, and two consultants call the same person. Test how deduplication on phone and email behaves before you go live.
- Empty channel data. The most common failure. The form works, records arrive, nobody notices — until three months later someone asks which campaign worked. On day one, send a test lead and confirm with your own eyes that the channel field arrived populated.
- Failing silently. If the API call fails and the form still tells the visitor "thank you, we'll be in touch", you have thrown a paid lead away quietly. Failed submissions must be logged somewhere a human actually looks.
- Keys tied to a person. A key created under the agency's own account becomes a problem the day you part ways. Give every integration its own key, write down who uses which, and revoke rather than negotiate — a revoked key stops working immediately.