> ## Documentation Index
> Fetch the complete documentation index at: https://docs.piperai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Meeting Types: Configure Piper for Every Conversation

> Define templates, scoring, CRM fields, and AutoSync behavior for every kind of call — demos, discovery, QBRs, onboarding, and more.

Meeting Types are the foundation of a well-configured Piper workspace. Each Meeting Type represents a distinct kind of conversation — a product demo, a discovery call, a QBR, an onboarding session — and tells Piper exactly what to generate, analyze, and extract after every call of that type. Getting your Meeting Types right means every rep automatically gets the right notes template, the right scoring rubric, and the right CRM fields filled in without any manual work.

Navigate to **Settings → Meeting Types** to view, edit, or create Meeting Types.

## Create a New Meeting Type

<Steps>
  <Step title="Open Meeting Types">
    Go to **Settings → Meeting Types** and click **Create Meeting Type**.
  </Step>

  <Step title="Name the Meeting Type">
    Enter a clear, descriptive name (e.g., `Demo`, `Discovery`, `QBR`, `Customer Onboarding`). This name appears throughout Piper and in your CRM records.
  </Step>

  <Step title="Configure each component">
    Work through the component sections below — Notes, Email, Call Scoring, Fields, Languages, Sharing, Tags, AutoSync, Zapier, and Bot Deactivation — to tailor Piper's behavior for this call type.
  </Step>

  <Step title="Save and assign">
    Save the Meeting Type, then set up auto-assignment rules so Piper routes the right calls to it automatically (see [Auto-Assignment](#auto-assignment) below).
  </Step>
</Steps>

## Configurable Components

Each Meeting Type exposes the following components. Expand any section to learn what it controls and how to configure it.

<Accordion title="Notes — Summary Template & Prompts">
  The Notes component controls the structure and content of the meeting summary Piper generates after each call.

  You have two modes to choose from:

  **Custom Notes Template** — You define the structure: sections, headings, and specific prompts that tell Piper what to capture. Use this when you need a consistent, opinionated format (e.g., "Pain Points", "Next Steps", "Budget Discussed").

  **Piper Auto Notes** — Piper generates a full narrative summary automatically without a predefined template. This works best when you have detailed CRM Fields configured for structured data extraction, leaving Auto Notes to handle the prose summary on the Notes tab.

  <Tip>
    If you've configured several CRM Fields to extract structured data, consider using Piper Auto Notes for the Notes tab. The fields handle structured extraction; Auto Notes handles the narrative — together they give you the best of both.
  </Tip>
</Accordion>

<Accordion title="Email — Auto Follow-Up Structure & Prompts">
  The Email component defines the structure and tone of the follow-up email Piper drafts after each call. Configure section prompts to specify what the email should cover — a summary of what was discussed, agreed next steps, resources mentioned, or anything else relevant to this call type.

  Piper generates the draft automatically; reps review and send from the Transcription page. The goal is a ready-to-send email that requires only a quick read-through, not a rewrite.
</Accordion>

<Accordion title="Call Scoring — Playbook & Scorecard">
  Assign a specific playbook or scorecard to this Meeting Type. Piper uses the scorecard to evaluate each call against your methodology — whether that's MEDDIC, SPIN, a custom framework, or any other structured approach.

  Scored calls surface coaching insights and trend data across your team, so managers can see which reps are following the playbook and where gaps exist.

  <Tip>
    To also write a call's score directly into your CRM, map it to a numeric field under **Settings → Meeting Types →  Call Scoring → Numerical CRM Fields**. Once configured, Piper writes the live score to that field after every scored call — independent of the standard AutoSync categories (Notes, CRM Fields, Logged Meetings & Calls).
  </Tip>
</Accordion>

<Accordion title="Fields — CRM Data Extraction & AutoSync">
  The Fields component controls which CRM data points Piper extracts from the conversation and whether it pushes them to your CRM automatically.

  To enable Fields generation:

  1. Navigate to **Settings → Meeting Types → \[your type] → Fields**.
  2. Toggle on each field you want Piper to extract.
  3. Enable **AutoSync** per field to push values to your CRM after every call, or leave it off to hold values for manual review.

  <Note>
    Piper never overwrites an existing CRM value by replacing it outright. When writing a field, Piper combines the current CRM value, your configured prompt, and the transcription — so context is always preserved, not lost.
  </Note>
</Accordion>

<Accordion title="Languages — Output Language">
  Set the language Piper uses when generating notes, emails, and other content for this Meeting Type. This is especially useful if your team runs calls in multiple languages or if specific meeting types (e.g., regional QBRs) are always conducted in a particular language.

  Supported output languages: **English, Spanish, French, German, Portuguese, Italian, and Finnish.**
</Accordion>

<Accordion title="Sharing — Visibility Inside Piper">
  Control who can see transcriptions of this Meeting Type inside Piper — **Private**, **Piper Admins Only**, or **Internal at Piper** (see [Data Privacy](/security/data-privacy#transcription-sharing-controls) for what each level means). For recurring internal meetings — like 1:1s or staff syncs — admins can configure the Meeting Type so that transcriptions are always Private, preventing broader visibility across the workspace. Sharing a transcription externally via link is a separate, independent toggle.

  Standard users can adjust sharing settings on transcriptions they own. Admins can adjust sharing on any transcription they have access to.
</Accordion>

<Accordion title="Tags — Filtering & Organization">
  Attach tags to a Meeting Type to make transcriptions easy to find and filter. Tags flow through to every call assigned to this type, so you can quickly pull up all `Demo` calls, all `Churn Risk` calls, or any other segment you care about.
</Accordion>

<Accordion title="AutoSync — When Content Pushes to CRM">
  The **Fields Auto-Sync** toggle controls whether Piper pushes updates to your CRM automatically after each call or holds them for your review.

  There are three AutoSync types:

  * **Notes** — The meeting summary pushed to your CRM contact, company, or deal records.
  * **CRM Fields** — Structured field values extracted from the transcript.
  * **Logged Meetings & Calls** — The meeting record itself (attendees, duration, outcome) logged in your CRM.

  When AutoSync is **off**, Piper holds all proposed updates in review mode. Open the Transcription page to see what Piper would write, then approve individual updates using the green arrow button next to each field.
</Accordion>

<Accordion title="Zapier — Send Data to External Apps">
  Enable a dedicated API key for this Meeting Type to trigger Zapier workflows whenever a call of this type is processed. You can generate multiple API keys — one per team or flow — to route data to different Zaps.

  See [Settings → Integrations → Zapier](/settings/integrations) for instructions on generating API keys and installing the Piper app in Zapier.
</Accordion>

<Accordion title="Bot Deactivation Rules — Skip Certain Meetings">
  Define rules that tell Piper's recording bot to skip specific meetings of this type. You can exclude meetings by:

  * **Keywords in the title** — e.g., `Lunch`, `☕️`, `Internal Sync`
  * **Email patterns** — Any keyword containing `@` is treated as an email domain pattern. If any attendee's email matches, the bot skips the meeting (e.g., `@partner-agency.com`).

  These rules work alongside the global bot deactivation rules in [Settings → Recording](/settings/recording-bot).
</Accordion>

## Auto-Assignment

Piper assigns a Meeting Type to each call automatically. It works through three layers, in order:

<Steps>
  <Step title="Keyword matching on the meeting title">
    You specify keywords that, when found in the meeting title, assign a particular Meeting Type. For example, the keyword `demo` maps to your `Demo` Meeting Type; `onboarding` maps to `Customer Onboarding`.

    Set this up under **Settings → Meeting Types → \[type] → Automatic Meeting Types** and add your keywords.
  </Step>

  <Step title="Team Setup defaults by job role">
    For each job role in your organization (SDRs, AEs, CSMs, etc.), you can configure default Meeting Types per call modality — Video Calls, Phone Calls, Audio Uploads, and Agent meetings.

    Configure this under **Settings → Users & Teams → Team Setup**. Every rep in a given role automatically gets the right defaults without any per-user configuration.
  </Step>

  <Step title="Call type fallback defaults">
    If neither a keyword match nor a role-based default applies, Piper falls back to a global default for each call modality: all video calls, all phone calls, or all audio uploads. Set these fallbacks in **Settings → Meeting Types**.
  </Step>
</Steps>

<Tip>
  Start with keyword matching for your highest-volume call types (demos, discovery, QBRs). Then use Team Setup to ensure each role's default covers everything that doesn't match a keyword. The fallback default acts as a safety net for anything that slips through.
</Tip>

<Note>
  Keyword matching on the title only applies to video calls. For phone calls — including Aircall — Piper skips straight to the Team Setup default for Phone Calls, then the global Phone Call fallback, unless an Aircall tag already assigned a Meeting Type when the call came in (see below).
</Note>

## Aircall Integration: Assign by Tag

If you use Aircall, Piper can assign a Meeting Type automatically based on the call's Aircall tag — there's no separate mapping screen to configure. Piper checks each tag on the call against your Meeting Type names: if a tag's name matches an existing Meeting Type's name (case-insensitive), that Meeting Type is assigned immediately, before any of the Auto-Assignment steps above run.

For example, naming an Aircall tag `Support` the same as your `Support` Meeting Type routes those calls automatically — just make sure the names match exactly.

<Note>
  A matching Aircall tag always takes priority over keyword matching, Team Setup defaults, and the fallback default. Piper does not analyze the conversation itself to override a tag-based match.
</Note>