Skip to main content
Intempt

Set notetaker coverage rules once, stop toggling it per meeting

Manually deciding per-meeting whether the notetaker should join doesn't scale, and it always misses the meeting that mattered. This configures auto-join rules by meeting type, host seniority, deal stage, and account tier, once.

Sellmeeting-notetakerB2BSaaSStandard3 steps3 outputs
1
2
3
Meeting Type Inventory Notetaker Config Dashboard
Run this recipe

What it does

Configures which meetings the Blu notetaker auto-joins based on meeting type, host seniority, deal stage, and account tier, replacing per-meeting toggles with standing rules.

You get

an automated notetaker coverage policy

How it works

1

Audit Current Meeting Types

list_meeting_types

List all configured meeting types in the project. For each, surface: name, default duration, current notetaker auto-join setting, and meetings-per-month count over the last 90 days. This is the baseline for designing coverage rules — types with high volume and high revenue impact (demo, discovery, close, renewal) should have autojoin on; types with low strategic value (internal sync, recurring 1:1) likely shouldn't.

Produces:Meeting Type Inventory
2

Configure Autojoin Rules

configure_notetaker_autojoin

Configure notetaker autojoin rules based on the meeting-type audit. Default policy: ON for Discovery, Demo, Proposal, Close, Renewal, and Customer Success calls; OFF for Internal Sync, 1:1, Recurring Standup, Interview. Layer on overrides: ON for any meeting linked to a deal with value > $50K regardless of type; OFF if any attendee has notetaker-opt-out flag. Hosts can manually override per-meeting via add_blu_to_live_meeting or the meeting record toggle.

Produces:Notetaker Config
3

Build Coverage Dashboard

Build Dashboard

Compose a notetaker coverage dashboard: % of meetings with notetaker present (target: 80%+ for revenue-impacting types), coverage broken down by meeting type and rep, failed-join count (notetaker invited but didn't join — usually a calendar permission issue), and manual-add count (hosts having to invite Blu manually — signal of misconfigured rules). Flag any type with <60% coverage as a configuration gap.

Produces:Dashboard

Ready to run this recipe?

Tell Blu what you need. It builds the segment, content, journey, and dashboard in minutes.

Sign up free

Hire the team that reclaims what your GTM stack is leaking.

You set the strategy. Agents run the plays. Seven AI agents across design, marketing, sales, and analytics. One customer context, tracked from first pixel to final dollar.

Start for free
Notetaker Coverage Setup | Intempt