Forrester Explains Poppy 1.0 For Customer Service Leaders
Forrester released guidance on Poppy 1.0, a protocol that allows customers to delegate tasks to personal AI agents, and what customer service leaders need to know. This protocol may change how companies interact with customers.
Original reporting · forrester.com
Original: “Poppy 1.0 Is Here: What Customer Service Leaders Need To Know”
Read “Poppy 1.0 Is Here: What Customer Service Leaders Need To Know” at Forrester →
How this was written. ABM Fuel wrote this article with a language model from Forrester’s reporting (model: @cf/meta/llama-3.3-70b-instruct-fp8-fast); it describes that reporting rather than adding to it. The original, linked above, is the full story.
Key points from Forrester’s report
- Forrester released guidance on Poppy 1.0, a protocol that allows customers to delegate tasks to personal AI agents.
- Companies have control over what personal agents can see or change, and can decide what customers can delegate to their AI agents.
- Implementing Poppy 1.0 requires making sure customer service tasks are AI-ready, and testing them end-to-end.
- Companies should be explicit about what's off-limits and decide which tasks they won't allow personal agents to perform through Poppy.
- Forrester clients can book a guidance session to understand what this means for their customer service operations.
Customer service leaders may need to adapt to a new protocol called Poppy 1.0, according to Forrester. This protocol allows customers to grant access to their personal AI agents, giving companies control over what those agents can see or change. Companies may decide what customers can delegate to their AI agents, and personal agents can still use other routes to interact with the company.
Forrester reported that doing nothing may not be the best choice, as personal agents can still reach companies without Poppy. By publishing Poppy, companies can give willing agents an authoritative source for dealing with them, while deciding what they can access or change. This approach may give companies more control over the interaction.
The key to implementing Poppy 1.0 is to start with the customer's task, not the protocol. Forrester suggests identifying tasks where delegation removes meaningful customer effort and where companies are comfortable with an AI agent completing the work. Companies should be explicit about what's off-limits and decide which tasks they won't allow personal agents to perform through Poppy.
Forrester also advises companies to make sure customer service tasks are AI-ready. This means scrutinizing what it takes to complete a task and testing it end-to-end. Companies should map the skills required for the task and look for the human glue, such as employees compensating for disconnected systems or undocumented exceptions.
Before making a customer service task available to personal agents, companies should improve system access, make ambiguous policies executable, and identify the tacit knowledge that AI will need. Forrester clients can book a guidance session to understand what this means for their customer service operations.
The implementation of Poppy 1.0 may have significant implications for customer service operations. Forrester notes that personal AI agents will increase service volume and expose unresolved demand that customer effort used to keep out of sight. Companies can use this unresolved demand to find problems that customers shouldn't need to chase them about in the first place.
Questions and answers
What is Poppy 1.0?
Poppy 1.0 is a protocol that allows customers to grant access to their personal AI agents, giving companies control over what those agents can see or change.
Do companies have to use Poppy 1.0?
No, companies do not have to use Poppy 1.0, but doing nothing may not be the best choice, as personal agents can still reach companies without Poppy.
How can companies implement Poppy 1.0?
Companies can implement Poppy 1.0 by starting with the customer's task, not the protocol, and making sure customer service tasks are AI-ready.


