# Pipedrive Nova meeting brief: customize it per deal, and feed it notes worth reading

https://salesbond.app/blog/pipedrive-nova-meeting-brief-custom-instructions/
Published: 2026-10-04 · Updated: 2026-10-04

On the Nova Meetings screen in Pipedrive, every upcoming meeting gets a brief that Nova writes from what is already on the deal: its notes and recent activity, the organization and the attendees who exist as contacts, and the email Nova reads through its own Gmail connection. The Customize brief panel on the deal overview adds your own instructions, and they apply to every future meeting linked to that deal ( [Pipedrive: Nova meetings](https://support.pipedrive.com/en/article/nova-meetings)). So write those instructions as a standing rule for the deal and revise them each time the deal moves. And when a brief looks off, check the deal record first, because the brief is a reading of it.

## Nora’s Monday brief

Monday, ten minutes before a call she inherited on Friday. Nora is covering an account for a colleague who is on leave, so she opens the Upcoming meetings tab, clicks the card and reads what Nova has prepared. The contact briefs name the IT lead and the operations manager. The deal context quotes a note from three weeks ago: “Pilot on hold until security review is done.” And the custom section, written by her colleague before the last call, says: “Push for the security review sign-off. It is the only blocker.”

So that is how she plans to open.

She checks the activity history first, out of habit, and finds Thursday’s call marked done with no description. Two minutes on the phone with her colleague settle it: the security review was signed off on Thursday, on that call. The real question now is who on the buyer’s side owns the data migration. None of that is on the deal. The instruction that would have had Nora reopen a closed question in front of the buyer is.

Nobody pasted anything into Nova here. That is the difference from prepping with a general assistant, where you pick what goes in; we wrote up that routine in [a ten-minute call prep from the deal](https://salesbond.app/blog/ai-sales-call-prep-pipedrive/). Nova reads the deal by itself, every morning, including the old note and the old instruction, and it lays both out in the same even tone as the parts that are still true.

## What goes into the brief

The help page lists four sections, each depending on the data available: deal context based on notes and recent activity, organization background if an organization brief is available, contact briefs for the attendees who exist in the CRM, and a preparation checklist highlighting recent activity ( [Pipedrive: Nova meetings](https://support.pipedrive.com/en/article/nova-meetings)).

Those are the sections. What feeds them is a different list, and it is the one you can actually do something about: the deal’s notes, its activities, the organization and contact records, and email.

Email has a catch. Even if Gmail is already synced with Pipedrive, Nova needs its own connection to the mailbox, because it reads your emails in real time to generate briefings and that takes different permissions from the standard sync ( [Pipedrive: Nova set up](https://support.pipedrive.com/en/article/nova-set-up)). A rep who skipped that step in the setup wizard gets briefs with no email context and may never notice why. The calendar is simpler: if it is already synced with Pipedrive, Nova sees the events through Pipedrive and tags them “synced via Pipedrive”. Nova only reads the calendar. It does not create, edit or delete events.

Anything outside those sources does not exist for the brief. The pricing spreadsheet on someone’s desktop, the Slack thread where the rep explained the account to a colleague, the thing the buyer said in the car park. If you want it in Monday’s brief, it has to be on the deal by Friday.

One more thing we read into “if an organization brief is available”. The organization section is conditional, so on a deal whose organization record is a bare name with no website and no notes, do not expect that section to carry the meeting.

## Customize brief: what to write, and why it outlives the meeting

There are two places to tell Nova what a brief should contain, and they work at different heights.

The account level is in Nova’s AI settings, on the Summary preferences tab. For the pre-meeting brief you can add custom instructions describing the focus, key topics or information to leave out. Those instructions apply to all future briefs and they replace Nova’s default instructions rather than adding to them ( [Pipedrive: Nova set up](https://support.pipedrive.com/en/article/nova-set-up)). If you write anything there, write the whole recipe, because a single extra line would leave you with that line and nothing else.

The deal level is the Customize brief panel on the deal overview. Free-form text, and Nova generates a custom briefing section from it for all upcoming meetings linked to that deal ( [Pipedrive: Nova meetings](https://support.pipedrive.com/en/article/nova-meetings)).

![Two levels of Nova brief instructions, account settings and the deal's Customize brief panel, both feeding the meeting brief](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-nova-meeting-brief-custom-instructions-2.png)

Our split: the account level is for how the team sells, the deal level is for what is true about this deal only. At the account level we would write things like “state the next step we promised and its date first” and “list any question from the last email thread that we have not answered”. Things that hold for every deal. The deal panel gets three or four lines, each a standing fact or rule about this account:

- the question we must ask next time (“Confirm who on their side owns the data migration before the 14th”);
- the subject not to raise (“Do not bring up the integrations roadmap, they asked us to park it until the pilot ends”);
- the known objection and our answer to it, so the brief repeats our position, not the buyer’s;
- who decides and who can block (“CEO signs; the IT lead can block on single sign-on”).

Now the part the help page states in one sentence and most teams miss: custom instructions apply to all future meetings linked to the deal, and never to a single one. The line “ask about budget” that you wrote before meeting two will still be in the brief for meeting five, after the budget was agreed in meeting three. A stale instruction is worse than no instruction. Nora’s Monday shows why.

So the panel works as the deal’s standing orders, and standing orders need someone to retire them. Our habit is to reread it while writing the post-meeting note and delete every line the the meeting answered. We also start each line with the date we wrote it, which is our convention, not a product feature, so that a line older than two meetings gets questioned by whoever reads it.

## Where did my meeting go?

Not every calendar event or Pipedrive activity is meant to show up in Nova. Four independent settings decide which ones do, under Settings > Meeting and activity syncing, in the Meeting sync rules section, and a meeting has to pass all four to appear ( [Pipedrive: Nova meetings](https://support.pipedrive.com/en/article/nova-meetings)). The help page shows the four toggles in a screenshot and names one of them in the text, the one that matters most for a sales team: Include meetings without a linked deal, person, or organization. With that setting off, the attendee’s email address has to be saved as a contact in Pipedrive, or the meeting stays out.

When you change any of these settings, Nova rechecks your upcoming meetings on its own: the ones that no longer qualify are removed, the ones that now qualify are added. Past meetings are not touched. So the fix for a missing meeting is always forward-looking and there is no point flipping a toggle to recover last week.

![Five-step checklist for finding out why a meeting is missing from Pipedrive Nova](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-nova-meeting-brief-custom-instructions-3.png)

Here is the order we go through when a rep says the Monday meeting is not in Nova:

1. No Meetings screen at all? Nova is included in every plan at no extra cost and is turned on by default for all users ( [Pipedrive: Nova set up](https://support.pipedrive.com/en/article/nova-set-up) ), but an admin can turn it off. The admin turns it back on in Settings > Manage users.
2. Look at the event title. Events titled “Home”, “Office”, “Out of office” or “Lunch” are always excluded, whatever the sync rules say. A rep who books customer lunches as “Lunch” will never see them in Nova. Put the customer’s name in teh title.
3. Check who is invited. If the setting for meetings without a linked record is off, every meeting needs an attendee whose email is a Pipedrive contact. The usual culprit is an invite that came from the buyer’s personal address, or a meeting where the only external attendee is a consultant nobody added to the CRM.
4. If the meeting is a Pipedrive activity rather than a calendar event, its activity type has to be one you selected for Nova to treat as a meeting. Newly selected types appear in Meetings, deselected ones are removed ( [Pipedrive: Nova set up](https://support.pipedrive.com/en/article/nova-set-up) ).
5. Then walk the four Meeting sync rules on the settings page with the rep. Remember the recheck only touches upcoming meetings.

If the event is not even in Pipedrive yet, the problem is a step earlier, in the calendar sync itself; we covered that in [calendar sync, meetings and activity types](https://salesbond.app/blog/pipedrive-calendar-sync-meetings-activities/).

## Ten minutes of notes that make tomorrow’s brief

Nora’s brief went wrong on Thursday, not on Monday. The fix is in the ten minutes after a call, and it is a writing problem.

If a notetaker is recording the call, the transcript is its job, and we have an opinion on how much of that should land on the deal in [what to let an AI notetaker write into Pipedrive](https://salesbond.app/blog/ai-notetaker-pipedrive-sync/). The post-meeting note is for what a person preparing the next meeting would need and could not get from a recording: who decides and who can block, what they said about money and timing in their own words, the question they asked that we did not answer, and what we promised. The promise goes in as an activity with a date rather than a sentence in the note, because the brief’s checklist highlights recent activity and an open activity is the clearest signal of a next step the brief can find.

Then the Customize brief panel, while the meeting is fresh. Delete the lines the meeting answered. Add the new objection. Change the question to ask.

It compounds. The second meeting’s brief is built from the first meeting’s note, the third from both, and a colleague who has to cover the account walks in knowing what the last person in the room knew. After the meeting, Nova also drafts CRM updates from the transcript for the rep to approve, and that is a different discipline with its own failure mode; it has [its own article](https://salesbond.app/blog/pipedrive-nova-suggested-crm-updates-review/).

A disclosure, since we are talking about what a tool can read off a deal. We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. This habit matters to us because every tool reading the deal, ours included, works with what the rep wrote down on Thursday and nothing else. If you want a second reader on your pipeline, [check your CRM with SalesBond](https://salesbond.app/).