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

# Test calls

> Choose Test agent to try the conversation, or Test campaign to check the complete campaign flow.

Open **Test** in Agent Builder. You'll see **Test agent** and **Test campaign**.
Choose based on what you want to check.

## Test agent

Use **Test agent** when you want to hear how the agent sounds and responds.
Try its greeting, ask a question, interrupt it, or see how it follows the script.

For example: “I've changed the opening line. Does it sound natural now?”

**Test agent** checks the conversation directly. It does not verify the full
campaign flow, such as lead enrolment and the follow-up actions after the call.
Follow the test dialog's instructions; for inbound agents, you dial in to talk
to the agent.

## Test campaign

Use **Test campaign** when you want to check how the conversation and the
surrounding campaign work together. It runs the campaign flow against a contact,
including the applicable entry rules, calling rules and post-call actions.

For example: “When this contact asks for information, does the campaign send
the follow-up text I've configured?”

For inbound campaigns, **Test campaign** asks you to dial in from your own phone
and checks the inbound flow. The settings being tested depend on the campaign
type; inbound campaigns do not need outbound entry tags.

<Tip>
  Start with **Test agent** while refining the conversation. Use **Test campaign**
  when you're ready to check the complete setup.
</Tip>

<Warning>
  These tests use real calls and consume minutes. **Test campaign** can also run
  configured actions, such as sending messages or updating the contact. Use your
  own test details.
</Warning>

## If Test campaign cannot start

**Test campaign** can stop before placing a call when a required setting is
missing. For example, an outbound trigger needs an entry tag, Appointment Booking
needs its calendar, and Live Transfer needs its destination.

Check the missing settings shown in the test dialog. See
[Going live](/campaigns/going-live) for the campaign setup checklist.

## Afterwards

The result appears in [run history](/campaigns/run-history) once the call has
been processed, with the outcome and whether the post-call actions ran.

## In the API

* [Create test call](/api-reference/agents/create-test-call) is Test agent: the agent phones you
* [Create campaign test run](/api-reference/campaigns/create-campaign-test-run) and [Get campaign test run status](/api-reference/campaigns/get-campaign-test-run-status) are Test campaign
* [List campaign runs](/api-reference/campaigns/list-campaign-runs) shows the result afterwards