marketing workflow

Lead Follow-up Loop

Send relevant follow-up without inventing personalization or losing replies in a manual queue.

Setup: 25 minutes
Difficulty: Intermediate
Tested: 2026-07-26

# Lead Follow-up Loop

Research a qualified lead, draft a grounded follow-up, and route the response safely.

**Outcome:** Send relevant follow-up without inventing personalization or losing replies in a manual queue.

**Category:** marketing

**Setup:** 25 minutes · Intermediate

## Requirements

- Qualified lead record and consent basis
- Approved product facts and outreach policy

**Tools:** gumloop, zapier

## Expected output

A cited research brief, reviewed message, and reply-routing automation

## Steps

### 1. Collect source-backed context

Gather only current facts from the lead's official site and supplied record.

**Prompt**

```text
Create a lead brief with one source URL per fact. Mark assumptions as unusable for outreach.
```

### 2. Select a relevant reason to write

Connect one verified need to one approved product capability without overstating fit.

**Prompt**

```text
Draft the relevance statement in two sentences and cite the supporting lead fact and product fact.
```

### 3. Draft for human approval

Prepare one concise message and keep sending disabled until a person approves it.

**Prompt**

```text
Write a plain-language follow-up under 120 words with one CTA and no artificial familiarity.
```

### 4. Route the response

Classify replies into interested, later, unsubscribe, or manual review and log the decision.

**Prompt**

```text
Return only a routing label, confidence, and one-sentence evidence. Route low confidence to manual review.
```

## Limitations

This workflow is for qualified, permission-aware outreach and does not make unsolicited bulk messaging acceptable.

## Privacy

Minimize stored personal data, honor opt-outs immediately, and follow applicable outreach and privacy rules.

## Sources

- https://www.gumloop.com/
- https://zapier.com/

Tested 2026-07-26 · Updated 2026-07-26

# Lead Follow-up Loop

Research a qualified lead, draft a grounded follow-up, and route the response safely.

**Outcome:** Send relevant follow-up without inventing personalization or losing replies in a manual queue.

**Category:** marketing

**Setup:** 25 minutes · Intermediate

## Requirements

- Qualified lead record and consent basis
- Approved product facts and outreach policy

**Tools:** gumloop, zapier

## Expected output

A cited research brief, reviewed message, and reply-routing automation

## Steps

### 1. Collect source-backed context

Gather only current facts from the lead's official site and supplied record.

**Prompt**

```text
Create a lead brief with one source URL per fact. Mark assumptions as unusable for outreach.
```

### 2. Select a relevant reason to write

Connect one verified need to one approved product capability without overstating fit.

**Prompt**

```text
Draft the relevance statement in two sentences and cite the supporting lead fact and product fact.
```

### 3. Draft for human approval

Prepare one concise message and keep sending disabled until a person approves it.

**Prompt**

```text
Write a plain-language follow-up under 120 words with one CTA and no artificial familiarity.
```

### 4. Route the response

Classify replies into interested, later, unsubscribe, or manual review and log the decision.

**Prompt**

```text
Return only a routing label, confidence, and one-sentence evidence. Route low confidence to manual review.
```

## Limitations

This workflow is for qualified, permission-aware outreach and does not make unsolicited bulk messaging acceptable.

## Privacy

Minimize stored personal data, honor opt-outs immediately, and follow applicable outreach and privacy rules.

## Sources

- https://www.gumloop.com/
- https://zapier.com/

Tested 2026-07-26 · Updated 2026-07-26

{
  "slug": "lead-follow-up-loop",
  "title": "Lead Follow-up Loop",
  "description": "Research a qualified lead, draft a grounded follow-up, and route the response safely.",
  "outcome": "Send relevant follow-up without inventing personalization or losing replies in a manual queue.",
  "category": "marketing",
  "tags": [
    "sales",
    "follow-up",
    "automation"
  ],
  "setupMinutes": 25,
  "difficulty": "Intermediate",
  "featured": false,
  "testedAt": "2026-07-26",
  "updatedAt": "2026-07-26",
  "tools": [
    "gumloop",
    "zapier"
  ],
  "inputs": [
    "Qualified lead record and consent basis",
    "Approved product facts and outreach policy"
  ],
  "expectedOutput": "A cited research brief, reviewed message, and reply-routing automation",
  "steps": [
    {
      "title": "Collect source-backed context",
      "instruction": "Gather only current facts from the lead's official site and supplied record.",
      "prompt": "Create a lead brief with one source URL per fact. Mark assumptions as unusable for outreach."
    },
    {
      "title": "Select a relevant reason to write",
      "instruction": "Connect one verified need to one approved product capability without overstating fit.",
      "prompt": "Draft the relevance statement in two sentences and cite the supporting lead fact and product fact."
    },
    {
      "title": "Draft for human approval",
      "instruction": "Prepare one concise message and keep sending disabled until a person approves it.",
      "prompt": "Write a plain-language follow-up under 120 words with one CTA and no artificial familiarity."
    },
    {
      "title": "Route the response",
      "instruction": "Classify replies into interested, later, unsubscribe, or manual review and log the decision.",
      "prompt": "Return only a routing label, confidence, and one-sentence evidence. Route low confidence to manual review."
    }
  ],
  "limitations": "This workflow is for qualified, permission-aware outreach and does not make unsolicited bulk messaging acceptable.",
  "privacy": "Minimize stored personal data, honor opt-outs immediately, and follow applicable outreach and privacy rules.",
  "sources": [
    "https://www.gumloop.com/",
    "https://zapier.com/"
  ],
  "related": [
    "launch-copy-sprint"
  ]
}

Requirements

Bring these inputs.

Qualified lead record and consent basis
Approved product facts and outreach policy

Output contract

Know what done looks like.

A cited research brief, reviewed message, and reply-routing automation

Execution

Run the playbook.

01
Collect source-backed context
Gather only current facts from the lead's official site and supplied record.
```
Create a lead brief with one source URL per fact. Mark assumptions as unusable for outreach.
```
02
Select a relevant reason to write
Connect one verified need to one approved product capability without overstating fit.
```
Draft the relevance statement in two sentences and cite the supporting lead fact and product fact.
```
03
Draft for human approval
Prepare one concise message and keep sending disabled until a person approves it.
```
Write a plain-language follow-up under 120 words with one CTA and no artificial familiarity.
```
04
Route the response
Classify replies into interested, later, unsubscribe, or manual review and log the decision.
```
Return only a routing label, confidence, and one-sentence evidence. Route low confidence to manual review.
```

Field note

How to use this route.

The human send gate is part of the MVP workflow, not an optional safety step. Automate research and routing first; earn the right to automate sending later.

Bring these inputs.

Know what done looks like.

Run the playbook.

Collect source-backed context

Select a relevant reason to write

Draft for human approval

Route the response

How to use this route.

Keep moving through the atlas