Meta and Sierra have launched the Personal Agent Protocol (Poppy), an open standard that establishes a framework for AI agents to identify themselves to businesses and allows customers to granularly control what those agents can access and modify. The protocol operates through a standardised file published at a fixed location on each company's website, enabling agents to authenticate themselves, request appropriate permissions, and operate within defined boundaries—whether as unauthenticated guests checking product availability or as authenticated users with read-only or full account access. The initiative addresses a critical operational gap: only 23% of merchants can currently identify AI-driven traffic, leaving businesses forced to choose between blanket blocking (as Amazon did with Meta's Muse agent in September) or granting unrestricted access. Poppy's design partners now include 35 organisations spanning payments infrastructure (Visa, Mastercard, PayPal), financial services (Bank of America, Wells Fargo), commerce platforms (Shopify, Walmart, Target), and travel (United Airlines), with a live demonstration showing Muse successfully navigating Rocket's mortgage preapproval process by coordinating with Rocket's own AI agent.
The implications for CX teams are substantial but require careful calibration. Poppy addresses a genuine trust deficit—56% of consumers permit agents to search and compare products, but only 35% grant payment credential access—yet the protocol currently excludes payments functionality, with card networks developing parallel frameworks (Visa's Trusted Agent Protocol, Mastercard's Verifiable Intent). For teams already managing customer interactions through Zendesk, Freshdesk, or similar platforms, the question becomes whether Poppy adoption will fragment the agent ecosystem further or create operational clarity. The protocol's reliance on customer-side permission management introduces new friction points: support teams must now educate customers on granular permission models whilst simultaneously managing agents that operate across authenticated and unauthenticated states within a single session. This creates a support burden that extends beyond traditional CX tooling.
The broader concern centres on whether Poppy's open-standard approach will actually achieve adoption at scale or become another fragmented standard competing with proprietary agent frameworks. With payment extensions still on the roadmap and card networks pursuing parallel protocols, CX leaders should monitor whether Poppy becomes the de facto standard or whether merchants continue implementing bespoke agent-blocking rules. The 132 million U.S. adults already using AI-assisted shopping suggests customer demand exists, but the gap between search-and-compare trust (56%) and payment trust (35%) indicates that permission frameworks alone won't resolve deeper concerns about agent autonomy and transaction security. Teams should prepare for a transitional period where Poppy coexists with blocking strategies and proprietary agent protocols, requiring flexible authentication and logging capabilities within existing CX platforms.
Meta and Sierra’s Poppy Lets Customers Set Limits for AI Agents PYMNTS.com