1. Home
  2. Docs
  3. Publishers
  4. Basics
  5. GUI Walkthrough

GUI Walkthrough

In this article, we will go through all GUI views and shortly describe what for and how to use them.


This is the Convoworks entry view where you can find all services you are allowed to access.

When creating a new service you can choose one of the available service templates to start with. There is a set of basic templates we provide, but if you installed some package extensions, you might find even more of them.

In the close feature, you’ll be able to start service from the uploaded template (the current workaround is to create service and use Import/Export to upload exported service)

Workflow Editor

This the heart of Convoworks functionality. Here you can add and re-arrange workflow components, here you define the real conversation.

Basic usage

  • drag and drop components from the toolbox (left) to the appropriate container in a currently selected block
  • select (click on it) on the component in the block to see and configure its properties
  • use drag and drop to re-arrange components’ order, both in the selected block (main section), or the order of the blocks (right)
  • use right-click to copy/paste used components
  • most of the components have help (available in component properties container on right)

Here are a few hints for using it in a more effective way

  • you can click on GOTO or INCLUDE components to follow (select in the editor) the referencing block
  • you can use browser navigation to navigate through block selection
  • you can close popups by pressing the ESC key


This is a simple view that lists all of your conversational blocks, but it displays just textual information, actually all conversation outcomes and expectations. We find it very useful for service overview or lecturing purposes.

In the close future, we will add the ability to inline edit responses and/or select a particular component in the workflow editor.

Use the copy SSML button to quickly test how the response sounds in Amazon or Google’s test views.


Here you can define variables that are accessible in any place in the service. It can be used to define some service level constants, like service name, some limits, defaults, … Variables that you might need to tune up through the time or ones which will be different for your testing and production environments.

Preview variables are used only when generating service or block preview. That way you can replace used expressions in service with the concrete values and have a much nicer and comprehensive preview.

Intent Model

Here you can see and define your service custom intents and entities.


Here you can set some basic Convoworks settings, like service name, ownership or you can share your service with other persons registered in your system.

Here you are also enabling and configuring access to target platforms, like Amazon or Google.


One of the main requirements in this kind of system is the ability to have separated live and development versions.


In Convoworks you are able to export your service and import it back. It is quite useful if you would like to develop a service on your local machine and after it is finished, import it to the production installation.

You also have the ability to export your model as Amazon or Dialogflow compatible model – to be honest, we are not sure when this might be useful.

When importing Convoworks service definition, you have the options to keep local variable and configuration settings – this is definitely useful when developing on multiple installations.


In the end, you have to test the service somewhere.

The current state of our test view is not spectacular, but it can be used for some basic tests. One important feature that it has is that you are able to eventual exceptions and you are able to see runtime variables values, while you are testing.