Architecture

These docs are for version 1.x of Rasa Open Source.

• User Guide

  • Installation
  • Tutorial: Rasa Basics
  • Tutorial: Building Assistants
  • Command Line Interface
  • Architecture
  • Messaging and Voice Channels
  • Evaluating Models
  • Validate Data
  • Configuring the HTTP API
  • Deploying your Rasa Assistant
  • Cloud Storage

• NLU

  • About
  • Using NLU Only
  • Training Data Format
  • Choosing a Pipeline
  • Language Support
  • Entity Extraction
  • Components

• Core

  • About
  • Stories
  • Domains
  • Responses
  • Actions
  • Policies
  • Slots
  • Forms
  • Retrieval Actions
  • Interactive Learning
  • Fallback Actions
  • Knowledge Base Actions

• Conversation Design

  • Dialogue Elements
  • Small Talk
  • Completing Tasks
  • Guiding Users

• API Reference

  • Action Server
  • HTTP API
  • Jupyter Notebooks
  • Agent
  • Custom NLU Components
  • Rasa SDK
  • Events
  • Tracker
  • Tracker Stores
  • Event Brokers
  • Lock Stores
  • Training Data Importers
  • Featurization of Conversations
  • Migration Guide
  • Rasa OSS Change Log

• Migrate from (beta)

  • Dialogflow
  • Wit.ai
  • LUIS
  • IBM Watson

• Reference

  • Glossary

• Architecture
  This diagram shows the basic steps of how an assistant built with Rasa responds to a message:

The steps are:

1. The message is received and passed to an Interpreter, which converts it into a dictionary including the original text, the intent, and any entities that were found. This part is handled by NLU.
2. The Tracker is the object which keeps track of conversation state. It receives the info that a new message has come in.
3. The policy receives the current state of the tracker.
4. The policy chooses which action to take next.
5. The chosen action is logged by the tracker.
6. A response is sent to the user.

Note Messages can be text typed by a human, or structured input like a button press.

👋 I can help you get started with Rasa and answer your technical questions.