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

# Campaigns: Automated Lead Outreach for Real Estate Agents

> A Campaign runs continuous automated outreach for a defined group of contacts. Learn how to create, manage, pause, and stop campaigns in AgentNode.

A campaign is an automated job that runs for a set of contacts. You tell AgentNode what you want it to do and who it should run for, and the campaign keeps doing it — for the contacts it names, and for anyone added later — until you stop it. Think of it as a standing instruction: set it once, and AgentNode handles the ongoing outreach while you focus on the conversations that need you.

<Info>
  **Example:** Past clients — check in with each of them every three months.
</Info>

## Creating a campaign

<Steps>
  <Step title="Open New Campaign">
    Click **New campaign** from the Inbox or Contacts page.
  </Step>

  <Step title="Describe what you want AgentNode to do">
    Type your instruction in plain language — for example, "Check in with past clients every 3 months" or "Follow up with cold leads who haven't responded in 60 days."
  </Step>

  <Step title="Choose who it runs for">
    Select individual contacts or a tag group. The campaign will run for every contact in that selection.
  </Step>

  <Step title="Answer any follow-up questions">
    The campaign opens on its chat and asks for anything else it needs to get started — for example, birthdays if you want personalised anniversary messages.
  </Step>

  <Step title="The campaign starts running">
    Once you've answered its questions, the campaign begins automatically. No further action is needed.
  </Step>
</Steps>

## The campaign workspace

Each campaign has four tabs that give you a full picture of what's happening.

| Tab | What It Shows |
| - | - |
| Overview | What you asked for and how it's going: who's on it, what it sent, who replied, who booked. |
| Recent Messages | The texts it has sent and the replies it has received. |
| Contacts | Who is on it, and who it removed and why. |
| Context | Its files, and the live sources it can look things up in. |

The campaign's chat is always beside these tabs. Tell it to change course there — update its tone, shift its focus, or give it new information to work with.

A campaign never texts anyone itself. Each contact's [weave](/weave) takes every campaign they are on and turns them into one conversation, so a person on three campaigns still gets one natural thread of texts.

## Adjusting a campaign

You don't need to stop a campaign to change how it behaves. Use the campaign chat to update its instructions at any time — mid-flight. Tell it to message less frequently, adopt a warmer tone, or start asking leads a different question. The campaign picks up your new instructions and applies them going forward without interrupting conversations already in progress.

## Pausing and stopping

<Tabs>
  <Tab title="Pause">
    Pausing a campaign puts it on hold. Nothing more is sent until you resume it. All contacts stay on the campaign and their conversation history is preserved. Use pause when you need a break — for example, over a holiday period — and plan to pick things back up.
  </Tab>

  <Tab title="Stop">
    Stopping a campaign ends it entirely. Contacts on the campaign will not be messaged again unless you add them to a new campaign. Use stop when the campaign's goal has been met or it's no longer relevant.
  </Tab>
</Tabs>

<Note>
  A campaign never messages someone who has opted out, regardless of whether the campaign is active or was paused and resumed.
</Note>

## Adding contacts to a running campaign

You don't need to stop or restart a campaign to include new contacts. Any contacts you add after a campaign is already running are automatically picked up and included in the outreach. This means a tag-based campaign grows naturally as you add new contacts with that tag.

<Tip>
  Use the campaign chat to refine your instructions over time. The more context you give, the more personalised the outreach.
</Tip>


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