Campaign will not start

Which requirements Nexcal checks at campaign start, why the start can be blocked and how to fix the cause step by step.

Last reviewed: 2026-07-22

Campaign will not start

When a campaign cannot be started, Nexcal usually points to the missing requirement. The start is deliberately blocked as long as not all required conditions are met. This prevents campaigns from running in production without a valid basis.

What Nexcal checks at start

Before a production start, Nexcal checks, among other things:

  • the workspace and the required permissions;
  • the approval of the company verification;
  • an approved, permitted caller ID;
  • the leads assigned to the campaign;
  • the campaign settings such as goal, script, knowledge and result fields;
  • the booking and runtime configuration, where relevant.

If one of these requirements is missing, the start stays blocked.

Common causes

Narrowing it down step by step

  1. Read the displayed message carefully; it usually names the specific cause.
  2. Check whether company verification and caller ID are approved.
  3. Check whether leads are assigned and the required settings are complete.
  4. Fix the stated cause and start again.

A detailed overview is available in fixing campaign start errors.

Wichtig: A campaign must not start in production before the required company verification and an approved caller ID are in place.

If the start remains blocked

If the start stays blocked even though the requirements are met, contact support. Include the workspace, the campaign and the exact message.

Back to Help Center