Facebook At Work Gets Its Own Version Of Messenger With Debut of “Work Chat”
Context & Ripple Effects
Work Chat is the second act for Facebook at Work's January 2015 pilot, which seeded the employee collaboration tool with a handful of test companies. The new app gives the enterprise product its own messaging client rather than borrowing consumer Messenger — the piece it needed before Facebook could charge for it.
The sequencing matters: within a year of this debut, Facebook readied the platform as a paid service billed per user (ahead of its London launch), then layered on bots and Box/Microsoft/Quip integrations and shipped a Workplace Chat desktop app reporting 30K organizations by late 2017. Work Chat is the communications foundation that whole stack sits on.
First-order effects
- Employees inside Facebook at Work test companies get a dedicated work-messaging app, splitting their professional conversations from their personal Messenger identities.
Second-order effects
- A standalone work chat client puts Facebook in direct line with enterprise messaging incumbents like Slack, forcing differentiation on price and integration breadth — which is exactly where Facebook went next with bots for Workplace and third-party integrations.
Third-order effects
- If the per-user billing model holds, Facebook converts a free consumer habit — chat — into recurring enterprise revenue, validating the playbook of porting consumer social products into paid workplace suites.
The trend: Consumer social platforms are repackaging their messaging infrastructure as per-user enterprise collaboration products, with chat as the entry point for bots, integrations, and paid tiers.