Configuring result fields
How to configure result fields for a campaign, which results are captured and how required fields steer the conversation.
Last reviewed: 2026-07-22
What result fields are
Result fields define which results a campaign captures in a structured way. They determine which details are recorded from each conversation and make the results comparable and analysable across all calls. This keeps traceable what a conversation achieved.
Defining result fields
Before the start, decide which results are relevant for your campaign. Pay attention to:
- a clear name for each field;
- an unambiguous description of what should be captured;
- a sensible number of fields, without overloading the conversation;
- the distinction between required fields and optional fields.
Define only fields the agent can actually capture during the conversation.
Required fields and gates
Required fields can act as a gate before a conversation is considered complete or before an appointment is booked. This ensures that important details are present. The agent asks at most one clear question per conversation step and does not re-ask details that have already been confirmed.
Fields that do not apply may be marked as such when a field does not fit a specific conversation.
Result status
For each field, the state of the detail can be recorded, for example captured, inferred, needs confirmation, missing or not applicable. These statuses help with later analysis. More on this in the article understanding result fields.
Do not define more fields than necessary. Every additional required field lengthens the conversation and can tire the person on the other end. Focus on the results you genuinely need for your analysis or for the next step.
Hinweis: Define the result fields before the start. At campaign start they are saved as part of the versioned campaign state and are locked afterwards.