What is a product agent?
A product agent is an AI agent that learns how an application works by using it. It can use that knowledge to answer questions, guide people through workflows, or take supported actions. Its knowledge depends on the workflows and information it can access.
What a product agent learns
A product agent can learn navigation, control names, task sequences, and the results of actions it performs. For example, it can learn that creating a report requires a connected data source and which steps complete that connection.
The learning account determines which experiences are available. A product with separate administrator and member workflows may need separate learning access for each. Product changes also require refreshed knowledge.
How access limits its knowledge
An agent learns the parts of the application available to its account. A workflow behind a permission or an unavailable feature flag may be outside that experience. Source code, internal policies, and business rules that are not exposed through the application are separate information sources.
Decide which environments and accounts the agent can use, and which actions are appropriate during learning. Access to a workflow is not proof that every path through it has been learned or checked.
Where Frigade uses it
Frigade Assistant uses learned product knowledge to answer questions, guide users through workflows, and help with supported actions. It can also draw on documentation and guidance from your team. How Frigade works explains the learning process and how knowledge is refreshed.
Frigade Knowledge uses that product understanding to compare help articles with the application and propose corrections. Your team can review the changes before publication. Read how to keep a knowledge base up to date when the product changes every day, or explore Frigade Knowledge.
Common questions
- How is a product agent different from a chatbot trained on docs?
- A chatbot that uses documentation answers from written sources. A product agent also learns by working through the application, including its controls and task sequences. The approaches can complement each other: documentation can explain policies or limits that using the interface alone would not reveal.
- Does a product agent need access to my source code?
- Frigade learns workflows through an account in your application, without requiring source-code access. Give that account access to the workflows you want it to learn. Documentation and guidance from your team can add information that is not available through those workflows.