Konversations-KI

A dialogue system needs more than fluent sentences to complete a defined task. In a classic task-oriented pipeline, natural language understanding interprets the request, identifying an intent and values for relevant slots. A slot might hold a destination or date, while the intent identifies the requested operation. State tracking maintains structured information across turns, including corrections, rather than merely assigning a permanent label to the first message. A policy selects the next action from the state and task context, such as asking about an unfilled field or invoking an allowed operation. Natural language generation expresses the selected response in words. These roles can be implemented separately or combined; the decomposition does not assert that every current product uses four independent modules. The original Rasa work provides a concrete example of learned language understanding and dialogue management, including choosing questions based on known slots. MultiWOZ supplies human-human task conversations and benchmarks distinct tracking and generation tasks. Rigid rules can fail when a valid user request falls outside the anticipated patterns, though a learned system can also misinterpret an unfamiliar request. Providing earlier conversation text as model context can help subsequent responses refer to prior turns. That is not automatically permanent memory or an update to model weights, and omitted context may not be available to the current response. Voice adds another stage: automatic speech recognition converts speech to text, while interpretation and action selection operate on the resulting request. Incorrect replies and obstructed escalation remain practical risks, as documented in the CFPB’s consumer-finance chatbot report. Task success and factual correctness therefore need evaluation alongside fluency.