Help for owners
I want my WhatsApp chats to appear in my CRM
Short answer
To connect WhatsApp to a CRM, incoming messages and delivery statuses reach your system as webhooks, and you match each phone number to one contact. The hard parts are duplicate contacts, consent records, the 24-hour window and who owns each chat. Settle those rules before connecting anything.
Does this sound like your situation?
- My team answers on personal phones and the CRM has no record.
- Customers appear twice in my CRM.
- I cannot tell who has agreed to get messages.
- Two people answered the same customer.
- I want leads from WhatsApp to land in my pipeline.
Why does this happen?
Phone numbers are not clean identifiers
The same number can be written with or without a country code, so the same person becomes two contacts. Numbers need one fixed format before matching.
Events arrive as webhooks
Message statuses and incoming messages reach your system as webhook calls. If your CRM cannot receive or retry them safely, messages are lost or duplicated.
Confirmed by developers.facebook.com
Consent must be stored, not assumed
Meta requires opt-in and that opt-out and block requests are honoured. The CRM needs a field that records who agreed, when and how.
Confirmed by developers.facebook.com
The window limits what can be sent
A reply from a CRM user is a free-form message only while the customer's 24-hour window is open; afterwards a template is needed.
Confirmed by developers.facebook.com
What can I do about it today?
- Decide who owns a chatOne named person or team per customer, so no double replies.
- Pick the fields you needPhone number, consent, source and last message date are usually enough.
- Export your contactsLook for duplicates and numbers in several formats before connecting.
- Write down the opt-in methodWhere a customer's permission is recorded.
- Keep it read-only firstStart by copying chats into the CRM before letting anyone send from it.
When should I bring someone in?
- Your CRM is a vendor tool whose limits you cannot read.
- Existing contacts are already messy.
- You need two-way sync rather than copying.
How do I handle it?
- Define the matching ruleOne number format and one rule for matching a message to a contact, written before building.
- Receive events safelyIncoming events are verified, saved first and processed after, so retries do not duplicate.
- Store consentOpt-in and opt-out status is a field that blocks sending when it is not set.
- Respect the windowThe sending screen knows when a template is required.
- Check with real chatsA set of real conversations is replayed to confirm contacts, ownership and statuses are right.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I import my old chats?
I cannot promise that earlier chats can be imported, so plan on the CRM holding chats from the date the connection starts.
Will my CRM vendor support this?
That depends on the vendor, so I read its own documentation first and make no assumption.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.