Two-way CRM sync explained: field maps, matching, the echo loop, duplicates, and what should never sync back
The parts of a CRM integration (field maps, match rules, triggers, delivery), the four ways a sync goes wrong, how to avoid each, what is worth syncing, and which CRMs Linkubit connects to.
Inboxes and CRMs8 of 11 in this topic
A two-way CRM sync keeps the same customer up to date in two systems: changes in your WhatsApp tool appear in your CRM, and edits in the CRM come back. It needs a field map (which field goes where, in which direction), a rule for matching records, and a way to stop changes bouncing back and forth. Done badly, it duplicates records, overwrites good data and loops.
On this page
The parts of a sync
| Part | What it decides |
|---|---|
| Object map | Which kind of record goes where: contacts to this board, deals to that one |
| Field map | Which field becomes which column, and the direction for each: push, pull or both |
| Match rule | Which existing record is the same customer: a phone, an email, an id |
| Triggers | When a sync happens: a lead created, qualified, assigned; a deal opened, won, lost |
| Conflict rule | What happens when both sides changed the same field |
| Delivery | Queued with retries, or called in the moment and lost if the CRM is slow |
The four ways a sync goes wrong
- The echo loop. System A pushes a value; B reports the change; A's rule fires on the change and pushes again; B reports again. Each step works. The bill and the API quota do not. A sync has to remember what it last sent and ignore its own change coming back.
- Duplicates. A match rule on something that varies, such as a name or a phone number typed two ways, creates a second record for the same person. Match on a normalised identifier, and link the two records once matched.
- Overwrites. A pull that writes a CRM edit over a phone number or email silently changes who a customer is. Identity fields should never be pulled; only your own descriptive fields.
- Silent failures. A CRM that refuses a column, a token that expired, a quota hit: if the failure lands in a log nobody reads, the board drifts out of date and everyone assumes it is right.
How Linkubit keeps a sync clean
- CRM steps are ordinary automations: send, update a field, add a note, create a record. "When this happens, do that in the CRM" sits beside your other rules, where you can read and change it.
- A slow CRM never slows a conversation. Updates go out within moments; if the CRM refuses one, you see the reason and can retry, and a disconnected CRM asks to be reconnected.
- No loops and no duplicates. Each customer is linked to one CRM record, only fields that changed are sent, and Linkubit ignores its own change coming back.
- Only your own fields come back. A CRM edit can never change a customer's name, phone number or email, and the field map won't let you set one up that would.
- New records can wait for a person. Approval is on by default, so a spam enquiry never lands on a shared board by itself.
- Editing a CRM never creates people Linkubit will message. Customers come in from a CRM only through an import, with a note of how they agreed to hear from you.
What to sync, and what not to
| Sync | Leave alone |
|---|---|
| Lifecycle stage, qualification, score, owner | Every message: a summary and a link are enough |
| Deal value, stage, expected close date | A price typed into the CRM back into the catalogue |
| The answers to your qualifying questions | Identity fields, from the CRM back |
| Payment status, amount, paid date | Fields nobody on the team reads |
| A note at each milestone | A note on every message |
Revenue from the CRM, safely
Teams that close deals in their CRM want the win to count everywhere. In Linkubit, when the CRM status says Won, the deal closes here at its own value, so the revenue, the ad that brought the lead in, and the sale reported back to Meta and Google all update. A deal is only ever marked won by a rule you set or a person on your team, never by the AI.
Which CRMs
Linkubit connects to monday.com and Zoho CRM: monday.com with WhatsApp and Zoho CRM with WhatsApp walk through each. For other systems, webhooks on the Scale plan send every lead, deal and conversation event to any address, such as Zapier or your CRM's own inbox, and spreadsheet import and export move records in and out. The integrations page lists what's next.
What is two-way sync in a CRM?
Changes flow in both directions: a lead qualified in the conversation tool updates the CRM record, and a field your team edits in the CRM comes back. Each field has its own direction so neither side overwrites what the other owns.
Should a CRM sync be real-time?
Near real-time is enough and safer. Queued delivery with retries survives a slow or unavailable CRM; a sync that calls the CRM inside every click fails whenever the CRM does.
How do I stop a CRM sync from creating duplicates?
Match on a normalised identifier like a phone or email, link the two records once matched, and send only the fields that changed. Never match on a name.
Read next
More on Inboxes and CRMsLinkubit vs other toolsWhatsApp templatesCost calculatorPricing
Try it on your own number. Start free, no card, or see the pricing.