Chat page

With the Assistant module, it is possible to start various workflows through direct access in the Chat.

The Chat page is available to all users. If a workflow is initiated as a result of a message in the chat, the user who wrote the message in the chat will be the initiator of the workflow. 

The Chat page is a user interface where information about the message history is displayed both on the User and Assistant sides. It is available to the User with the roles of Assistant User, Assistant Administrator.

The Chat page has the following features:

  1. Using Assistant as an additional tool for employee communication with program robots (along with starting robots through the orchestrator and initiating the workflow by filling in data on the screen form).
  2. Receiving data from the robot directly to the chatbot.
  3. Transferring data to the robot via the Assistant.
  4. Classifying user requests in order to determine intent.
  5. Communicating with the Assistant using smart search.
  6. Launching feedback from any message from the Assistant sent to the chat (Feedback tab).

The view of the Chat tab page is displayed below.

The Chat page workspace contains input/output fields:

  • selecting the user's reference: classifier or smart search
  • entering and sending a message
  • displaying a request from the user
  • displaying a response from the Assistant
  • Possibility to start feedback

The Chat page interface is a field divided into 3 areas:

  • Chat area (1)
  • Assistant panel (2)
  • Requests tab (3)

On the right is the chat area.

Above the left side of the chat area is the Assistant panel, where the user can view the history of HIS chat requests, add/favorite workflows, as well as track active requests, overdue tasks and tasks on other people's requests.

Down from the left side of the chat area is the Requests tab.

Between the Assistant panel and the Requests tab there is a forward-back button (4) If you click this button, the Assistant panel is minimized - only the chat area remains visible.

Chat area

The Chat page displays the correspondence between the User and the Assistant.

It is possible to receive answers to questions from the chat in the form of text messages, or there is an option to receive a service, as a result of which the workflow is started.

The user writes his question in the text field of the chat (2) and sends it by clicking on the Send button (3) or by clicking on Enter.

Messages can be displayed in the chat in the format of screen forms that have been created in the screen form editor.

Feedback process (1) can be started from any assistant message sent to the chat.

On the left side of the chat, the user can view the history of their chat requests, as well as track active requests, overdue tasks, and tasks on other people's requests.

Description of chat area interface elements

Element name

Visibility

Description

Start feedback button (1)

If the feedback button in the Feedback tab is enabled

The button is located on the generated response of the Assistant to the user's request.

When clicked, the workflow selected in the Feedback tab is started.

The last message of the user in the chat and the last reply of the Assistant in the chat are the input attributes.

no name

User request input field (2)

If:

  1. A new request is created.
  2. Subject is not defined by the classifier of the selected skill.
  3. The Smart Search skill is used.

Used by the user to enter a text message into the chat.

Send button (3)

If:

  1. A new request is created.
  2. Subject is not defined by the classifier of the selected skill.
  3. The Smart Search skill is used.

Sends the user's request to the Assistant chat.

The button is inactive if there are no characters without a space in the input field of user's request.

The button is inactive if the skill is not selected by the user (if several skills are available).

Hot key Enter duplicates the functionality of the button.

Date of dialog start (4)

Displayed in the message

Displays the text of the dialog start date.

The questions asked by the User earlier to the Assistant in the chat will be displayed in the Dialogs tab in sent messages (2).

Assistant panel

The Assistant panel allows the User to view the history of his requests to chat.

By clicking the active requests, overdue tasks and tasks by other people's requests buttons, the history of the User's requests launched in the Requests tab is filtered.

The active requests include the requests that are currently running. If a workflow was started when executing a request, the request is in the active requests until the workflow is fully performed. 

The overdue requests include requests that are not completed in a certain period of time and are there until they are fully performed.

Requests that were assigned to the executor via a workflow launched through another user's chat are included in other people's requests.

If there are no requests according to the selected filter, nothing is displayed in the field.

If you click the active tasks, overdue tasks and tasks by other users' requests buttons again, the filtering is removed.

Filtering is displayed only by the clicked button, filters are not combined.

Assistant panel interface description

Element name

Description


Active requests filter button (1)

The button filters the history of user requests and messages from the chat assistant.

The button displays the number of records that match the filter and are active.

Requests are taken into account, in which the workflows that are currently running are launched - the workflows can be launched via the Classifier skill or by manually launching the workflow on the Favorites tab.

If there are no active records, the button is displayed without numbers.

When clicking on the filter:

    • The Requests tab becomes active.
    • Records on the Requests tab are filtered - only active user requests are displayed.

Filtering is maintained as long as the Active queries filter is selected.

Filtering is reset:

    • When you select a different filter button.
    • When you click the filter again.

If there was an active record (opened chat request history) that fits the filter logic, the record remains active, the chat is not changed.

Filter button

Overdue tasks (2)

Filter button by the history of user requests and messages from the assistant in the chat.

The button displays the number of records that match this filter and are active.

Requests with incomplete and overdue tasks in the form of SFs are taken into account:

    • A request with a launched workflow (via the Classifier skill or when manually launching a workflow on the Favorites tab), which receives a task where the task executor is the user who launched the workflow.
    • A request with a task assigned to the executor through a workflow launched through the chat of another user.

If there are no active records, the button is displayed without numbers.

When you click on the filter:

    • The Requests tab becomes active.
    • Records on the Requests tab are filtered - only overdue tasks of the user are displayed.

Filtering is maintained as long as the Overdue tasks filter is selected.

Filtering is reset:

    • When you select a different filter button.
    • When you click the filter again.

If there was an active record (opened chat request history) that fits the filter logic, the record remains active, the chat is not changed.

Filter button

Tasks by others' requests (3)

Filter button by history of messages from the chat assistant.

The button displays the number of records that match this filter and are active.

Requests with unfinished tasks in the form of SF assigned to an executor via a workflow launched via another user's chat are taken into account.

If there are no active records, the button is displayed without numbers.

When you click on the filter:

    • The Requests tab becomes active.
    • The records on the Requests tab are filtered - only the user's tasks by other people's requests are displayed.

Filtering is retained as long as the task filter for others' queries is selected.

Filtering is reset:

    • When you select a different filter button.
    • When you click the filter again.

If there was an active record (opened chat request history) that fits the filter logic, the record remains active, the chat is not changed.

untitled

Forward-backward button (4)

When you click the button, the Assistant panel is minimized - only the chat area remains visible.

If you click the button again, the panel is expanded.

By default, the panel is in the expanded state.

Requests tab

The Requests tab displays the list of user requests and messages from the Assistant in the chat.

If you click the New request button, a new chat is created, the user selects a skill (if more than one skill is available), a new request is created, which is entered into the list of requests history on the Requests tab.

The list of available skills is formed from groups of documents available to the user (the Intelligent search skill) and groups of classifiers (the Classifier skill).

Document group forms one skill in chat, classifier group forms as many skills as there are classifiers in the group.

If skill is used in chat:

    • Classifier, then new queries can be added to the chat until the classifier determines the subject of the query.
    • Smart search, then new queries can always be added to the chat room - a query record always has an active user query input field.

Records are added to the tab in the following cases if:

    • The user clicked the New request button and selected a skill in the chat room.
    • The user launched a workflow from the Favorites tab.
    • The user received a task in the form of an SF in chat, where he is the executor of the task, and the initiator of the workflow launched through chat, within which the task is directed, is another user. 
    • The user has sent requests earlier in the Assistant widget under his account, and a record with the history of requests from the widget in the read mode is added to the tab.

Records with tasks assigned to the group are not added to the Requests tab and are displayed to the user only within the Tasks subsection.

If there are no records, the tab displays text:
List of Requests to Assistant

By default, the tab is active.

Description of the interface elements of the Requests tab

Element name

Description

Field

untitled

Search field (1)

The search is performed by the headers of the queries created on the Queries tab.

Case is not taken into account.

Search by part of the name is available: the entered text can be in any part of the message in the request history.

Button

New request (2)

When the button is clicked, a new query is created

  • The button is displayed in two places - in the Requests tab and on the chat area itself (there are no request records in the tab or they are not selected for viewing by the user).
  • Highlighting any record for viewing in the Requests tab disappears
  • The chat is cleared
  • The user request entry field is displayed in the chat room.
  • If a user has:
    • one skill available - the Assistant's message about the active skill is added to the chat room
    • more than one skill available - an Assistant message is added to the chat to select a skill
  • A new user request record is generated on the Requests tab if:
    • Multiple skills are available - first the user selects a skill, then an entry appears, the title of the entry is displayed as:
      <Skill name>+order number of request with identical name
    • One skill is available - a record appears, the title of the record is displayed as:
      <Skill name>+order number of request with identical name
  • The button is inactive if the user has not selected a skill in the chat room

List

untitled

Records of user requests and messages from the chat assistant (3)

Displays records of user requests and messages from the chat assistant.

The record contains:

  • Headline
    • Name of skill + sequence number of the query with identical name in case when the Intelligent Search skill is selected or the subject of the classifier skill is not defined yet.
      If the subject is defined, the heading is changed (see the point below)
    • Name of skill (Name of subject) + sequence number of request with identical name when skill of classifier is selected and subject is defined after user's request.
    • The user name of the workflow + the sequence number of the request with the identical name when the user launched the favorite workflow from the Favorites tab.
    • <Workflow instance number>+<Name of the published workflow>, if a user has received a task in the form of an SF in chat, where the task executor is the user and the initiator of the workflow launched via chat, within which the task is sent, is another user
      Records with tasks assigned to a group are not added to the Requests tab and are displayed to the user only within the Tasks subsection
    • The last message added within the created request (updated with each new message added to the chat, online).
    • Date the request was created

Two identically named chats must always be distinguished by a number, except for the first one, it has no number.
Each new identical title is increased by +1 from the maximum number of the last identically named title.
Example:

    • Registration of requests
    • Registration of requests 2
    • Registration of requests 3
    • Registration of requests - the name was changed when the subject was determined
      Registration of vacation

If an assistant's reply is added to a user request record that has not been viewed by the user or a new task is assigned to a user that the user has not yet opened for viewing, the record in the list is marked with an unread message sign. 
The sign of an unread message disappears after opening a chat record and viewing the last message in it.

The history of messages is displayed as soon as you click on a chat entry:

    • tasks assigned to the user
    • user requests
    • assistant responses

Records are arranged by date - the most recently updated requests are added to the top.

The records contain icons similar to the filters above the Requests tab:

    • active requests - displayed on records where there are running workflows:
      1. The Classifier has identified a topic Workflow and the user launched it in the chatroom.
      2. A user launched a workflow from the Favorites tab.
    • overdue tasks - displayed on the records where there are tasks (SF) assigned to the user and the deadline for the task has already passed:
      1. Another user launched through chat a workflow from the Favorites tab or through a classifier that runs an SF assigned to the user.
      2. The user launched the workflow from the Favorites tab or through the classifier within which the SF assigned to the user is running.
    • tasks by others' requests - displayed on records in which there are tasks (SFs) assigned to a user when a workflow containing that task is launched via another user's chat room

Records do not contain icons if:

    • The workflow in the record has completed the care
    • The user has completed the task assigned to the user
    • There are no running workflows or tasks on the user in the record

List

Assistant widget

The record contains user requests and messages from the Assistant in the widget chat.

It is displayed only if the user has sent requests to the Assistant widget.

The record contains all messages that are available in the user's widget.

The chat is available for viewing only.

The record contains:

    • Title - Assistant widget

    • The last message added as part of the created request

    • Date the request was created

When you click on a chat entry, the message history is displayed:

    • user requests
    • assistant responses




  • Нет меток