Skip to main content
An insight is something a customer said about your business rather than about themselves: a bug, a feature request, an objection, a pricing concern, a competitor. Each one is tied to the account that said it, with the quote and speaker when there is one. Insights are available through MCP and the REST API. There is no Insights page in the open-source app.

​
Where insights come from

  • Extraction. When the worker processes a call transcript, it runs a second pass that pulls out what the call taught you about your own business.
  • Your agent. An agent that reads a call or email can write insights directly with record_insight or POST /v2/insights.
New insights are sorted once a day, around 05:30 UTC. Sorting places each one in a lane and subtype and links it to an account. Until then it does not appear in reads.

​
Read insights

Over MCP, call get_insights. Over REST:
Filter by lane, subtype, one account with focus, or a start date with since. Lanes and subtypes are listed on List insights. The response includes the workspace’s taxonomy, so you can show labels without hardcoding them.

​
Write insights

Over MCP, call record_insight. Over REST:
category is one of product, positioning, market or buyer. Send every insight from one source in one call. Near-duplicates are skipped, so written can be lower than submitted. See Record insights. Facts about the account itself, such as a new title or a budget, are not insights. Write those as a note. On a self-hosted instance, replace https://api.opennous.cloud with your own API URL.