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.

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