WhatsApp on the site, not decoration
"Connect WhatsApp" can mean one link - or a full system that replies, captures leads, and updates the business.
In Israel, WhatsApp is not "another channel." It is where the customer already lives. So almost every business with a site eventually asks: add a button, open a chat, build a bot. The problem is that the same family of words covers four completely different products - with different cost, limits, and outcomes.
I am Naor from NaorX. I have shipped simple WhatsApp buttons, CRM wiring, and bots on the Business API. Pricing and scope for bots is covered separately in what a WhatsApp bot really costs. Here the focus is different: what you actually connect to the website, and when each option fits. For the broader integration mindset, see also the API guide.
Four connection levels (light to heavy)
1) Button / wa.me link
Customer taps on the site, WhatsApp opens to your number (sometimes with prefilled text). Fastest to install, cheapest to maintain, right when a human answers. Not a bot. A door.
2) On-site chat widget
A floating chat window. Behind it, it may still just open WhatsApp, or a third-party inbox. Looks more polished than a lone green icon - but usually still depends on a human unless automation sits behind it.
3) WhatsApp Business API (official business account)
You are no longer on a personal phone app. Business number, Meta rules, message templates for proactive outreach, quality limits. This is the base for serious bots, teams, and messages outside the 24-hour window.
4) Bot / automation on the API
Menus, intent replies, lead capture, booking, updates to Google Sheets / CRM, sometimes payment or order status. That is a product project - not "add an icon." How a full project looks on my side is also in behind the code at NaorX.
Simple rule:
If someone answers within minutes during business hours - start with a smart button. If you drown in repeat questions, or need nights / weekends covered - think API and bot, not another icon.
wa.me button - how to do it properly
The base looks like https://wa.me/9725XXXXXXXX (international format, no leading zero, no dashes). You can add prefilled text with text= - for example "Hi, I came from the website about...".
- Placement: not only the footer. On mobile a sticky button helps. On desktop - near the main CTA or after the value offer.
- Prefilled text: saves the customer thinking, and helps you spot site traffic.
- Business number: prefer a dedicated business line, not the owner private phone with no backup.
- Response hours: if you are offline at night - say so next to the button. Otherwise people expect an instant reply and bounce angry.
Field tip:
A button with nobody answering is worse than no button. If you travel or get slammed - at least set a business-app auto reply, or move up to a bot.
Chat widget - when it is worth it
A widget helps when you want clear on-page presence, multiple agents, or a smoother path between site chat and WhatsApp. It is less right if all you need is "tap and talk to me" - there wa.me wins on simplicity and load time.
Watch the weight: third-party chat scripts can slow the site. If speed matters for revenue - keep Core Web Vitals in mind.
Business API - when you move up
API enters when you need one of these:
- Real automation (not only an away message in the app)
- Multiple agents / an orderly conversation queue
- Proactive messages (reminders, order status) via approved templates
- Wiring to a sheet, CRM, booking system, or custom site
- Stability that does not depend on one physical phone dying or going offline
Important: Business API is not "install a WordPress plugin and forget." There is a BSP, business verification, template approval, and Meta policy. Anyone selling you a "smart WhatsApp bot with no API" on a personal account may work for a while - then get restricted exactly when leads peak.
A bot tied to the site - what it must do
A good bot is not trying to be a friend. It closes a job:
- Understands what the customer wants (booking / price / status / human)
- Collects the minimum needed (name, phone, request details)
- Writes it where the business actually looks (sheet, CRM, email, dashboard)
- Hands off to a human when the chat leaves the script
If the bot only dumps menus with no system behind it - you bought a toy. The connection is what saves time. That is the integrations world again.
Quick decision table
| Your situation | Start with |
|---|---|
| Small business, someone answers in business hours | wa.me button + prefilled text |
| Want visual presence / multi-agent chat | Widget (watch performance) |
| Many repeat questions, irregular hours | Business API + basic bot |
| Bookings / orders / status / CRM | API + automation wired to systems |
| Just "make it green on the site" with no reply | Do not start until someone answers |
Mistakes you see again and again
- Personal number on the site with no backup - owner on vacation, leads burn.
- Bot with no human escape hatch - customers get stuck and leave bad reviews.
- Promising a "smart bot" without official API on an unstable personal account.
- Heavy widget that kills mobile speed for a green animation.
- No record of where leads go - everything in chat, nothing in a system. Clear handover matters - see also what you get at delivery.
Checklist before you wire anything
- Who answers, and in which hours?
- What should the customer achieve in the chat (lead / booking / support / purchase)?
- Button, widget, API, or bot - from the table above.
- Where is the data stored after the chat?
- What happens when the bot / human is unavailable?
- Did you test on a real phone, not only desktop?
Summary
Connecting WhatsApp to a website is not one feature. It is a ladder: smart link, widget, Business API, and a bot wired to the business. Most businesses should start low on the ladder - and climb only when real load appears. Jumping straight to a "full bot" without a clear process often means paying twice: once to build, once to reset expectations.
If you know what the customer must do after the tap - choosing the connection gets much simpler.
Want WhatsApp on your site - from button to API bot?
That is the kind of work I do at NaorX. Describe what you have today and what is missing via the contact form, and we can break it into a clear first phase.
Need help with your project?
Whether it's a website, bot, automation or something else - I'm here to help you build a solution that works
