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

> ## Agent Instructions
> Use the public API base URL: https://api.teamfollowup.ai/api.
> Authenticate public API requests with Authorization: Bearer YOUR_API_KEY.
> Use product-owned terms: agents, campaigns, projects (GoHighLevel sub-accounts), contacts, calls, outcomes, skills, cadences, phone numbers.
> Scope requests by locationId rather than projectName.
> Read the guide linked from each API reference group before recommending an endpoint.

# Campaign settings

> Configure the campaign's trigger, calling rules and installed abilities.

A campaign connects an agent to the people it should call and the rules it should
follow. Open **Campaign settings** in Agent Builder to adjust the selected campaign.

## Find the setting you need

<CardGroup cols={2}>
  <Card title="Audience and triggers" icon="users" href="/campaigns/audience">
    Understand how people enter each campaign and configure its trigger.
  </Card>

  <Card title="Calling hours" icon="clock" href="/campaigns/calling-window">
    Set permitted hours and decide which timezone they follow.
  </Card>

  <Card title="After-hours coverage" icon="moon" href="/campaigns/after-hours">
    Decide when the AI should cover calls outside your team's working hours.
  </Card>

  <Card title="Caller ID" icon="phone" href="/campaigns/phone-numbers">
    Choose the number people see when the campaign calls.
  </Card>
</CardGroup>

## Booking and transfer resources

Each setting belongs to the part of the campaign that uses it:

| Setting | Where it belongs | Applies to |
| - | - | - |
| Entry and exclusion tags | Outbound trigger | Outbound campaigns |
| Calendar that starts confirmation calls | Appointment trigger | Confirmation campaigns |
| Calendar used to offer a new appointment | Appointment Booking capability | Outbound and inbound campaigns with booking installed |
| Transfer destination and routing | Live Transfer capability | Campaigns with transfer installed |
| Immediate calls and scheduled follow-up | Calling rules | Outbound and confirmation campaigns |

An inbound campaign starts when someone calls its number. It has no outbound
entry tags or dialing schedule. Confirmation campaigns start from a booked appointment;
their rescheduling currently uses the same calendar selected on the trigger.

Open [Appointment Booking](/skills/booking) to choose a booking calendar, or
[Live Transfer](/skills/transfers) to configure a handoff. A campaign type does
not prove an ability is installed. The **Skills & Tools** panel shows the actual inventory.

Advanced routing can select different calendars or transfer destinations based
on what is known about the lead. Review the existing routing rules before changing
the default resource.

## Keep related changes together

The campaign's active switch controls whether it is enabled. Tags, calling hours,
caller ID and resource choices all contribute to whether it is ready to call.
Review [Going live](/campaigns/going-live) before enabling it.

Use [Power Dialer](/campaigns/power-dialer) for attempt schedules and the queue,
[follow-up workflows](/campaigns/after-the-call) for what happens after a call,
and the agent's [script](/agents/prompt) or [audio settings](/agents/delivery) for
the conversation itself.

## Call results

Edit detection wording on the campaign’s [outcome cards](/agents/outcomes).
Use [Detectors](/campaigns/detectors) for an additional yes-or-no condition, and
[Follow-up workflows](/campaigns/after-the-call) for what should happen afterward.

## In the API

* [Get campaign](/api-reference/campaigns/get-campaign) reads every setting on this page
* [Update campaign](/api-reference/campaigns/update-campaign) changes the `trigger`, the `calling` rules and the installed `capabilities`; its `actionResults` reports each block as `saved` or `unchanged`