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

# Follow-ups

> Track what you promised a lead, and whether it actually happened.

A follow-up records what needs to happen next with a lead and whether anyone did it. Action items extracted from a [meeting](/en/leads/meetings) become follow-ups automatically, and you can add your own.

## Where follow-ups come from

<CardGroup cols={2}>
  <Card title="From a meeting" icon="microphone">
    Analysis extracts commitments made during the conversation — "send the pricing sheet", "introduce them to the technical team" — and turns them into follow-ups without anyone taking notes.
  </Card>

  <Card title="Added manually" icon="pen">
    Anything you decide afterwards, or anything from a conversation that wasn't recorded.
  </Card>
</CardGroup>

## Working follow-ups

<Frame caption="Follow-ups live on the lead, alongside everything else about them">
  ![A lead detail screen showing captured fields and the actions available, including adding a meeting recording.](https://cdn.gettap.co/docs/images/screens/teams-lead-detail.png)
</Frame>

Open a lead to see its follow-ups. Mark them complete as you go — that's what feeds [action completion](/en/insights/action-completion), which shows managers who is actually closing the loop and who is collecting promises.

You can attach files to a follow-up, so the thing you sent is recorded alongside the fact that you sent it.

## Follow-ups and your CRM

Action items sync to your CRM as tasks on the lead's record, so reps who live in the CRM see them without opening Tap.

<Note>
  Completing a follow-up in Tap and completing the equivalent task in your CRM are separate actions. Pick one place as the system of record for your team and be consistent — otherwise the completion numbers in insights won't reflect reality.
</Note>

## Why completion is worth tracking

The gap between "we had a great conversation" and "we did the thing we promised" is where most event pipeline dies. Follow-up completion makes that gap visible at the point where it can still be fixed.

<Tip>
  A rep with high capture volume and low completion isn't lazy — they're usually overloaded. Reading the two numbers together tells you whether to coach or to redistribute.
</Tip>

<Card title="See it across the team" icon="chart-line" href="/en/insights/action-completion">
  Action completion in insights.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.