Test a Campaign
Test the agent, then run the campaign against a short list of your own numbers before it reaches a real customer.
Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.
Test in two stages: first the agent on its own, then the whole campaign with a list of two or three of your team's numbers. A short test catches a wrong greeting, a missing field or a bad calling window before any customer hears it.
Stage 1: test the agent
The agent does the talking, so it should sound right before you attach it to a campaign.
- Sign in to the Xebit VoiceCloud dashboard at
voice.xebit.ai. - Sign in to the Xebit VoiceKit admin console on your own host.
- Open the agent the campaign will use.
- Start a test call and talk to it the way a real customer would, including the awkward answers.
Listen for:
- a clear greeting that says who is calling and why;
- the right questions, in the right order;
- the right language, including mixed language replies such as Hindi and English;
- a natural end to the call, and a handoff to a person when one is asked for.
If something is off, change the agent's instructions and test again. Agent Testing covers this in detail.
Stage 2: run a small test campaign
- Create a campaign with the same agent and dialling plan you will use for real. See Create a Campaign.
- Add only two or three contacts: your own number and a colleague's, on numbers your carrier can reach.
- Fill in the extra fields the real list will carry, so the agent uses them on the call.
- Start the campaign inside its calling window.
- Answer the calls and play the customer. Let one go unanswered to see the retry.
- Open each call's details in the dashboard or admin console and check the recording, transcript, summary and outcome.
What to check
| Check | What good looks like |
|---|---|
| Introduction | The agent says who it is and why it is calling. |
| Language | It speaks the language set for the contact or the campaign. |
| Message | It delivers the message for this campaign and uses the contact's fields correctly. |
| Caller ID | The call shows the number on your trunk you expect. |
| Outcome | The right outcome and structured fields appear against each contact. |
| Retry | The unanswered contact is tried again after the gap you set. |
| Recording and transcript | Both are there for every answered call. |
| Your systems | Webhooks arrive and Zoho or Salesforce records update, if connected. |
Fix and test again
- Wrong words or questions: change the agent's instructions.
- Wrong timing, pacing or retries: change the dialling plan.
- Wrong caller ID or calls not connecting: check your carrier and trunk. See Carrier and SIP Issues.
- Nothing arriving in your systems: see Webhook Failures or CRM Sync Errors.
Run the test list again after each change, and only start the full list when a test call sounds the way you want a customer to hear it.
Test calls are real calls over your carrier, so they are connected minutes like any other call.
Next step
Continue to Run a Campaign to start calling your full list.