Safely manage your Zendesk from the AI assistant you already use, via the Deltastring MCP. Beacon configuration platform →
← Back to news

Meta’s AI Tamagotchi bet is…working?

Meta's personal AI agent Muse is gaining traction at a pace that outstrips ChatGPT's early mobile adoption, signalling a decisive shift in how consumer AI products are being distributed and adopted. The company is expanding Muse beyond its current mobile footprint into smart glasses and a dedicated Tamagotchi-style wearable device, a hardware-first strategy that contrasts sharply with the browser and app-based approaches that dominated the initial AI boom. This expansion arrives amid intensifying competition from OpenAI and Anthropic, who are now locked in rapid model release cycles—Anthropic's Opus 5.5 followed by OpenAI's GPT-6 updates within 90 minutes—suggesting the frontier has shifted from model capability to distribution and user integration.

For CX teams, the implications are substantial. Meta's success with Muse raises a critical question: as consumer AI agents become ambient and wearable rather than application-based, how will enterprise support platforms need to evolve to compete for user attention and integration? The traditional ticketing and case management workflows that underpin modern CX infrastructure assume users will actively seek support through designated channels. A Tamagotchi-style device that delivers AI assistance passively throughout the day fundamentally challenges that assumption. Teams already running Agentforce or similar agent-based platforms should be monitoring whether their architectures can operate across fragmented hardware ecosystems, or whether they risk becoming relegated to backend infrastructure whilst consumer-grade AI captures the primary user relationship.

The velocity of this shift also matters. Meta's hardware play isn't speculative—it's already in development with clear timelines. For mid-market and enterprise CX vendors, the question becomes whether to build agent capabilities that integrate with these emerging consumer platforms or to double down on enterprise-specific workflows where control and compliance remain paramount. The money is flowing toward consumer adoption and hardware integration, not toward incremental improvements to existing support ticketing systems.