A two-way CRM and SMS contact sync breaks in four predictable ways: duplicate contacts, two systems fighting over the same field, update loops, and an opt-out that one side never hears about. Fix those four on paper before you write the integration and most of the pain goes away.
This post is a design guide for the team building or buying that sync. It's about contact data, not message content, and it ends with what Ready's CRM connections can and can't do today.
Pick one identity key
Matching on name or email is how duplicates get created. People share emails, change names and use two addresses. For texting, the natural key is the phone number in E.164 format (+12125550199). Normalize every number to E.164 on the way in, from both sides, before you compare anything. The E.164 formatting post covers the messy inputs.
Decide up front what happens when:
- Two CRM records share one phone number (a household, a front desk line). Either merge them or mark the number as shared, but pick one.
- One CRM record has two numbers. Sync the mobile one for texting and store the other as a plain field.
- A number is reassigned to a new person. Your sync can't know this, so don't treat an old match as permanent proof.
Assign field ownership
For every synced field, name exactly one system as the owner, and make the other read-only for that field.
| Field | Typical owner | Why |
|---|---|---|
| Name, company, deal stage | CRM | Sales edits these |
| Phone number | CRM | One source of truth for identity |
| Last text date, reply status | Texting platform | Only it sees messages |
| Opt-out status | Whichever heard it first, always wins | See below |
| Tags for campaigns | Texting platform, or pick one | Avoid two editors |
"Last write wins" feels simple and quietly corrupts data when two edits land close together. Ownership is boring and it works.
Make opt-out the one field that always wins
Opt-out is the exception to every ownership rule. If a contact texts STOP, the texting side knows first, and that status has to reach the CRM and every other tool that can send. If the CRM marks someone as do-not-text, the texting side has to stop too. In both directions, opted out beats everything, and nothing should ever flip it back automatically because a record was re-imported.
On Ready, a STOP always blocks that number in the sub-account that received it, and GET /v1/opt-outs/:phone tells you the status. Check it before sending from another tool. The opt-out sync post goes through the cross-channel cases.
Stop update loops
A loop looks like this: the CRM updates a contact, the sync updates the texting side, that fires a change event, which updates the CRM again. Guards that work:
- Skip a write when the incoming value equals the stored value.
- Tag each write with its source, and ignore change events you caused.
- Debounce bursts, so ten field edits become one sync.
- Put a hard cap on writes per record per minute, and alert when it trips.
What Ready's CRM connections do
Ready's App Library connects to Close, HubSpot, Pipedrive, Salesforce, Zoho CRM. A connection can create or update a contact, add a note to the contact's timeline, move a deal to a stage, and start a Ready flow when a new contact appears in the CRM. That covers the common "new lead, text them" and "deal moved, text them" automations with no code.
What it doesn't do yet: Ready doesn't log every text to the CRM timeline on its own. That's still to build, so if you need a full message history in the CRM, plan to write it yourself through the API, or use a connection's note step for specific events. The native GoHighLevel integration is two-way for inbound and outbound messages, and texting from Close is also supported. For the wider picture, see CRM SMS integrations and the GoHighLevel duplicate contact post.
A short pre-launch checklist
- Every number normalized to E.164 on both sides.
- A written rule for shared and reassigned numbers.
- One owner named per field.
- Opt-out flows both ways, tested with a real STOP.
- Loop guards in place, with an alert.
- A reconciliation job that compares counts weekly.
Wrapping up
Sync is mostly a data-governance problem with a thin layer of code on top. Start with the identity key and the opt-out rule, and the rest follows. You can try the App Library connections on a free signup, and the messages docs cover the API side.
Frequently asked questions
What should I use as the unique key for a contact sync?
The phone number in E.164 format. Names and emails change or repeat, and a normalized number is the one thing both systems share.
Which system should own opt-out status?
Neither exclusively. Whichever system learns of an opt-out first should push it to the other, and opted out should beat every other value.
Does Ready log every text to my CRM timeline?
Not on its own yet. A connection can add a note to a contact's timeline, but automatic logging of every text is still to build.
How do I avoid sync loops?
Ignore changes your own sync caused, skip writes where nothing changed, and cap writes per record.