Result fields and booking
How result fields marked as required act as a gate before a booking and why no appointments are promised without configuration.
Last reviewed: 2026-07-22
How result fields and booking connect
Result fields and booking work together in many campaigns. Before the voice agent offers or books an appointment, certain details often need to be captured first, for example a confirmed interest or a required prerequisite. Result fields marked as required let you control this flow.
You configure the result fields in the campaign area and the appointment logic in the booking settings. For how to set up booking, see configuring booking settings. For an overview of the booking process, see booking in Nexcal.
Required fields as a gate before booking
A required field can act as a prerequisite for a booking. In that case, the agent should offer or book the appointment only once the required detail has been captured. This has several benefits:
- appointments arise only when the important prerequisites are met;
- unsuitable or premature bookings are avoided;
- the booking stays tied to the campaign goal.
If a required detail is missing, the agent asks for it specifically before moving to the booking, posing at most one clear question per conversational step.
What the agent does not do
Without the corresponding configuration, the agent does not promise appointments. If booking is not enabled or the prerequisites are not met, no appointment is booked. Instead of forcing an appointment, a callback can be offered as an alternative depending on the campaign. For more, see callbacks instead of appointments.
Hinweis: Make only those details required that are genuinely needed for a meaningful booking. Too many prerequisites can lengthen the conversation unnecessarily.