> ## 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.

# Find your module

> Find the part of your workspace that controls what you want to change.

Start with the part of your workspace you want to set up or understand.

| Module | The question it answers |
| - | - |
| [Agents](/agents/overview) | What should the agent say and know? |
| [In-call Capabilities](/skills/overview) | What can the agent do while someone is on the line? |
| [Campaigns](/campaigns/overview) | What starts a call, who is eligible, and what happens afterwards? |
| [Master agent](/campaigns/master-agent/overview) | How does one shared setup run across several projects? |

## Go one level deeper

In **Agents**, choose identity and settings, script and knowledge, lead context,
split testing or conversation testing. In **Campaigns**, choose settings, lead
enrolment, outcomes and workflows, or campaign testing. In **In-call Capabilities**,
choose available tools, individual skills or editing several selected skills.

## Resources used by those modules

[Phone Numbers](/campaigns/phone-numbers) supplies caller IDs.
[Voices](/agents/voice) supplies the voice catalogue.
[CRM connections](/concepts/built-on-ghl) supplies calendars, tags and lead context.
[Projects](/concepts/projects) defines the account in which a campaign runs.
[Calls](/concepts/call-history), [Contacts](/concepts/contacts) and
[Analytics](/concepts/analytics) help you inspect the results.

## Follow a task across modules

"Find out whether the caller wants a quote, then send a follow-up" has two parts:

1. In **Campaigns → Call results**, define the detector and what the person must have said.
2. In **Campaigns**, branch on that field and configure the follow-up action.

An action performed while the call is live belongs to the agent's in-call
capabilities. An action performed after the call belongs to the campaign workflow.

## Working with the builder chatbot

Ask the chatbot about a control you are looking at, or tell it what you want to
change. For example: “Make the opening friendlier, but keep the qualifying questions.”
It can explain a setting without changing it, or help you edit your setup and
check what saved.

Within **Campaigns**, [Power Dialer](/campaigns/power-dialer) brings together the
campaign's cadence, dialing options and lead queue.

## In the API

Each module has its own reference landing page: [Agents](/api-reference/agents),
[In-call Capabilities](/api-reference/skills-and-tools),
[Campaigns](/api-reference/campaigns), [Master agent](/master-agent/overview) and
[Projects](/api-reference/projects). The
[API reference overview](/api-reference/overview) lists the rest.