A dialogue system, or conversational agent (CA), is a computer system intended to converse with a human. Dialogue systems employ one or more of text, speech, graphics, haptics, gestures, and other modes for communication on both the input and output channel.
The elements of a dialogue system are not defined because this idea is under research; however, they are different from chatbots.[1] The typical GUI wizard engages in a sort of dialogue, but it includes very few of the common dialogue system components, and the dialogue state is trivial.
After dialogue systems based only on written text processing starting from the early Sixties,[2] the first speaking dialogue system was issued by the DARPA Project in the US in 1977.[3] After the end of this 5-year project, some European projects issued the first dialogue system able to speak many languages (also French, German and Italian).[4] Those first systems were used in the telecom industry to provide phone various services in specific domains, e.g. automated agenda and train tables service.
What sets of components are included in a dialogue system, and how those components divide up responsibilities differs from system to system. Principal to any dialogue system is the dialogue manager, which is a component that manages the state of the dialogue, and dialogue strategy. A typical activity cycle in a dialogue system contains the following phases:[5]
Dialogue systems that are based on a text-only interface (e.g. text-based chat) contain only stages 2–5.
Dialogue systems fall into the following categories, which are listed here along a few dimensions. Many of the categories overlap and the distinctions may not be well established.
Some authors measure the dialogue system's performance in terms of the percentage of sentences completely right, by comparing the model of sentences (this measure is called Concept Sentence Accuracy[6] or Sentence Understanding[4]). Dialogue systems can sometimes give inconsistent responses depending on how users phrase their questions[7] .
Dialogue systems can support a broad range of applications in business enterprises, education, government, healthcare, and entertainment. For example:
In some cases, conversational agents can interact with users using artificial characters. These agents are then referred to as embodied agents.
In the 2020s, dialogue systems have increasingly been built on top of large language models (LLMs), which allow them to handle open-domain conversation more flexibly than earlier rule-based or statistical approaches.[8] Modern implementations often integrate both voice and text interfaces, providing users with multi-modal interaction through conversational agents. Such systems are also being embedded into applications with user-friendly interfaces for customer service, education, and personal assistance.[9]
A survey of current frameworks, languages and technologies for defining dialogue systems.
| Name & links | System type | Description | Affiliation[s] | Environment[s] | Comments | |
|---|---|---|---|---|---|---|
| Chatterbot language | XML dialect for creating natural language software agents | |||||
| Chatterbot language | Language/Engine for creating natural language software agents | |||||
| CSLU Toolkit | A state-based speech interface prototyping environment | OGI School of Science and Engineering M. McTear Ron Cole | publications are from 1999. | |||
| Domain-independent toolkit | Complete multilingual framework for building natural language user interface systems | out-of-box support of mixed-initiative dialogues | ||||
| DaVoice AI | Domain-independent toolkit | Language/Engine for creating natural language software agents | Derek Willis | primarily for telephony. | ||
| Olympus | Complete framework for implementing spoken dialogue systems | http://wiki.speech.cs.cmu.edu/olympus/index.php/Olympus | ||||
| Nextnova | Multimodal Platform | Platform for developing multimodal software applications. Based on State Chart XML (SCXML) | ||||
| VXML Voice XML | Spoken dialogue | Multimodal dialogue markup language | Developed initially by AT&T, then administered by an industry consortium and finally a W3C specification | Example | primarily for telephony. | |
| markup language | Multimodal dialogue markup language | "has not reached the level of maturity of VoiceXML in the standards process". | ||||
| Quack.com - QXML | Development Environment | |||||
| OpenDial | Domain-independent toolkit | Hybrid symbolic/statistical framework for spoken dialogue systems, implemented in Java | ||||
| NADIA | dialogue engine and dialogue modelling | Creating natural dialogues/dialogue systems. Supports dialogue acts, mixed initiative, NLG. Implemented in Java. | Markus M. Berg | create XML-based dialogue files, no need to specify grammars, publications are from 2014 |
