A Shopify WhatsApp support app should match the way your team already answers. If one person replies from a phone, a click-to-chat button is the right tool. If several people need one shared transcript, assignment, and internal notes, that is an inbox product, and a button app should not be forced into that job.
WhatsApp Chat Button is a free storefront widget. The catalog documents the button, a popup, a list of agents the shopper can choose, business hours, and click counts. It does not document a shared inbox. Choose on that difference before you compare logos.
Start with who answers today
Write down the real operating model before you open an app listing. The useful questions are short.
- One phone: the owner or a single support person already replies in the WhatsApp app on that device.
- A few numbers: sales, wholesale, and order help are different people, and the shopper should pick one.
- A queue: several agents share one number, a supervisor assigns chats, and the history has to stay in a desk tool.
Best-app roundups often skip that split. They rank features a store will never use. A merchant who answers alone does not need assignment. A merchant with a queue will be disappointed by a button that only opens WhatsApp on a phone.
Use a button when one person replies on a phone
Click-to-chat means the shopper taps a button and WhatsApp opens with a message already started. The conversation then lives in WhatsApp, on the phone number you configured. There is no second inbox inside Shopify.
The free plan in the catalog includes the storefront controls a one-person team actually touches: button design, the popup, business hours, a GDPR consent checkbox, page rules, and analytics for clicks. Billing is Shopify Managed Pricing. The catalog does not add a paid tier for those controls.
Business hours do not remove the button. Outside the hours you set, the button dims and the popup text changes. A shopper can still see it. Write the offline sentence so it tells them when you reply, instead of implying the chat is staffed.
Page rules can show the button on product pages and hide it on a policy page. Device rules can show it on mobile, desktop, or both. Those settings keep one person from being pinged on pages that do not need a chat.
Use the agent list when two or three people have their own numbers
The popup can list more than one agent. Each entry has its own phone number, name, avatar, and greeting, and it can be limited to certain page types. The shopper chooses who to message. Each choice still opens that person’s WhatsApp. It does not drop every chat into one shared screen.
That fits a small team that already works this way. Wholesale messages go to one number. Order problems go to another. The storefront makes the choice visible, which is better than one overloaded phone.
It does not fit a team that needs a manager to assign a chat after it arrives. There is no assignment queue in this app. If your process depends on that, say so in the buying notes and look at an inbox product. Do not describe the agent list as a shared inbox.
Extra contact rows can sit under the panel: Telegram, Instagram, a phone call, or email. Those are additional links, not a combined ticket system.
Buy an inbox only when the team needs a shared transcript
An inbox product is a different purchase. You are paying for a place where several agents see the same conversation, leave notes, and hand the chat to someone else. Some of those products also sell bots, campaigns, or a WhatsApp Business API connection. Those capabilities are not documented for WhatsApp Chat Button.
Before you switch, verify the inbox claims on that vendor’s current listing and help docs. Check whether the shared number is included, whether assignment is real, and what the plan costs. Do not copy a price from a truncated App Store excerpt into your own notes. This article does not name a winning inbox app, because the right one depends on the queue you have.
A button can still sit beside an inbox. Some stores use the button for simple product questions and a separate tool for the queue. That is a reasonable split. It is a poor split if nobody will watch the phone that the button opens.
What the free button will and will not report
The dashboard counts clicks, popup opens, and send taps for a date range. Optional Google Analytics and Meta Pixel events can fire on a tracked click. Those numbers tell you that people used the button. They do not tell you whether the person on the phone replied, or whether the chat became an order.
Judge the tool by reply habits, not by the click total alone. If clicks rise and replies do not, the gap is the team’s process. Another app will not fix an unanswered phone.
Set the hours to the shift that phone is actually watched, in that desk’s timezone. Outside those hours the button dims and the popup text changes. It stays on the page. A consent checkbox can require a tick before Send, remembered in that browser, with no exportable archive. Leave auto-open off on product pages so the panel does not cover add to cart. Those controls are part of fitting the button to one person. They do not turn the button into a queue.
A practical choice
Stay with a button
Stay when one person, or a short list of people with their own numbers, already answers in WhatsApp. Install WhatsApp Chat Button, set the number or the agent list, and test one product page on a phone.
Look for an inbox
Look elsewhere when you need assignment, internal notes, or one transcript that several agents share. Say that requirement in the first line of your shortlist. A free button is the wrong promise for that team, and pretending otherwise creates a support gap you will notice on the first busy day.
Match the app to the team you have now. You can change later. You should not buy a queue tool for a single phone, and you should not ask a button to behave like a desk.
Check the reply path before you install
The app can place the button. It cannot make someone answer. Name the person who owns each number in the agent list, and agree the hours those numbers are watched. If a number is only a marketing line that nobody opens, leave it off the chooser.
Send one test from a product page, one from a collection page if the button is allowed there, and one outside the published hours. Confirm the greeting, the dimmed offline state, and that the chat arrived on the intended phone. Those three checks take less time than migrating a queue you do not have.
If the test shows that shoppers need a shared transcript after all, stop and shortlist an inbox. The button page on the Squadkin site is the reference for the click-to-chat setup, not a promise that the same app will run a help desk.