Custom campaign
When a custom campaign is the right choice and how you freely define goal, script and results when no standard type fits.
Last reviewed: 2026-07-22
What a custom campaign is
A custom campaign is the right choice when no standard type reflects your conversation goal. You define the goal, script and results freely and assemble the building blocks as your use case requires. Here too, the voice agent stays bound to the campaign goal and the configured rules.
When this type fits
Choose a custom campaign when your plan combines several goals or deviates from the usual patterns. Typical examples:
- a conversation that should inform and capture feedback at the same time;
- a flow that captures several results in a specific order;
- a special case for which none of the standard types fit.
If your goal clearly matches a standard type, that type is usually the simpler choice.
What you define yourself
In a custom campaign, you configure the building blocks deliberately:
- Formulate a clear campaign goal and a description.
- Create a script as the conversation guardrail.
- Provide the matching knowledge as the factual basis.
- Define the result fields for the results to be captured.
- Enable the booking settings if needed.
The more carefully you align these building blocks, the more reliably the conversation proceeds. Also check whether the result fields cover all the results you want to analyse later, so there are no gaps in the documentation.
Limits of a custom campaign
Even a freely configured campaign ideally pursues one clear main goal. Too many equally ranked goals in a single conversation make it harder for the agent to steer and make the results less comparable. Consider whether several separate campaigns are the better choice when the goals differ significantly.
Hinweis: A custom campaign also follows the functional hierarchy of goal, script, AI layer, knowledge, objection rules and result fields. The agent does not invent offers and does not deviate from the goal.