How to check Analytics for yur Agents

icon picker
Analytics tab and filters

At the moment, the analytics of the
@Dialog
s of
@Bot User
s with
@Agent
s is presented on the
@Platform
in the form of a table with the
@Request
s of the
@Bot User
s.
On the Analytics tab, you can:
View
@Request
s processed by
@NLU
@Slot
s included in the
@Script
of all
@Agent
s of the
@Company
;
See the number of unique
@Chat
s,
@Dialog
s and
@Request
s for the period; ​
pasted image 0.png
Filter
@Request Table
data (details: );
Download message history (details: );
Download
@Context Variable
s (details: );
Download the statistics of passing by
@Slot
s (more details: );
Download an
@Agent
usage report (more details: );
Download a report of
@Dialog
completion
@Slot
s (more details: )

Information in the Request Table

When you open the tab, the number of
@Chat
s,
@Dialog
s and
@Request
s in the table is 0, and next to the
@Agent
selection field in the Filter by chat data section , a warning is displayed that you must select at least one
@Agent
. Also, when you open a tab, the value in the field FROM of the CREATION filter is preset to a month ago.
image.png
After selecting the
@Agent
and applying other filters in the
@Request Table
, you must click the SHOW REPORTS button . After that, the
@Request Table
will display the
@Request
s corresponding to the set filters. The list of all
@Request
s processed by the
@NLU
@Slot
s included in the
@Script
s of all
@Agent
s of the
@Company
is presented in the form of a
@Request Table
, where the columns contain various characteristics of these
@Request
s.
image.png

Description of fields

DIALOG ID
@Dialog
ID on the
@Platform
.
BOT — the name of the
@Agent
on the
@Platform
.
REQUEST — the text of the
@Request
.
TIMESTAMP date and time when the
@Bot user’s Message
was received, which is defined as a
@Request
.
STATUS — recognition status: recognized/unrecognized. Implemented the ability to edit the
@Intent
s’
@Training Dataset
by pressing the button next to the recognition status. More: .
RESOLVED — the status of working with the
@Request
: resolved / unresolved. If the
@Request
has been analyzed, if necessary, added to the
@Training Dataset
of the required
@Intent
and further work with this
@Request
is not required, for convenience, you can check the box.
INTENT — the
@Intent
to which the response was assigned. When the
@Intent
is unrecognized (status = unrecognized), this field has a dash. If the
@Intent
to which the
@Request
belongs was subsequently deleted — intent not found.
CONFIDENCE — confidence/threshold ratio. When the
@Intent
is unrecognized (status = unrecognized), this field has a dash.
Sorting by fields DIALOG ID , TIMESTAMP , INTENT is possible .
The first click on the column to be sorted in descending order, the second click in ascending order. When sorted in ascending order by the INTENT column , first
@Request
s with existing
@Intent
s are displayed in alphabetical order, then
@Request
s with deleted
@Intent
s; When sorting in descending order,
@Request
s with removed
@Intent
s go first, then those with existing
@Intent
s in reverse alphabetical order.

Applicable filters

Chat Data

The filters in this section are used to filter records based on the values ​​of the CHANNELS and AGENTS fields .
pasted image 0.png
CHANNELS: Multiple choice between
@End Channel
s. When using this filter, only
@Dialog
s in the selected channel(s) will be displayed in the list. Current
@End Channel
List:
pasted image 0.png
AGENTS: multiple choice between
@Agent
s. When using this filter, only the
@Dialog
s of the selected
@Agent
s will be displayed in the list.
pasted image 0.png

Dialog Data

The filters in this section are used to filter records by the values ​​of the CREATION , DURATION , DIALOG ID, CHANNEL VISITOR ID fields.
pasted image 0.png
CREATION: selection of the date and time interval for the creation of the
@Dialog
. The date and time of the first message in the
@Chat
is taken as the moment of creation of the
@Dialog
, in the absence of an unfinished
@Dialog
.
DURATION:
@Dialog
duration filter. The criteria for creating and ending a
@Dialog
are given above.
DIALOG ID: filter by
@Dialog
ID on the
@Platform
.
CHANNEL VISITOR ID: filter by
@channel_visitor_id
. The search is performed by the Chat ID from the End Channel — this information is stored in the
@Channel Variables
@channel_visitor_id
and
@channel_chat_id
.

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.