-
Notifications
You must be signed in to change notification settings - Fork 2
Conversation
It is an API that allows you to build, test and deploy a bot or virtual agent across mobile devices, messaging platforms like Facebook, Twitter,Slack. It also has a visual dialog builder to help you create natural conversations between your apps and users.
There is a demo page, you may try it instantly.
This diagram shows the overall architecture.
**1)**Users interact with your application through the user interface that you implement.
Such as a simple chat window or a mobile app, or even a robot with a voice interface.
**2)**The application sends the user input to the Conversation service.
**3)**The application can interact with your back-end systems based on the user's intent and additional information.
The natural-language processing for the Conversation service happens inside a workspace, which is a container for all of the artifacts that define the conversation flow for an application.
A single Conversation service instance can contain multiple workspaces.
A workspace contains the following types of artifacts:
An intent represents the purpose of a user's input, such as a question about business locations or a bill payment. You define an intent for each type of user request you want your application to support. In the user interface, the name of an intent is always prefixed with the # character. To train the workspace to recognize your intents, you supply lots of examples of user input and indicate which intents they map to.
An entity represents a term or object that is relevant to your intents and that provides a specific context for an intent. For example, an entity might represent a city where the user wants to find a business location, or the amount of a bill payment. In the user interface, the name of an entity is always prefixed with the @ character. To train the workspace to recognize your entities, you list the possible values for each entity and synonyms that users might enter.
A dialog is a branching conversation flow that defines how your application responds when it recognizes the defined intents and entities. You use the dialog builder to create conversations with users, providing responses based on the intents and entities that you recognize in their input.
- Alpertunga Ertin
- Ahmet Buğrahan Taşdan
- Burak Sofu
- Halil Ozan Akgül
- Harun Zengin
- Onur Kalınağaç
- Ozan Kınasakal
- Pınar Baki
- Rahmetullah Varol
- Utku Bozdoğan
- Meeting-1 (12.02)
- Meeting-2 (17.02)
- Meeting-3 (24.02)
- Meeting-4 (02.03)
- Meeting-5 (10.03)
- Meeting-6 (16.03)
- Meeting-7 (06.04)
- Meeting-8 (05.05)