Skip to main content

How the Insights Agent works

What the Insights Agent does, what data it reads, how it generates results, and how to understand the status of each insight.

Written by Simon Oliver
Updated over 2 weeks ago

The Insights Agent answers research questions about your customer feedback. You ask a question in plain language - "What are the most common complaints from enterprise customers?" - and the agent searches your mentions, backlog, surveys, and uploaded files to generate a written answer with evidence.


What the agent does

When you submit a question, the agent uses a series of tool calls to search and synthesize your workspace data. It reads:

  • Mentions - individual feedback entries from all your integrations and survey responses

  • Backlog items - issues and feature requests Pilea has identified across your feedback

  • Survey responses - answers and summaries from any surveys you've run

  • Uploaded files - CSV or spreadsheet data you've imported

The agent does not read your source code, billing data, or any data outside your Pilea workspace. It does not store your question or the generated insight outside of Pilea.

SCREENSHOT: Example of an insight agent named "Daily bug digest".

Two ways to get insights

Agents (scheduled): Agents run automatically on a schedule you set (see screenshot above). Each agent has a fixed prompt that runs at the scheduled time and delivers the result to a Slack channel, email, or both. This is useful for recurring questions like "What feedback came in this week?" or "Which backlog items are growing in mentions?"

Ad-hoc insights: Click Create Insight on the Insights page to ask a one-off question. The agent runs immediately when you submit it. Use @ in the prompt to reference specific backlog items, customers, surveys, or uploaded files and focus the search.

SCREENSHOT: The Insights page showing agent avatars at the top and a grid of insight cards below.

Understanding insight status

Each insight card shows a status as the agent works:

Status

What it means

Pending

The insight is queued and will start shortly

Generating

The agent is actively searching and writing the result

Completed

The insight is ready to read

Failed

The agent could not find enough data. The card shows "Insufficient data".

Most insights move from Pending to Generating to Completed in under a minute. If your workspace has a large number of mentions, it may take longer.

ℹ️ Note: A "Failed" insight with "Insufficient data" usually means the question was too narrow for the data available - for example, asking about a customer segment with no feedback yet. Try broadening the question or checking that the relevant integrations are connected.

What's inside a completed insight

Open any completed insight card to see the full result. Each insight includes:

  • A written narrative answering your question, with inline references to the mentions and backlog items used

  • Related Backlog Items - backlog items the agent identified as relevant, which you can triage directly from the insight view

  • Suggested Follow-ups - related questions you can click to explore further

Use Copy Insight to copy the text to your clipboard, or Share to copy a direct link.

[SCREENSHOT: An open insight detail showing the narrative content, Related Backlog Items, and Suggested Follow-ups sections]

Insight visibility

Insights you create yourself are private by default and show Only me on the card. Agents always publish their insights to the workspace so your whole team can see them, shown with a Published badge.


Related articles

  • Running your first insight with the Insights Agent - Step-by-step guide to submitting your first question

  • Writing effective prompts for the Insights Agent - How to phrase questions that get useful results

  • Setting up an agent - How to configure schedule, delivery, and prompt for a recurring agent

Did this answer your question?