Result fields and call ending

Result fields and an orderly call ending

Result fields can steer not only booking but also the end of a call. In many campaigns, a conversation should only end in an orderly way once the most important details have been captured. Result fields marked as required let you define which information should be present before the close.

For how a conversation is generally brought to a close, see call ending and hang-up.

Required fields as a gate before the close

A required field can act as a prerequisite for an orderly call ending. This means:

• The agent tries to capture open required details before the close.
• If a required detail is missing, it asks for it specifically.
• The agent poses at most one clear question per conversational step.
• Details that have already been confirmed are not asked again.

This avoids a conversation ending while important information is still missing.

Limits of the gate

A gate does not force details against the prospect's wishes. If the prospect wants to end the conversation or expresses a stop request, that takes precedence. The agent does not keep arguing after a clear call ending. In such cases, required fields may remain open and receive the status missing.

Hinweis: A gate ensures the agent tries to capture important details. It does not override an explicit wish to end the conversation.

Open fields after the call

If required fields remain open, this is visible in the analysis through the result status. For how to read the statuses, see understanding result status. For what you can check when results are missing, see missing or unclear results.

Related topics

• Required and optional result fields
• Result fields and booking