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

# Follow-Ups Queue

> An inbox of work that needs your attention — surfaces every contact, account, and opportunity that hit a signal worth acting on.

<div
  style={{
background: "linear-gradient(135deg, #143D4E 0%, #1C758A 55%, #30C8CA 100%)",
borderRadius: "24px",
padding: "28px",
marginBottom: "28px",
color: "#FFFFFF",
boxShadow: "0 20px 50px rgba(20, 61, 78, 0.22)",
position: "relative",
overflow: "hidden",
border: "1px solid rgba(255,255,255,0.08)"
}}
>
  <div
    style={{
position: "absolute",
top: "-36px",
right: "-36px",
width: "170px",
height: "170px",
background: "rgba(255,255,255,0.08)",
borderRadius: "999px"
}}
  />

  <div
    style={{
position: "absolute",
bottom: "-48px",
left: "-24px",
width: "130px",
height: "130px",
background: "rgba(255,255,255,0.06)",
borderRadius: "999px"
}}
  />

  <div
    style={{
  display: "inline-flex",
  alignItems: "center",
  background: "rgba(255,255,255,0.14)",
  color: "#FFFFFF",
  padding: "7px 14px",
  borderRadius: "999px",
  fontSize: "12px",
  fontWeight: "700",
  marginBottom: "12px",
  letterSpacing: "0.08em",
  textTransform: "uppercase"
}}
  >
    FOLLOW-UPS
  </div>

  <p style={{ margin: 0, fontSize: "16px", lineHeight: "1.9", maxWidth: "760px", color: "#FFFFFF" }}>
    Follow-Ups is your daily action queue — every signal worth acting on across the workspace, lined up in one inbox so nothing slips by.
  </p>
</div>

## What Lands in the Queue

ParsaLink watches for signals across the CRM and writes a Follow-Up item whenever something deserves human attention. Out of the box that includes:

* A contact you emailed who replied
* A contact you reached out to who's gone silent past your follow-up threshold
* An opportunity that hasn't moved stage in N days
* A proposal that was viewed but didn't get a response
* An account whose primary contact bounced or unsubscribed

Each item carries the underlying entity (contact, account, opportunity), the signal that surfaced it, a relative timestamp, and a one-line summary so you can triage without opening detail pages.

***

## Triaging an Item

For every item you can:

* **Snooze** — push it forward by a few days so it resurfaces later (handy for "ask again next week" follow-ups).
* **Done** — mark the action taken and dismiss it.
* **Open** — jump to the contact / account / opportunity to take action there.

Snoozed items reappear automatically. Done items are filed away but still searchable.

<Tip>
  The queue lives at **CRM → Follow-Ups**. Pin it as your daily landing page if it's where you start the morning.
</Tip>

***

## Signal Settings

Different teams have different definitions of "too quiet". Tune which signals fire and how aggressive they are at **Settings → Follow-Ups**.

Toggles include:

* Email reply received
* No-activity threshold (days of silence before a contact surfaces)
* Opportunity stuck-in-stage threshold
* Proposal viewed but no reply
* Bounce / unsubscribe surfaced for ownership review

Each signal can be turned off individually — useful if you already have an [Automation](/automations/overview) handling that case end-to-end and don't want the duplicate inbox item.

***

## Follow-Ups vs Automations

The two systems overlap but solve different problems:

* **[Automations](/automations/overview)** run unattended. They send an email, change a stage, create a task without a human in the loop.
* **Follow-Ups** keep a human in the loop. They surface signals so *you* decide what to do.

A common pattern is to use Automations for the obvious cases (auto-acknowledge an inbound email, round-robin assign a new lead) and Follow-Ups for the judgment calls (an opportunity that's lingered in Proposal stage for two weeks needs you to decide whether to push or let it die).