Solutions

Product insights for agents

See how people use your agents, where the experience gets in their way, and which workflows your product should support better.

Paste into a coding agent running in your project folder.

Agent prompt

Talk to an engineer
Intelligence / Product insights

What are people trying to do?

Start with the patterns. Follow them back to the conversation.

Users ask to compare plans
Workflow opportunity
Explore
Users repeat the date range
Missing application context
Explore
“Can you compare these side by side?”

The agent returns a separate answer for each plan. The user needs a comparison they can work with.

Any agent frameworkOpen protocolsSelf-hostableBuilt for your product
A WORKFLOW TO START WITH

Your users are telling you what the product should do next.

Conversation is a new source of product evidence. The requests people repeat and the work they take over show where the experience can improve.

The request
“Can you compare these plans side by side?”
Illustrative scenario

The work

The agent gives separate answers, but the user keeps asking for a comparison. Follow the interaction to see the gap between the response and what the person actually needs.

The result

Give the comparison a place in the product: an interactive table, useful criteria, and a clear next action. Use the evidence to decide what to build.

01

See the whole experience

Bring conversations, tool activity, generative UI, and application state together so product teams can understand what people were trying to do.

02

Find patterns worth acting on

Look at repeated requests, corrections, and moments where users step in. Trace an insight back to the interactions that support it.

03

Decide what to change

Improve the interface, workflow, or available tools. When the opportunity is better agent behavior, turn the lesson into a Skill.

A shared view for product, engineering, and domain experts.

Rich Threads preserve messages, tool activity, generative UI, and application state. Intelligence helps you connect the patterns to the experiences behind them, so the team can decide what deserves attention.

Explore the documentation

Start with a product question.

Where do users get stuck? What do they ask for that your product cannot help them do? Review the interactions, choose a change, and look for improvement in the next round of use.

Explore Product Analytics

Put it to work with your agent.

Copy the setup prompt into your coding agent to start building with CopilotKit.

Paste into a coding agent running in your project folder.

Agent prompt

Talk to an engineer