October 2026

2026-10-30 — Tracked links: Get notified when a recipient opens your shared content

After sending a deck, you shouldn’t have to keep checking view counts to know whether someone has opened it. Tracked links give each recipient their own link to an Octave asset and notify you when that link is opened. Get a direct Slack message by default, or choose a Slack channel or email, with notifications for every view or just the first. When Octave knows the recipient’s contact and open deal records, it connects your content link to those records, and logs activity on the deal timeline. This gives you a clearer signal for when to follow up.

Use case: Send a prospect her own deck link and get a Slack notification when it’s opened, giving you a clearer signal for when to follow up without checking view counts by hand.

Problem it solves: A single shared link showed that someone had opened an asset, but didn’t connect that activity to a specific recipient. Sellers had little information to help time their follow-up.

2026-10-29 — Zoom guest emails: Identify prospects who join Zoom calls as guests

When a prospect joins Zoom without signing in, their missing email can leave Octave without a contact to connect to the conversation. Octave now looks for that email in the Zoom invite list or a matching Salesforce or HubSpot meeting. To qualify, a CRM meeting must have the same Zoom link and start within an hour of the call. Octave only fills in the email when the name match is unambiguous. Matched guests become contacts and external participants on the call, helping you see who attended and what they said, and connect the conversation to the right deal for revenue insights.

Use case: Open a Zoom call where a prospect joined as a guest and see them listed as a participant, helping you connect the conversation to the right contact and deal.

Problem it solves: Guests who weren’t signed in to Zoom often arrived without an email address and were left out of the participant records. That could make a customer call appear to have no external participants.

2026-10-27 — Credit usage report: See where your workspace’s credits go

A credit balance tells you what’s left, but it doesn’t explain what you’ve used. The new Credit usage tab in Workspace Settings → Plan usage shows your workspace’s final Octave credit charges over the last 7, 30, or 90 days. View usage over time in a line chart or explore daily totals in stacked bars. Break usage down by activity, source, Octave Managed Agent agent type, and event type, so you can see which workflows used the most credits or investigate a spike.

Use case: Open Plan usage, select the last 30 days, and see which agent type used the most credits—or use the breakdowns to investigate a sudden increase.

Problem it solves: A credit balance showed owners what was left, but not where their credits went. Understanding a spike meant asking Octave for help.

2026-10-23 — Ask Octave Answers Across Records: Connect the dots across your deals and accounts

Ask Octave answers questions that span records by searching the knowledge graph and connecting the library, accounts, deals, calls and people into one answer. Natural phrasing works: it maps "rev ops leader" to the RevOps Leader persona and uses a persona's listed job titles to find the match. When a tool fails during a request, Ask Octave says so, so a thin answer can be traced to a retrieval problem.

Use case: A sales manager can now ask "Why did we win this deal?" and get one answer drawn from the deal, its calls and the people involved.

Problem it solves: Questions across records could miss the graph search, and name matching relied on overlapping keywords, so deal investigations took separate lookups.

2026-10-23 — Share Ask Octave conversations with your team

The owner of an Ask Octave conversation can share it with the whole workspace or with selected members. Teammates open it in a read-only view, see who owns it, and follow the questions and answers behind the result. Only the owner can continue, rename, unshare or delete it. Someone opening a private thread sees an unavailable message instead of a blank chat.

Use case: A sales manager can now send a teammate a link to an Ask Octave conversation and have them read the full thread behind the answer.

Problem it solves: Threads were visible only to their creator, so a link gave teammates nothing and passing along an answer meant copying text out of the chat.

2026-10-23 — See what happened to incoming calls and activity

Ingestion Overview shows how incoming calls and activity move through Octave. In Settings > Connections, it shows totals for Received, Filtered, Pending and Processed activity, switchable between a provider table, a stacked bar chart and a flow diagram. For Zoom and Gong, it also compares Octave's totals with the records the connected account still makes available.

Use case: A workspace owner can now find out why a call is missing: unavailable from the provider, excluded by a filter, or still waiting to be processed.

Problem it solves: A missing call had no visible cause, so owners had to ask support where the gap occurred.

2026-10-23 — Bring Zoom Phone conversations into Octave

Octave imports recorded Zoom Phone calls that have transcripts as call events. They use the same processing and historical import as Zoom meetings. Findings from those calls feed matching and library Suggestions. The import uses the existing Zoom connection with Zoom Phone access and the required permissions, and workspaces without them keep importing meetings as before.

Use case: An SDR who sells over the phone can now see buyer objections from Zoom Phone calls turn into library Suggestions.

Problem it solves: Zoom Phone recordings were missing from Octave even when Zoom was connected, so phone conversations never contributed evidence.

2026-10-22 — Choose a default brand kit for your workspace

Workspace owners can set a default brand kit in Settings, Workspace, General. Skill runs, Deal Pulse, demos and MCP tools check that kit first. If it is deleted or made private, Octave falls back to the newest workspace-wide kit, and private kits are never used to brand the workspace. Owners can clear the default at any time, and two MCP tools read or set it from a connected assistant.

Use case: A marketing lead can now set one default brand kit and have every skill run and Deal Pulse output use it, without choosing a kit each time.

Problem it solves: With several brand kits in a workspace, generated content depended on whichever kit a tool found first.

2026-10-21 — Give Ask Octave a familiar ChatGPT or Claude look

Ask Octave offers ChatGPT-style and Claude-style desktop appearances next to the original Octave look. The choice is made from the conversation options menu and is remembered per user in each workspace. The layouts use a flat sidebar, a conversation area that scrolls on its own and a compact message box that stays in view while an answer streams. Debug and Trace sit in the options menu.

Use case: A rep who works in ChatGPT all day can now switch Ask Octave to the ChatGPT layout and keep it there.

Problem it solves: Ask Octave had one layout, so people used to other chat tools had to relearn the basics.

2026-10-19 — Suggestion Swipe Review: Keep your library current, one card at a time

Suggestion Swipe Review is a dedicated place to work through the Suggestions queue. From the Suggestions inbox, apply filters and select Start review. Each suggestion appears as a card, with the right arrow to accept and the left arrow to reject. A refine chat under the card rewrites a suggestion without leaving the page.

Use case: A workspace owner can now clear a backlog of dozens of Suggestions in one sitting with the arrow keys, rewriting any that need work in the refine chat.

Problem it solves: Reviewing each Suggestion from the inbox was slow enough that people put it off, and the backlog grew.

2026-10-15 — Keep product docs and release notes connected to Octave

Connect a product documentation site, a developer documentation site or a release notes page to Octave. Octave reads the site's llms.txt file to find its pages and keeps that content current. Answers cite the source passages they draw on. To add one, open Connections and choose a collection type under Add source.

Use case: A solutions engineer can now connect the developer docs site once and have Octave's Context API answers cite the exact passages they came from.

Problem it solves: Product details were copied into the library by hand, and answers could come from outdated docs.

2026-10-07 — Connections: Keep your context graph aligned with your sources

Connections keep your context graph in line with the sources your team already maintains. Connect Notion pages, Google Drive docs, live webpages, or published Octave assets, or upload files and paste text. Octave checks each connection weekly and, when it finds a significant difference, creates a Suggestion that is already filled in for you to review. One-way sync updates the context graph from changes in a doc or site. Two-way sync also lets Octave update the connected doc when your library changes. Teams stop copying edits between their docs and Octave by hand, and the library stays in step with what they have written down.

2026-10-07 — Talk to Ask Octave about your Google Docs

Ask Octave can read a Google Doc pasted into the chat. Octave opens it through the workspace's connected Google Drive and reads only the tab named in the link, with read-only access. Questions, context graph updates, and insights analyses can all use the doc. It stays out of the shared library unless someone adds it as a Connection.

Use case: A sales engineer can now paste a Google Doc link into Ask Octave and ask a question about that one doc, without adding it to the library.

Problem it solves: Using a doc once meant copying its text into the chat or adding it to the library.

2026-10-07 — See what changed between asset versions

Any two versions of a hosted page can be compared side by side. Additions, removals and wording changes are highlighted. The comparison works on a teammate's edit or an agent's update alike.

Use case: A marketing owner can now compare an agent's update to a deck against the current version and see each changed line before approving it.

Problem it solves: Checking what changed between two versions of a page meant opening both and reading them line by line.

2026-10-07 — Gallery view for shared assets in Octave

The Assets page has a gallery view of the team's shared assets. Each hosted page shows as a thumbnail, and search finds the one you need. Everyone browses the same shared set.

Use case: A rep can now open the gallery, search for a battle card, and find the one a teammate already built.

Problem it solves: People did not know which battle cards, one-pagers and decks already existed, so teams rebuilt assets that were already there.

September 2026

2026-09-24 — Build new library items from what Octave already knows

Creating a library item by hand, such as a persona or competitor, first checks whether Octave already has a suggestion for it. The creator can use the suggestion as it is, edit it, or start from scratch. For competitors and reference customers, Octave also shows that company's recent activity as source material.

Use case: A product marketer can now start a new competitor entry from what Octave already suggested, and see that company's recent activity while writing it.

Problem it solves: Manual creation started from a blank form, even when Octave had already worked out most of the entry from customer conversations.

2026-09-23 — Filter customer feedback by customer type and call purpose

The Voice tab can be narrowed to specific kinds of conversations. Two filters, customer type (new or existing) and call purpose, apply to the whole page. The totals, the charts and the quotes all update to match the filter.

Use case: A product marketer can now filter Voice to discovery calls with new customers and read only the quotes from those conversations.

Problem it solves: Voice mixed quotes from every kind of conversation, so feedback from a renewal call and a first discovery call counted together.

2026-09-23 — Automatically remove duplicate recordings

When several tools record the same meeting, Octave keeps only the longest recording so the conversation counts once. The behavior is on by default for new recordings. Existing duplicates are left as they are.

Use case: A RevOps owner who runs two recorders on the same calls can now trust that each conversation is counted once in findings and analytics.

Problem it solves: One meeting captured by two tools showed up as two conversations, which inflated counts and repeated the same findings.

2026-09-23 — See which library updates are substantial

The library's change history labels each saved edit as none, minor or material. The label is based on how much of the item's text changed when it was saved. It appears beside each revision in the history.

Use case: A library owner can now scan an item's history and open only the material rewrites, skipping the typo fixes.

Problem it solves: Every saved edit looked the same in the history, so telling a small correction from a substantial rewrite meant reading each revision.

2026-09-21 — Cohorts: Compare win rates across groups of deals, by conversation topic

Cohort comparison sets two groups of deals side by side based on what came up in their conversations, such as whether they are considering specific competitors or planning to build in-house. It shows which group has the higher win rate, how large the difference is, and a confidence score. The topics come from conversation content, not from CRM fields.

Use case: A sales leader can now compare deals where the buyer mentioned an in-house build with deals where they did not, and see whether the win rate gap is large enough to trust.

Problem it solves: Comparing win rates by conversation topic meant exporting deals and sorting them by hand, with no sense of whether a gap was meaningful.

2026-09-19 — Unified event analytics

AI assistants and custom integrations can get conversation analytics through one request: counts, rankings, detailed breakdowns and trends over time. Every request takes the same date range and the same breakdowns, such as company, deal stage, or which side of the call was speaking. The answers stay consistent across the four kinds of question.

Use case: A RevOps analyst can now have an AI assistant rank competitors by mentions and then chart the trend for the top one, with the same date range and breakdown on both questions.

Problem it solves: Analytics questions went through separate tools with their own filters, so an assistant had to stitch the pieces together and the numbers did not always line up.