Skip to main content
Intempt
Coming soon

Set up your meeting types

Organizes calls with the notetaker's built in All, My, and Shared views so downstream summaries and reporting pull from the right call set.

Authored by Sid Chaudhary

Founder & CEO at Intempt

Agentic workflow

Coming soon

6 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Audit the types you have

    Coming soon

    Blu builds a step

  2. 2

    Create the Discovery type

    Coming soon

    Blu builds a step

  3. 3

    Create the Demo type

    Coming soon

    Blu builds a step

  4. 4

    Create the Proposal type

    Coming soon

    Blu builds a step

  5. 5

    Create the Renewal type

    Coming soon

    Blu builds a step

  6. 6

    Create the Check-in type

    Coming soon

    Blu builds a step

About this recipe

When to use it

Coaching, summaries, and reporting recipes all need to know what kind of call they're looking at. This establishes one clean meeting-type catalog, Discovery, Demo, Proposal, Close, Onboarding, QBR, Renewal, Customer Success, Internal, so nothing downstream has to guess.

What it delivers

Establishes a clean, standardized meeting-type catalog so every downstream recipe (summaries, coaching, reporting) can target the right call type without ambiguity.

How you prompt this

Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.

Tell Blu Agent what you want

“Organizes calls with the notetaker's built in All, My, and Shared views so downstream summaries and reporting pull from the right call set.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.

Outputs

    How the recipe runs

    Blu follows the steps in order and shows you each one before anything goes live.

    1. 01Audit the types you haveList current meeting types in the project. For each existing type, classify: KEEP (clearly defined, distinct purpose, sufficient volume to justify), MERGE (overlaps with another type: e.g. 'product walkthrough' and 'demo' usually merge), RETIRE (dead type, no meetings booked in 90 days), or RENAME (purpose is right but name is unclear).
    2. 02Create the Discovery typeCreate or update the 'Discovery' meeting type. Default duration: 30 min. Booking link visibility: prospects who haven't yet seen a demo. Required outcome on completion: champion identified, pain confirmed, current solution noted, timeline established, budget signal captured. Default notetaker autojoin: ON. Skip creation if a clean equivalent already exists (use the audit output). Use the result of "Audit the types you have".
    3. 03Create the Demo typeCreate or update the 'Demo' meeting type. Default duration: 45 min. Booking link visibility: prospects who have completed discovery (or self-served past the qualifying threshold). Required outcome: features demonstrated logged, technical questions captured, objections logged, next-step proposed. Default notetaker autojoin: ON. Skip if a clean equivalent exists. Use the result of "Audit the types you have", "Create the Discovery type".
    4. 04Create the Proposal typeCreate or update the 'Proposal' meeting type. Default duration: 30 min. Booking link visibility: opportunities at proposal stage. Required outcome: pricing structure confirmed, contract questions captured, decision-maker presence verified, expected close date. Default notetaker autojoin: ON. Use the result of "Audit the types you have", "Create the Demo type".
    5. 05Create the Renewal typeCreate or update the 'Renewal' meeting type. Default duration: 30 min. Booking link visibility: existing customers within 90 days of contract end. Required outcome: usage health confirmed, stakeholder confirmation, expansion/contraction signals, contract terms discussion. Default notetaker autojoin: ON. Use the result of "Audit the types you have", "Create the Proposal type".
    6. 06Create the Check-in typeCreate or update the 'Customer Success Check-in' meeting type. Default duration: 30 min. Booking link visibility: existing customers; reachable from in-app help center. Required outcome: usage patterns discussed, blockers captured, expansion opportunities noted. Default notetaker autojoin: ON. Use the result of "Audit the types you have", "Create the Renewal type".

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /meeting-types-taxonomy in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    More recipes by Sid Chaudhary

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe