Skip to main content

​
The learning loop

The analytics pipeline turns conversations into findings. Suggestions and Revisions are how those findings change your strategy: when Octave detects a recurring pattern — a new objection across multiple calls, a competitor gaining mention frequency, a value prop landing in won deals — it proposes a concrete Library update, your team decides, and every decision is recorded. The review loop is Evidence → Suggestion → acceptance → Library update → Revision. Acceptance can be a manual decision or an enabled workspace auto-approval policy, subject to its confidence threshold, allowed entity types, and daily caps. Direct entity edits are also possible; they do not require a suggestion.

​
Suggestions

A Suggestion is a proposed Library change grounded in evidence. There are two kinds:
  • Create — propose a new entity: an Objection prospects keep raising, a Competitor that started appearing in deals, a Buying Trigger that precedes your wins.
  • Refine — propose changing an existing entity: add a newly discovered pain point to a Persona, update a Motion ICP narrative, attach a new proof point.
Suggestions carry proposed content and source information. With includeEvidence=true, conversation-sourced suggestions expose evidence; intel-sourced refinements (sourceType: "trends") expose intelEvidence instead. User-created suggestions need not have conversation evidence. Suggestions are reviewed from the dashboard, via API, or by an AI assistant through the MCP suggestion tools:
  • Accept — the change is applied to the Library and takes effect for every agent and workflow on the next run.
  • Reject — the proposal is declined and recorded, which also teaches the pipeline what your team considers noise.
You can also create suggestions yourself — from field feedback, a lost-deal review, or an assistant conversation — and route them through the same review flow instead of editing entities directly. That keeps one decision trail for every strategy change, whatever its source.

​
Revisions

A Revision is the immutable record of an applied change: what changed, what the content was before and after, when, and its source, including a suggestion when applicable. Revision recording is asynchronous and does not cover every maintenance write. Revisions answer “why does our messaging say this?” months later — you can trace a positioning statement back through the suggestion that proposed it to the calls that motivated it.

​
API surface

  • GET /api/v2/suggestion/list, GET /api/v2/suggestion/get — browse the review queue
  • POST /api/v2/suggestion/create, POST /api/v2/suggestion/update — create and edit proposals
  • POST /api/v2/suggestion/accept, POST /api/v2/suggestion/reject — decide
  • GET /api/v2/revision/list, GET /api/v2/revision/get — read the change history