Pipedrive Nova: What It Actually Writes to Your CRM

Here is a scenario playing out at a lot of small B2B sales teams running Pipedrive right now: someone in sales ops gets an email about a new AI feature called Nova, skims it, sees "AI meeting assistant," and either turns it on for the whole team the same afternoon or ignores it because it sounds like every other AI announcement this year.

Neither reaction is quite right. Nova is a real, specific product with a real approval mechanism built into it, a real rollout-status question worth checking before you rely on it, and at least one independent review that already found gaps between the pitch and the hands-on result. It is also easy to confuse with Pulse, a separate Pipedrive prospecting tool that unifies lead enrichment and scoring. Nova is not that. Nova is about what happens to your CRM after a sales call.

If your team is deciding whether to turn Nova on, or you are just trying to understand what another CRM vendor's "AI writes your notes now" feature actually does under the hood, this is what is verifiable right now.

What Pipedrive Nova Actually Does

Pipedrive announced Nova's general availability on September 16, 2026, and says it is included in every Pipedrive plan at no extra cost, a meaningful detail since several AI CRM add-ons from other vendors sit behind a premium tier. Nova works in three stages around a sales call.

Before the meeting, Nova generates a briefing pulled from your CRM data, connected emails, calendar, and recent account activity, so a rep walks into a call with deal history already surfaced instead of digging for it manually.

During the meeting, you choose how it listens. Either an AI Notetaker joins the call as a visible participant and transcribes the conversation, or a separate Nova Companion desktop app captures system audio directly without any bot joining the call window. That second option matters for teams uneasy about a visible AI participant showing up on every client call.

After the meeting, Nova generates a summary, pulls out follow-up actions, and drafts suggested CRM updates, including fields like deal stage, deal value, and expected close date, based on what the transcript actually said.

Access depends on two separate switches: Nova needs to be active for your company's account, and you need a Nova seat assigned to you specifically. It also requires access to Pipedrive's Deals app to do anything useful, which is a reasonable constraint given what it is writing to.

The Part That Actually Matters: Approval, Not Automation

The headline risk with any tool that reads a call and touches CRM fields is the same one we have covered with HubSpot's Smart Deal Progression and Salesforce's Agentforce: does it write to the record on its own, or does a human stay in the loop?

Pipedrive built Nova on the same approve-before-write model HubSpot chose. According to Pipedrive's own materials, Nova places each suggested field change next to the deal's current value and waits for a rep to approve, edit, or skip it individually. Nothing saves automatically. The company's language for this is blunt: approve, edit, or skip every CRM update before it reaches your pipeline. The suggestions are also scoped tightly, drawing only from the meeting transcript rather than reaching into other data sources to infer a change.

This is the detail worth checking before you roll any AI notetaker out broadly, not just Nova. If you are evaluating multiple tools in this category, including AI SDR platforms that touch pipeline data at a much higher volume, the same question applies every time: does it ask before it writes, and what happens the one time it gets it wrong while nobody is watching.

What an Independent Review Actually Found

Marketing copy from any vendor is marketing copy. The more useful signal is what happens when someone outside the company tests it.

A hands-on review published by tl;dv in October 2026 reported that Nova's meeting summaries held up well, but that its suggested CRM field updates were noticeably weaker, and recommended treating those suggestions as drafts rather than something to approve on autopilot. The same review flagged a smaller but telling detail: in one test, a customer's name showed up in the CRM under the rep's own Google account name, a side effect of how the call was joined rather than a transcription error. It is worth noting, in the interest of being as skeptical of this review as we are asking you to be of Pipedrive's own claims, that tl;dv is itself a Pipedrive partner, which the reviewer disclosed. That does not make the finding wrong. It is a reason to treat it as one useful data point rather than the final word, and to run your own small test before standardizing on Nova for your team.

That same review also surfaced a setting worth checking immediately if your team sells into regulated or consent-sensitive regions: Nova's guest-notice setting, which is supposed to tell meeting participants a call is being transcribed, defaults to "no automatic alerts." Pipedrive's support documentation describes the capability to notify guests and let them decline, but a default that is off means nobody is told unless you turn it on yourself. If any of your calls touch a two-party consent state, or buyers in the UK or EU, this is the first setting to check, not an afterthought. We covered the broader version of this problem, including which US states require every participant's consent before a call can legally be recorded, in AI notetaker consent risk.

A Rollout Status Conflict Worth Resolving Before You Rely On It

Here is something that will not show up in Pipedrive's own announcement, but matters practically: coverage of Nova is not consistent about whether it is actually generally available. Pipedrive's newsroom and outlets like SiliconANGLE reported the September 16, 2026 date as a general-availability launch. At least one other outlet, Let's Data Science, reported that Pipedrive's own beta-program page listed Nova among its current beta features, which is a direct contradiction of the GA framing.

The practical takeaway is not that one source is lying. It is that a staged rollout across plan tiers, regions, or account types can produce exactly this kind of conflicting coverage, where the press release describes the destination and the product's own internal status page still describes where a given account actually sits. Before you plan a team rollout around Nova, confirm what your specific account has access to rather than trusting either the announcement or a single third-party article.

What To Check Before Turning Nova On For Your Team

If you run Pipedrive and are deciding whether to enable Nova broadly, a short checklist beats a company-wide announcement:

1. Confirm your account's actual status. Check whether Nova is active on your plan and whether seats need to be assigned individually, rather than assuming it is live because you read about the GA launch.
2. Pick a notetaking mode deliberately. Decide whether the visible AI Notetaker or the audio-only Companion app fits your client relationships better, since a visible bot joining every sales call is a choice, not a default you should leave unexamined.
3. Fix the guest-notice default first. Turn on participant notification before any call touches a consent-sensitive region, and confirm your approach matches your state or country's actual recording-consent rules.
4. Treat early CRM suggestions as drafts, not approvals. Have a manager spot-check a handful of Nova's suggested field updates against the actual call before trusting the suggestions team-wide, especially for fields like deal value and close date that flow straight into your forecast.
5. Decide what "approved" actually means on your team. An approve-before-write design only protects your data if reps genuinely read each suggestion before clicking approve. A rep who rubber-stamps every suggestion to clear a notification queue has recreated the exact problem the approval step was built to prevent.

That last point is the one that determines whether Nova, or any tool like it, actually improves your pipeline coverage numbers or just moves the same risk from "nobody updates the CRM" to "somebody updates the CRM without really checking." The tool changes who does the typing. It does not change whether anyone is paying attention to what gets typed.

Frequently Asked Questions

What is Pipedrive Nova?

Nova is Pipedrive's AI meeting assistant, announced as generally available on September 16, 2026, and included in all Pipedrive plans at no additional cost. It briefs a rep before a call using CRM data, emails, calendar, and recent activity, records and transcribes the conversation, and afterward drafts a summary, follow-up actions, and suggested CRM updates for the rep to review.

Does Pipedrive Nova update CRM records automatically?

No. Pipedrive's own materials describe an approve-before-write design: Nova places suggested changes, which can include deal stage, value, and expected close date, beside the current CRM values, and a rep must approve, edit, or skip each one before anything saves. Nothing writes to the record on its own.

Is Pipedrive Nova actually accurate?

Mixed, based on the limited independent testing available so far. A October 2026 hands-on review from tl;dv found Nova's meeting summaries strong but its suggested CRM updates weaker, and recommended treating those suggestions as drafts rather than finished updates. That reviewer also disclosed a conflict of interest, since tl;dv is a Pipedrive partner, which is a reason to keep verifying rather than take any single review as the final word.

Is Pipedrive Nova generally available or still in beta?

Sources disagree. Pipedrive's newsroom and trade press covered Nova as a September 16, 2026 general-availability launch, but at least one outlet reported that Pipedrive's own beta-program page listed Nova among its current beta features. Confirm your account's actual access and rollout status rather than assuming either report applies to you.

Does Pipedrive Nova record sales calls without consent?

Pipedrive's support documentation says Nova can notify meeting participants that a call will be transcribed and let them decline. One hands-on review reported that the guest-notice setting defaults to off, so teams in two-party consent states or the UK and EU should check and change that default before rolling Nova out broadly, rather than assume consent is being requested automatically.