Skip to main content
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 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. For TFU Live, open Test and turn on Collect business fields. Use Choose fields to hide individual questions. The available questions follow the saved Brain and Voice prompt and the connected CRM’s fields; nothing is specific to a business or niche. Name and phone remain the main inputs. Extra questions sit under Personalize this test (optional) on the shared form. Up to eight extra fields appear, in prompt order. Hidden fields do not count toward that limit, and turning the main switch off hides all extra questions. Hiding a field does not remove it from the prompt or clear its existing value. Supported GHL standard fields are City, State, Country, Postal code, Street address, Company name and Website, alongside text-like custom fields. lead_city can use standard City when no custom field of that name exists. Identity, call-routing and system variables are not extra form questions. A TFU Live Test agent form offers Business Name only when the prompt uses it. All its answers personalise only that simulated test conversation and do not change the contact’s saved fields. The Test campaign form saves the visible standard and custom fields on its test contact before running the real campaign. Its browser link still accepts only a contact created by a test link, or a new number. Blank answers leave existing values unchanged. You can also ask the chatbot to enable or disable the setting. Other campaign configuration stays unchanged.

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. The widget is offered for agents that answer calls, and for every TFU Live agent that has a campaign. Before you copy its code, name the websites allowed to run it under Website widget in the campaign’s settings. Naming acme.com covers www.acme.com and every other subdomain. A website that is not on the list cannot load the widget. A widget conversation is a real voice conversation with your agent. It is billed at your call rate and listed as Web Usage. On a live, active campaign it works like a phone call to the same agent: on GoHighLevel a contact is made for the visitor, and the agent books, tags and runs its workflows for real. On a paused campaign, or with all calls stopped, it is conversation only and nothing is written to your CRM. Until the visitor gives a phone number, the agent cannot transfer them or text them. 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 to check readiness and activate deliberately.

In the API