Facebook launches closed beta of Customer Chat, a plugin for businesses to enable Messenger chats on company websites; works across multiple devices
While most of the billion-plus users on Facebook Messenger are individuals, the company has refined its messaging platform to be more business-friendly.
Context & Ripple Effects
This beta is the third step in Facebook's slow migration of business messaging off its own properties. It opened Messenger to commerce with Businesses on Messenger in 2015, then let sites embed threads via the Page Plugin that December. Customer Chat goes further: instead of a page widget, businesses get a full chat surface on their own domains, tied to the same Messenger thread a user already has on mobile.
First-order effects
- Businesses in the beta can serve website visitors through persistent Messenger threads, so a conversation started on desktop continues on the customer's phone without a new login or session.
- Facebook gains placement of its messaging client on merchant-owned real estate, extending Messenger beyond the app and into checkout and support flows it does not host.
Second-order effects
- Web live-chat vendors now compete against a free channel backed by Messenger's billion-plus-user identity graph, pressuring per-seat chat pricing toward the messaging-model end of the market.
- Developers building on the chat SDK for shopping and booking bots gain a second distribution surface — the merchant's own site — rather than being confined to discovery inside Messenger.
Third-order effects
- If the pattern holds through later iterations like the 2020 Chat Plugin update and the appointment-booking and lead-gen toolset, customer service consolidates around portable messaging identities rather than per-site chat silos, making the conversation itself the transaction layer.
The trend: Customer support is shifting from site-specific chat widgets to cross-device messaging threads anchored in platform identity graphs.