Required and optional result fields
The difference between required and optional result fields and how required fields act as a gate before booking or call ending.
Last reviewed: 2026-07-22
Required and optional fields
Result fields can be defined as required fields or as optional fields. Required fields are details the voice agent should capture in the conversation because they are decisive for the campaign goal. Optional fields are supplementary details that are captured when they come up in the conversation but are not strictly necessary.
You make this classification during campaign configuration. For details, see configuring result fields.
Required fields as a gate
Required fields can act as a prerequisite, that is, a gate, for certain steps. This means:
- A required field may need to be captured before a booking.
- A required field may need to be captured before an orderly call ending.
- If a required detail is missing, the agent should ask for it specifically.
This ensures that key information is present before a conversation reaches an outcome. The interplay with booking is described in result fields and booking.
Distinguishing required from optional sensibly
Not every detail needs to be a required field. Too many required fields can make a conversation feel unnatural. A few principles help:
- Make only those details required that are genuinely needed for the campaign goal.
- Use optional fields for supplementary information.
- The agent asks at most one clear question per conversational step.
- Details that have already been confirmed are not asked again.
Fields that do not apply
If a field does not apply to a specific conversation, it can be marked as not applicable. This keeps it traceable that the detail was deliberately not captured rather than missing by mistake. For more on the possible states, see understanding result status.
Hinweis: Before the campaign starts, review which fields really need to be required. A clear classification helps the agent keep the conversation natural.