The WhatsApp Business app, a connection through a provider, or the WhatsApp Business Platform directly - the practical difference is what you still have in a year.
Key takeaways
- The WhatsApp Business app keeps the conversation on the device - not in the business.
- Connecting to the official platform moves conversations to a server, which is what turns them into an asset.
- Outside the 24-hour window you can only reach out with a pre-approved template.
- The right option follows how many people touch the same customer.
In Israel the customer conversation happens on WhatsApp, so the question is not whether to connect it to a CRM but how. The three available options differ on one practical point that decides everything: where the conversation is stored, and what happens to it when the rep who ran it leaves.
The three options
| Option | What you get | What you give up |
|---|---|---|
| WhatsApp Business app | Fast, free, no setup | Conversation on a device; no central record; broadcast recipient limits |
| Connection through a provider/BSP | Relatively quick setup, ready-made interface | Dependence on the provider; cost and control sit with them |
| Direct WhatsApp Business Platform | Full control, conversations stored with you | Requires development and setup with Meta |
Choosing between rows two and three is mostly a question of development capacity. Choosing between row one and the other two is a business question: are the conversations an asset of the business or of the rep.
What happens to history when a rep leaves?
This is the deciding question for most businesses. In the app, the conversation sits on the device the rep holds. When they leave - even on entirely good terms - the history goes with them, and a customer who writes a week later reaches someone who no longer works for you.
With the official platform, every inbound and outbound message is stored on your server or the provider's, linked to the customer record, and visible to anyone with permission. A departing rep changes nothing about the information.
It is also the answer to the common question "why not just carry on with the app": because in the app you are building history that is not yours.
The 24-hour window - the rule that surprises every business
On Meta's official platform, once a customer writes to you a window opens in which you can reply in free text. After it closes, a business-initiated message is only possible using a template approved in advance by Meta.
The practical consequence: an appointment reminder, a delivery update or a review request all need an approved template, and approval takes time and is sometimes rejected. A business planning proactive messages needs to build its templates ahead of time, not on the day it needs them.
What to check with each provider
- Where the conversation is stored, and who can view it.
- What happens when a rep replies from their personal phone - does the message reach the system.
- How a conversation is linked to an existing customer, and what happens when the number is unrecognised.
- Who owns the business phone number, and what happens when the contract ends.
- How messages outside working hours are handled.
- How conversations are exported, and in what format.
Point 4 surprises businesses regularly: a number managed through a provider and not registered to the business is a real risk when changing providers, and it is exactly the lock-in described in vendor lock-in warning signs and an exit plan.
What actually breaks
- Two parallel conversations - one in the system and one on the rep's personal phone.
- An unrecognised number creating a new record instead of attaching to the existing one.
- Messages sent and never answered, with nobody following up.
- A template rejected on the day it was needed, because it was not prepared in advance.
- Files and photos that sink into the thread without reaching the record.
The first is the most common of all, and it is not solved by training but by a decision: either the business number is the only number customers are spoken to on, or you accept that history will be partial. There is no middle state that survives, because once a customer has written to a personal phone they will keep writing there.
What do you gain from having the conversation in the system?
Beyond the record, four things that show up in daily work:
- Faster replies, because whoever is available can answer rather than only the rep who owns the thread.
- Full context before replying - what was bought, what was quoted, what service ticket is open.
- Real measurement of response time, instead of an impression.
- Continuity when someone is on leave or leaves.
The second is what changes the quality of the conversation itself: a rep who can see the customer has already asked twice about the same thing writes a completely different answer from one starting cold.
What to prepare before you start
- Decide on the number - a new one or the existing one, and who is registered as its owner.
- Prepare three to five templates for proactive scenarios: reminder, status update, review request.
- Define out-of-hours behaviour - an automatic reply and when a human returns.
- Decide who answers, and what happens when there is no reply within two hours.
- Link to the customer record by normalised number, so duplicate records are not created.
The last point connects directly to the phone-cleaning work described in migrating data from Excel into a CRM: numbers that are not normalised will not attach to the existing customer, and every conversation opens as a new record.
Consent and opting out
Proactive WhatsApp messaging rests on the customer being willing to hear from you, so it is worth structuring from day one: record where and when consent was given, allow opting out inside the message itself, and honour it across every channel - not only WhatsApp. A customer who asked to be removed and gets an SMS a week later experiences that as the same business, rightly.
Operationally that means one opt-out record every channel checks before sending, rather than a separate list per tool. It is also what prevents the common situation where an opt-out is recorded in the email platform but not in the CRM that sends the reminders.
Sources
Frequently asked questions
Can we start with the app and move later?
You can, and it is a reasonable start for a one-person business. What to know in advance: app conversation history usually does not migrate into a system, so the longer you wait the larger the part left behind. The move also requires a decision about the phone number itself.
What about groups and broadcast lists?
Those are app features rather than business-platform features, and they carry recipient limits. Structured bulk sending happens on the platform through approved templates, with rate limits set by the number's quality rating.
Won't customers feel it is a robot?
That is up to you. The same system can carry personal messages a rep writes, not only automated templates. The practical rule: templates for reminders and operational updates, human writing for anything that needs an answer.
How is Hebrew support?
The platform supports Hebrew, but test the rendering on the customer's side with a real message - particularly where numbers, links or document numbers sit inside a Hebrew sentence, which is exactly where text can appear reversed.
Keep reading
Related service
WhatsApp Cloud API
Templates, a two-way inbox and reminders on the official Meta API.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.