# Follow-ups

{/* AUTO-SYNCED SOURCE: this page lives in apps/app/src/modules/db-leads/docs/ and is mirrored into the docs app by `bun sync:module-docs`. Edit it in the module, not in apps/docs. */}

<Lead>
The most common outcome of an acquisition call is neither yes nor no, it is **"not now"**. The follow-up is how you record that without losing sight of the contact.
</Lead>

## Setting one

In three places:

<DefinitionList>
  <DefItem term="In the three-dot menu">In the contact panel or the customer view, under **Follow-up**.</DefItem>
  <DefItem term="In a run-through">Through the **Later** outcome. See [Durcharbeiten](/tools/db-leads/durchgang).</DefItem>
  <DefItem term="On a finding">Instead of accepting or dismissing: defer it.</DefItem>
</DefinitionList>

Intervals: **1 week**, **1 month**, **3 months**, **6 months**, **1 year**, or a date of your choice in the calendar. A chosen date beats an interval: whoever opens the calendar has a specific day in mind.

## It creates a real task

A follow-up is not a note inside a tool, it is a task carrying the contact's name:

<Checklist>
  <ChecklistItem>It appears under **Tasks** in the platform.</ChecklistItem>
  <ChecklistItem>It appears in **onOffice**, if the contact comes from there.</ChecklistItem>
  <ChecklistItem>On the due date a **notification** goes out: to the assignee, otherwise to the workspace owner.</ChecklistItem>
</Checklist>

<Tip title="Why in the morning">
The reminder is scheduled for the morning, not for midnight. A reminder arriving at night has already slipped down the list by morning and carries a "yesterday" stamp.
</Tip>

## The "Follow-ups" view

The tab shows all deferred contacts grouped into **overdue**, **today**, **this week** and **later**. A click opens the contact.

<Callout tone="note" title="Ticking off is deliberately not possible here">
It is the same task that also appears under Tasks and in onOffice. If you could complete it in three places, you could also complete it differently in three places. It is set on the contact and completed under Tasks or in onOffice.
</Callout>

## Rescheduling works everywhere

Change the due date under Tasks or in onOffice and shortly afterwards DB-Leads shows the same date, with the reminder rescheduled. There is only one date, no matter where you touch it.

## Follow-up or exclude from scan?

Two different things, and confusing them costs you a contact:

<DefinitionList>
  <DefItem term="Follow-up">"Interesting, but later." The contact stays fully in play and keeps being analysed.</DefItem>
  <DefItem term="Exclude from scan">"This person has repeatedly made clear they are not selling." The contact stays in list and board but is no longer analysed and no longer proposed. Reversible at any time.</DefItem>
</DefinitionList>

## Further reading

<CardGrid>
  <Card title="Durcharbeiten" href="/tools/db-leads/durchgang">The "Later" outcome in stack mode.</Card>
  <Card title="Customer view" href="/tools/db-leads/kundenansicht">Where the follow-up sits on the contact.</Card>
  <Card title="Rules" href="/tools/db-leads/regeln">Set follow-ups automatically.</Card>
</CardGrid>
