Graphlogic.ai documentation

How to check Analytics for yur Agents

Chat history

The

@Platform⁠

has the ability to receive a file (.csv) by email with the history of

@Dialog⁠

s that meet the conditions of the installed analytics filters.

Request and receive a file

You can request a report on

@Chat⁠

history on the Analytics Tab.

Set the Analytics filters to the required values.

Click the Chat history button on the EXPORT panel.

⁠

When you click the button, a modal window with report filters appears.

⁠

The NLU requests filter is responsible for

@Bot user’s Message⁠

s passed through

@NLU⁠

@Slot⁠

The All messages and buttons filter is responsible for all

@Bot User⁠

and

@Agent⁠

messages (including

@Bot user’s Message⁠

s passed through

@NLU⁠

@Slot⁠

s, buttons, sending

@Attachment⁠

);

When you enable the All messages and buttons filter, the NLU requests filter is activated automatically.

The NLU requests filter cannot be turned off if the All messages and buttons filter is enabled.

After turning off the All messages and buttons filter, the NLU requests filter becomes available for switching.

⁠

The External requests filter is responsible for

@External Request⁠

The Incoming Requests filter is responsible for

@Incoming Request⁠

The Notifications filter is responsible

@Notification⁠

@Slot⁠

The Timers filter is responsible

@Timer⁠

@Slot⁠

Select the required filters and click the GET REPORT button. After this, the upload request will be sent to the

@Platform⁠

, where it will wait for processing in the general queue of upload requests.

You will receive a notification that the report will be sent to the email address to which your account is registered on the

@Platform⁠

⁠

If one

@Agent⁠

was selected in the analytics filters, after the system completes the request, an email with a link to download the file is sent to the user’s account. The link is valid for 24 hours.

If several

@Agent⁠

s were selected in the analytics filters, several letters will be sent, one for each

@Agent⁠

If there is no

@Conversation⁠

for one or more selected

@Agent⁠

s during the specified period, then empty reports will be received for these

@Agent⁠

The maximum delay between placing a request in the queue and sending the file by email is 24 hours.

Important: since the formation of the file takes some time, it will include the data that was in the system at the time when it was time to process the request. That is, the data available in analytics at the time of sending the request and the data in the file may differ.

Important: at the moment there is no limit on the number of requests sent, therefore, when sending repeated requests, there may be delays in receiving files, as well as mass receipt of letters by mail.

Report file

The

@Chat⁠

history report file has the extension .csv. Line separator is comma;

File encoding: UTF-8;

The file has a tabular structure;

The file can be opened with text editors;

The file can be opened with spreadsheet editors: Google Sheets, Open Office, Pages, MS Excel. It is not recommended to use MS Excel, since the file in one cell may contain values with line breaks (for example, bot text in several paragraphs), MS Excel may not process such breaks correctly, and the table structure will be broken

Table columns and their contents:

⁠

AGENT —

@Agent⁠

’s name

CHANNEL — name (type) of

@End Channel⁠

(Dialog360, Webim, Telegram, Jivosite, etc.)

CHANNEL_ID — ID of a specific channel

CHAT_ID —

@Chat⁠

CHAT CREATED — date and time of creation of the

@Chat⁠

, i.e. date and time of the start of the first

@Dialog⁠

in this

@Chat⁠

. Format HH:MM:SS DD.MM.YYYY (UTC).

VISITOR_ID — parameter obtained from the

@End Channel⁠

in which this

@Dialog⁠

took place

DIALOG_ID — identifier of the

@Dialog⁠

to which the message in this line belongs

DIALOG STARTED — date and time of the start of this

@Dialog⁠

. Format HH:MM:SS DD.MM.YYYY (UTC)

DIALOG DURATION — duration of this

@Dialog⁠

. Format HH:MM:SS

MESSAGE AUTHOR — author of the message in this line

agent — author is

@Agent⁠

⁠

user — author is

@Bot User⁠

⁠

system — for MESSAGE TYPE = timer, incoming request, external request, notification task, notification request, notification delivered, notification failed, notification no account

MESSAGE TYPE — message type

text — text

timer —

@Timer⁠

triggered

incoming request — launch of

@Incoming Request Slot⁠

button list — list of

@button⁠

external request — sending an

@External Request⁠

ER response — response from an external system to an

@External Request⁠

⁠

attachment — sending

@Attachment⁠

notification task — successful launch of mailing via the

@Notification⁠

@Slot⁠

notification request — arrives if the launch task was processed without errors and the system sent a request to the messenger API

notification delivered — arrives if the mailing has been delivered

notification failed — comes if there is no WhattsApp account for the specified number

notification no account — comes if sending the mailing failed

MESSAGE DATE TIME — the date and time of registration of this message in the

@Platform⁠

database. Format HH:MM:SS DD.MM.YYYY (UTC)

INTENT:

intent — name of the recognized

@Intent⁠

confidence-threshold shows the

@Confidence Threshold⁠

and confidence values for the processed

@Request⁠

. The first number shows the confidence value with which the

@Intent⁠

was recognized. The second number shows the

@Confidence Threshold⁠

value that was set for the

@NLU⁠

@Slot⁠

at the time this

@Request⁠

was recognized

request —

@Bot User⁠

’s

@Request⁠

message_history (2) - Google Таблицы - Google Chro.png

⁠

MESSAGE — message content; each type of content has its own format:

“text”: unformatted text of the

@Bot User⁠

’s or

@Agent⁠

’s message.

“timer”: empty string;

“incoming request”: text with the special word “BODY: “, followed by the request body.

“button list”: button labels, separated by commas in order of display, enclosed in quotes.

“external request”: parameters of the sent

@External Request⁠

in the format:

ER name: <name of External request>

headers: { <External request headers> }

body: {

“ER response”: response code and body of the received response, respectively, in the format: code: <response code>

body: { <response body> }

"attachment": type of sent file and link to the file in the format: type: <URL>

“notification task”: a request that the

@Platform⁠

receives when launching a mailing, and a response to it in the format: Request: <request> Response: code: <response code> body: {<response body>}

“notification request”: mailing status, a request that the

@Platform⁠

sends to the messenger (or omnichannel) API to launch the mailing and a response to it in the format: Request:<request> Response: code: <response code> body: {<response body>}

“notification delivered”: a request that the messenger/omnichannel platform sends to the

@Platform⁠

with the mailing delivery status in the format: Request: <request>

“notification failed”: a request sent by the messenger/omnichannel platform to the

@Platform⁠

with the mailing delivery status in the format: Request: <request>

“notification no account”: a request sent by the messenger/omnichannel platform to the

@Platform⁠

with the mailing delivery status in the format: Request: <request>

Request and receive a file

Report file

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.