Why campaign settings are locked after start
Why most campaign settings are locked after the start and how you can still make adjustments.
Last reviewed: 2026-07-22
Why settings are locked after the start
As soon as a campaign has started in production, most of its settings are locked. The reason is the campaign state created at start: it forms the binding basis for all of the campaign's calls. If changes were possible at any time, results could no longer be clearly attributed to a configuration.
What the lock achieves
- Consistent execution: all leads are called on the same basis.
- Traceable results: every result belongs to a defined state.
- Protection against errors: unintended changes do not affect ongoing conversations.
What is usually locked
After the start, the core parts of the campaign are typically fixed, including the campaign goal, script, additional rules, result fields, booking settings and the runtime rules. These parts are part of the saved start state.
The assigned voice and the caller ID also belong to the fixed state. If you want to change them, set up a new campaign for that. The assigned leads and the runtime rules likewise stay unchanged while the campaign runs.
What you can still do
Even with locked settings, you keep control over the campaign's operation:
- You can pause and resume the campaign.
- You can finish and archive the campaign.
- You can set up a new campaign as a draft for changed content.
How knowledge behaves after the start is described separately in changing knowledge after campaign start.
Hinweis: If you need extensive changes to the goal, script or result fields, set up a new campaign for that instead of rebuilding a running campaign.