Skip to main content
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.
Start with Test agent while refining the conversation. Use Test campaign when you’re ready to check the complete setup.
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.

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 for the campaign setup checklist.

If Test campaign asks a question first

Test campaign can ask you one or two questions before it places a call. Nothing is written until you answer: no test run, no tag, no call.
  • The campaign has no speed to lead step, only power dialer calls. Choose to be called now, or to be queued into the campaign so the power dialer calls you on its schedule.
  • The calling window does not allow a call right now. The dialog shows the time in the zone the campaign judges the window in. Choose to be called now anyway, or to let the call wait for the window.
In the API, the response carries needsDecision with kind set to no_speed_to_lead or calling_window, asked in that order. Send the same request again with callNow or overrideCallingWindow as the answer. forceCall answers both at once and also dials over a call already in progress with the number.

If the number has an opt-out

A stop on the number never blocks a test. Before it dials, Test campaign lifts every stop on the contact:
  • the do-not-call list
  • the kill switch and opt-out tags
  • the campaign’s own stop tags
  • Do Not Disturb
  • the native Do not call switch
Test agent and share links lift every stop that would block their call. A stop the person asked for is lifted too, so real campaigns can call them again. The do-not-call list keeps a record of who lifted it. Do Not Disturb comes off for calls and texts only. Email and other channels stay as they are. If a stop does not come off, the test does not start. The answer is TEST_STOPS_NOT_CLEARED, or TFU_LIVE_TEST_STOPS_NOT_CLEARED for a TFU Live agent. Run the test again. GoHighLevel can hold a channel at permanent Do Not Disturb, for example after the person texts STOP. Only the person can lift it, by texting START. Texts to them do not send. If the call channel is held that way, the test cannot call the number. The answer is TEST_CALL_DND_PERMANENT, or TFU_LIVE_TEST_CALL_DND_PERMANENT for a TFU Live agent.

Afterwards

The result appears in run history once the call has been processed, with the outcome and whether the post-call actions ran.

In the API