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

# Testing and sharing

> Choose a test channel, inspect the result and share the agent without changing your live campaign.

The builder chat helps you configure the agent. The voice test lets you speak
with the configured voice agent. These are two different conversations.

## Choose a test channel

* **Phone test:** use [Test calls](/campaigns/test-calls) to place a call to your
  chosen test number and inspect its status.
* **Web test:** speak with the voice agent in a browser. Microphone permission
  is required.
* **Shareable form or widget:** let someone else try the configured agent from
  a full-page form or an embedded widget.

Open **Test** on the selected agent and copy its share link or embed code.
Check that you have selected the campaign you want the other person to try.

## Collect business fields

The **Collect business fields** switch adds optional business questions to the
shareable test forms. It is a campaign setting and does not rewrite the agent's
script or calendar selection.

Ask the chatbot to enable or disable that setting explicitly. It should preserve
other campaign configuration and verify the saved value.

## Embedding

Choose a full-page link, an inline frame or a floating widget. Frame placement
and size belong to the HTML you place on your website. The chatbot can explain
or draft that HTML; changing a campaign setting does not install it on a website.

An embedded voice test needs microphone permission on its iframe. Check the
published page in the browser where it will be used.

## Check before launch

Test the opening, the main capability, a refusal, a callback request and a
missing context value. Review what was recorded and whether it matches the
conversation. Testing and sharing do not themselves activate the campaign.
Use [Going live](/campaigns/going-live) to check readiness and activate deliberately.

## In the API

* [Create web agent session](/api-reference/agents/create-web-agent-session) is the browser test
* [Create test call](/api-reference/agents/create-test-call) is the phone test
* [Update campaign](/api-reference/campaigns/update-campaign) sets `testing`, the stand-in lead fields a test uses