Work log

1. Description

It is designed to view the history of calls served by the Agent.

It consists of the following elements:

  1. Top bar (Fig.1(1));
  2. Filter block (Fig.1(2));
  3. Registry (Fig.1(3));
  4. Pagination (Fig.1(4)).

Fig. 1. Work log tab

1.1. Top bar

The top bar consists of a button to return to the Agents page (Fig.2(1)), displaying the name of the Agent (Fig.2(2)), the amount of time (Fig.2(5)), which they spent in each status, as well as:

  1. Agent evaluation (Fig.2(3));
  2. Status change menu (Fig.2(4));
  3. Call button (Fig.2(6)).

Fig. 2. Top bar

Data updates occur every 10 seconds automatically

1.1.1. Agent evaluation

This displays the number of calls rated by Auditors and Supervisors, as well as the summarised rating of the Agent. 

Rating—total score. It is calculated by the formula sum(call ratings) / number of rated calls, rounded off to hundredths (0.00).

Calls with transfers are not rated.

Only a call that has a call recording and/or transcription can be evaluated.

One call can only be evaluated once.

1.1.2. Status change menu

The status change menu consists of a timer that displays the amount of time in this status since the last transition to this status and a drop-down list that opens when you click on the timer field (Fig.3). The drop-down list displays the available transition statuses. To switch to the desired status, click on it in the drop-down list.

Fig. 3. Status change menu

There are such statuses:

 Offline;

 Online;

 Pause;

 Break out.

When the operator is in the Break out status, the drop-down list looks like in Fig. 4.

Fig. 4. Agent on Break out

An Agent enters the Break out status only if they miss the number of calls entered in the Max no answer field on the Timing tab of the agent`s Team. This parameter is counted by distributed calls that the Agent missed, regardless of whether the subscriber dropped it or was distributed to another Agent.

The status change menu forces the Agent to enter the required status.

When you select the Pause status, a Select the reason for the pause modal window opens (Fig. 5). The modal window displays all available pause reasons and the amount of time: How much time the Agent was in this pause today / How much time is provided for being in this pause?

Fig. 5. Select the reason for the pause modal window

Which pauses will be displayed in the modal window depends on the settings on the Agent Statuses page in the Admin application.

1.1.3. Call button

The button is designed to call the Agent. When you click the button, a call window opens (Fig. 6)

Fig. 6. Call window

When you hover the cursor over the window, it takes the following form (Fig.7):

Fig. 7. Expanded call window

When a call is accepted, the agent's name changes to its Extension, a talk time counter and additional tools appear (Fig.8), namely:

 - button to mute the microphone;   - the microphone is mute;

 - a call hold button; 

Fig. 8. Call window when dialing Agent


Clicking the end call button  ends the call and closes the window.

1.2. Filter block

It is designed to filter the data displayed in the registry.

It consists of the following elements:

  1. Filtering fields (Fig.9(1));
  2. Reset filters button (Fig.9(2));
  3. Expand filters button (Fig.9(3)).

Fig. 9. Filter block

1.2.1. Filtering fields 

Available fields for filtering:

  • From - sets the start time of the period for which you want to view data;
  • To - sets the end time of the period for which you want to view the data.

1.2.2. Reset filters button 

Represented as a button , all previously selected filters are reset when clicked.

1.2.3. Expand filters button

Represented as a  button, all fields for filtering are revealed when clicked.

Note

The number of fields displayed may vary depending on the browser window size. Use the  button to expand all fields.

1.3. Registry

It is designed to display records with call data.

It consists of the following elements:

  1. Select visible columns (Fig.10(1));
  2. Refresh button (Fig.10(2));

  3. Registry (Fig.10(3)).

Fig. 10. Registry

1.3.1. Select visible columns 

It is designed to select the columns displayed in the registry.

The Select visible columns modal window opens (Fig.11) when you click thebutton.

Fig. 11. Select visible columns modal window

Select the checkbox (Fig.11(1)) - this column is displayed in the registry;

Clear the checkbox (Fig.11(2)) - this column is not displayed in the registry.

1.3.2. Refresh button

Updating the register table is performed by clicking on the refresh button -

(Fig.3(2)).

1.3.3. Registry

The data in the registry is updated every 10 seconds.

The following columns are available in the registry:

  1. Date & time;
  2. Direction;
  3. Answered at;
  4. Bridged at;
  5. Queue bridged at;
  6. Joined at;
  7. Leaving at;
  8. Hangup at;
  9. Reporting at;
  10. User;
  11. Extension;
  12. From;
  13. To;
  14. Destination;
  15. Gateway;
  16. Team;
  17. Queue;
  18. Member;
  19. Duration;
  20. Tags;
  21. Display;
  22. Hold;
  23. Wait;
  24. Billing;
  25. Reporting;
  26. Queue wait;
  27. Queue duration;
  28. Result;
  29. SIP code;
  30. Hangup cause;
  31. Blind transfer.

1.3.3.1. Date & time

Displays the date and time of the event that occurred.

1.3.3.2. Direction

Displays call directions:

  •  - inbound;
  •  - outbound.

1.3.3.3. Answered at

The time when the connection with the subscriber took place is displayed - calls began to come to the subscriber.

1.3.3.4. Bridged at

Displays the connection time of the subscriber, or another Webitel User, with the Agent.

1.3.3.5. Queue bridged at

Displays the connection time of the Agent with the Subscriber.

The difference between Bridged at and Queue bridged at is that Bridged at displays the time for both calls from the Queue and internal calls, while Queue bridged at only displays the time for calls from Queues.

1.3.3.6. Joined at

Displays the time when the subscriber got into the Queue.

1.3.3.7. Leaving at

Displays the time when the subscriber left the Queue. The exit from the Queue is the connection with the Agent or the end of the call.

1.3.3.8. Hangup at

Displays the time the call ended.

1.3.3.9. Reporting at

Displays the time when Postprocessing started.

1.3.3.10. User

Displays the username.

1.3.3.11. Extension

Displays the user's Extension. Depending on the type of call, it has different meanings (see Tab. 1).

1.3.3.12. From

Displays the number from which the call originated. Depending on the type of call, it has different meanings (see Tab. 1).

1.3.3.13. To

Displays the number of the called party. Depending on the type of call, it has different meanings (see Tab. 1).

1.3.3.14. Destination

The number being called is displayed. Depending on the type of call, it has different meanings (see Tab. 1).


Сolumns
Call type

From

To

Destination

Extension

InboundSubscriber's numberWebitel User number (filled in after the User has picked up the phone)The number dialed by the Subscriber
Outbound IVR 

The number that is entered in the settings of the Resource through which the call is made

The number of the Subscriber to whom the call is being made (after modification, if digits were taken away or added)

Subscriber's number
User Extension (Webitel)

The number of the Subscriber to whom the call is being made (after modification, if digits were taken away or added)

Subscriber's numberUser Extension (Webitel)
Progressive dialerThe number that is entered in the settings of the Resource through which the call is made
  • The number of the Subscriber to whom the call is being made (after modification, if digits were taken away or added);
  • Webitel User number (filled in after the User has picked up the phone)
Subscriber's number
Predictive dialerThe number that is entered in the settings of the Resource through which the call is made
  • The number of the Subscriber to whom the call is being made (after modification, if digits were taken away or added);
  • Webitel User number (filled in after the User has picked up the phone)
Subscriber's number
OutboundUser Extension (Webitel)

The number of the Subscriber to whom the call is being made (after modification, if digits were taken away or added)

The number dialed by Webitel User/Agent

User Extension (Webitel)
Internal between Users

User Extension (initiator of the call)

User Extension (recipient of the call)User Extension (recipient of the call)User Extension (initiator of the call)

Tab. 1. Display data depending on the type of call

1.3.3.15. Gateway

Displays information on the Gateway that was used in this case.

1.3.3.16. Team

Displays the Agent's Team.

1.3.3.17. Queue

Displays the Queue that the call came from.

1.3.3.18. Member

Subscriber information is displayed.

1.3.3.19. Duration

Displays the amount of time spent on the call.

1.3.3.20. Tags

It is present in the records of calls in which an answering machine is configured in the routing with the ability to record a voice message.

1.3.3.21. Display

The number that is entered in the Resource settings is called through.

1.3.3.22. Hold

Displays the amount of time the call has been on hold. If there was no hold, the field is empty.

1.3.3.23. Wait

Displays the connection timeout.

1.3.3.24. Billing

Displays the amount of time the Subscriber has been connected to the Agent.

1.3.3.25. Reporting

Displays the amount of time the Agent spent on postprocessing.

1.3.3.26. Queue wait

Displays the time spent by the Agent in the Queue, from entering the Queue until the moment of connection with the Agent or until the end of the call in the case when the Subscriber ended the call without waiting for the Agent.

1.3.3.27. Queue duration

Displays the time spent by the Agent in the Queue from the moment they enter the Queue until the end of the call.

1.3.3.28. Result

Displays the result. There are the following result options:

  • missed - missed by the Agent, present only in the Preview dialer, when the Dialer did not reach the Agent and, accordingly, does not dial the Subscriber;
  • timeout - present in calls that have postprocessing configured. It is set if the Agent did not have time to finish postprocessing in time;
  • failed  - did not get through to the Subscriber;
  • abandoned - got through to the Subscriber, but there was no connection with the Agent;
  • success - successful result;
  • cancel - canceled.

1.3.3.29. SIP code

Displays the SIP call termination code. Possible reasons can be found in Table 3.

1.3.3.30. Hangup cause

Displays the reason for ending the call. Possible reasons can be found in Table 3.

When receiving/sending a HangUp event, we receive/send Cause Code, i.e., the reason the call ends and the subscriber leaves the queue.

In the table below you can view all Cause Codes used in ISDN telephony that correspond to the Q.850 protocol.

ITU-T Q.850 CodeSIP answerCauseDescription
0
UNSPECIFIED

It is issued by the router when none of the other codes fit. This cause usually occurs in situations similar to causes 1, 88, and 100.

1404UNALLOCATED_NUMBERThis cause indicates that called side cannot be reached because although the called side number possesses a valid format, currently it is not assigned (assigned).
2404NO_ROUTE_TRANSIT_NETThis cause indicates that the equipment sending this cause has received a request for call routing through a particular transit network which it does not recognize. The equipment sending this cause does not recognize the transit network for the following reasons: the transit network does not exist or that particular transit network, although it exists, does not maintain the equipment sending this cause.
3404NO_ROUTE_DESTINATION

This cause indicates that called side cannot be reached because a network through which the call has been routed doesn’t maintain a desirable destination. This cause is supported depending on the network.

6
CHANNEL_UNACCEPTABLEThis cause indicates that the last identified channel is not acceptable for the sending object to use in this call.
7
CALL_AWARDED_DELIVERED

A user has been given an incoming call, and the incoming call connects to the channel already set for that user for similar calls (for example, x.25 virtual calls in a package mode).

16
NORMAL_CLEARINGNormal call termination
17486USER_BUSYThe called side cannot take another call because the user's busy state has been detected. This cause value can be created by a called user or network. In case when the user is detected as busy, it is noted that the user’s equipment is compatible with the call.
18408NO_USER_RESPONSEThe called side doesn't respond to a message of call establishing, warning, or connection indication during an established period.
19480NO_ANSWERThis cause is used when a called side has been warned but is not answering with a connection indication during the prescribed period. A note: this cause is not necessarily generated by the Q.931 procedures but can be caused by the internal network timers.
20480SUBSCRIBER_ABSENTThis cause value is used when the mobile station has logged out of the system, the radio connection with the mobile station has not been established, or the personal radio connection user temporary does not possess the address on any user network interface
21603CALL_REJECTEDThis cause indicates that the equipment sending this cause does not wish to receive this call although it may have accepted this call because the equipment sending this cause is not busy or incompatible. A network also can generate this reason indicating that the call has been rejected due to the restrictions of additional service. The diagnostics field may include additional information about the additional service and the reason for denying.
22410NUMBER_CHANGEDThis cause is returned to the calling side when the called side’s number specified by the calling side is no longer assigned. The new calling side number may be optionally included in the diagnostics field. When the network does not support this cause, it means the reason №1: unallocated (unassigned) number must be used.
23410REDIRECTION_TO_NEW_DESTINATIONThis cause is used by the general ISUP protocol mechanism which can be launched by the commutator that decides to establish a call to another called number. This exchange may cause a redirection mechanism that uses this cause value to request a previous exchange participating in the call to route the call to the new number.
25483EXCHANGE_ROUTING_ERROR

This cause indicates that the destination point specified by the user cannot be reached because the intermediate commutator has disabled the call due to reaching the limit while executing the hop counter procedure. This cause is generated by the intermediate node that produces a result of 0 when the hop counter value is decreasing.

27502DESTINATION_OUT_OF_ORDERThis cause indicates that the destination point specified by the user cannot be reached because the interface of the destination point does not work properly. The ‘does not work properly’ term means that the signaling message could not be delivered to the remote side; for example, physical level failure, level of data transmission channel on the remote side, or the disabled user’s equipment.
28484INVALID_NUMBER_FORMATThis cause indicates that a called side cannot be reached because the called side number has an invalid or incomplete format.
29501FACILITY_REJECTEDThis cause returns when an additional service requested by the user cannot be provided by the network.
30
RESPONSE_TO_STATUS_ENQUIRYThis cause is included in the STATUS message when the prior receipt of the STATUS INQUIRY was a reason for generating the STATUS message.
31480NORMAL_UNSPECIFIEDThis reason is used to report a normal event only when none of the other reasons in the normal class apply.
34503NORMAL_CIRCUIT_CONGESTIONThis cause indicates that currently there is no suitable circuit/channel for call processing.
38503NETWORK_OUT_OF_ORDERThis cause indicates that a network is not working properly, and this state is likely to last for a long time so the immediate call retry is unlikely to be successful .
41503NORMAL_TEMPORARY_FAILUREThis cause indicates that a network is not working properly, and this state is unlikely to last for a long time; so the user may want to make one more call attempt almost immediately.
42503SWITCH_CONGESTIONThis cause indicates that the switching equipment generating this cause is experiencing a high traffic period
43
ACCESS_INFO_DISCARDEDThis cause indicates that a network couldn’t deliver to the remote user information about access according to the request, i.e the information between users, low-level compatibility, high-level compatibility, or subaddress as specified in the diagnostics.
44503REQUESTED_CHAN_UNAVAILThis cause comes back when another side of the interface cannot provide the scheme or channel indicated by the requesting object.
50
FACILITY_NOT_SUBSCRIBEDThis cause indicates that a user has requested an additional service that is available but the user is not authorized to use.
52403OUTGOING_CALL_BARREDThis cause indicates that although the calling side is a subscriber of the CUG outbound call, the outbound calls are not allowed for this CUG subscriber.
54403INCOMING_CALL_BARREDThis cause indicates that although the called side is a CUG subscriber for the inbound call, the inbound calls are not allowed for this CUG subscriber.
57403BEARERCAPABILITY_NOTAUTHThis cause indicates that a user has requested a transfer capability that is implemented by the equipment that generated this cause but the user is not authorized to use.
58503BEARERCAPABILITY_NOTAVAILThis cause indicates that a user has requested a transfer capability that is implemented by the equipment that generated this cause but which is currently unavailable.
63
SERVICE_UNAVAILABLEThis cause is used for informing about the cause of service or parameter unavailability only when none of the other reasons in the service class or parameter unavailability apply.
65488BEARERCAPABILITY_NOTIMPLThis cause indicates that the equipment sending this cause does not support the requested transfer capability.
66
CHAN_NOT_IMPLEMENTEDThis cause indicates that the equipment sending this cause does not support the requested channel type.
69501FACILITY_NOT_IMPLEMENTEDThis cause indicates that the equipment sending this cause does not support the requested additional services
79501SERVICE_NOT_IMPLEMENTEDThis cause is used for informing about the cause that is related to the unimplemented service or parameter only if none of the other reasons in the class of unimplemented service or parameter apply.
81
INVALID_CALL_REFERENCEThis cause indicates that the equipment sending this cause received a message with a link to a call that is not currently used in the user-network.
88488INCOMPATIBLE_DESTINATIONThis cause indicates that the equipment sending this cause has received a request to establish a call that has low-level compatibility, high-level compatibility, or other compatibility attributes (for example, data transmission speed) which cannot be implemented.
95
INVALID_MSG_UNSPECIFIEDThis reason is used for informing about invalid message cause only if any other reason in the invalid message class does not apply.
96
MANDATORY_IE_MISSINGThis cause indicates that the equipment sending this cause has received a message without an information element that must be present in the message before this message can be processed.
97
MESSAGE_TYPE_NONEXIST

This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize because this message is not defined or defined but not implemented by the equipment sending this cause.

98
WRONG_MESSAGEThis cause indicates that the equipment sending this cause has received a message that the procedures do not indicate that it is a valid message to receive in the call state, or that a STATUS message was received indicating the incompatible call state.
99
IE_NONEXISTThis cause indicates that the equipment sending this cause has received a message including unrecognizable information element (s) because the information element (s) / parameter (s) name (s) is (are) not defined or defined but not implemented by the equipment sending this cause. This reason indicates that the information element (s) has (have) been discarded. However, the information element is not obligated to be present in the message to allow the equipment sending this cause to process the message.
100
INVALID_IE_CONTENTSThis cause indicates that the equipment sending this cause has received the information element that was implemented by it. However, one or several fields in the I.E. are encoded in a way that hasn’t been implemented by the equipment sending this cause
101
WRONG_CALL_STATEThis cause indicates that a message non-compliant with the call state has been received. 
102504RECOVERY_ON_TIMER_EXPIREThis reason indicates that a procedure was initiated by timer expiration connected with error processing procedures. This is often caused by NAT issues. Make sure «NAT Mapping Enable» is activated in your ATA. If it isn’t concerning NAT, sometimes it refers to a provider. Check if another outbound provider can solve a problem.
103
MANDATORY_IE_LENGTH_ERROR

This cause indicates that the equipment sending this cause has received a message including parameters that are not recognized because parameters are not defined or defined but not implemented by the equipment sending this cause. The reason indicates that the parameters have been ignored. Besides, if the equipment sending this cause is an intermediate point thus this cause indicates that the parameter (parameters) was (were) transmitted without changes.

111
PROTOCOL_ERRORThis reason is used for informing about protocol error cause only in case when none of the other causes in the protocol error class apply.
127
INTERWORKINGThis reason indicates that an internetwork call (usually an SW56 service call) has ended.
503
MANAGER_REQUESTThis cause is used when you send an API command to end the call.
605
PICKED_OFFThis cause means that the call was picked up from another added number.
606
USER_NOT_REGISTEREDThis means you tried to call a SIP user that has not been registered.
609
GATEWAY_DOWNGateway is down (does not respond to OPTIONS or SUBSCRIBE)
687
ABANDONEDThis means that the call was canceled by the dialer


ORIGINATOR_CANCELThe call originator (agent or client) ended the call before receiving the answer (Answer)

Tab. 3. Hangup cause

1.3.3.31. Blind transfer

The number to which the blind transfer was made is displayed here. When there is no blind transfer, the field remains empty.

1.4. Pagination

It consists of the Rows per page field, which indicates the number of entries (it is possible to set from 1 to 1000) per page, and forward and backward buttons for switching pages.

2. Opportunities

2.1. View information for a specific period

Goal

View information for a specific period

Preconditions
  1. Access to the Supervisor application;
  2. Access to the Agents section in the Supervisor application;
  3. The presence of at least one Agent.

Steps


  1. Click on the From field (Fig.9). The calendar opens;
  2. Select the date and time of the beginning of the period for which you want to view information;
  3. Click the Add button. The calendar closes. The selected date and time are displayed in the From field;
  4. Click on the To field (Fig.9). The calendar opens;
  5. Select the date and time of the end of the period for which you want to view information;
  6. Click the Add button. The calendar closes. The selected date and time are displayed in the To field.

Result

The registry displays records for the selected period.

2.2. Selection of displayed columns in the registry

Goal

Select of displayed columns in the registry

Preconditions
  1. Access to the Supervisor application;
  2. Access to the Agents section in the Supervisor application;
  3. The presence of at least one Agent.

Steps


  1. Click thebutton. The Select visible columns modal window opens (Fig.4).
  2. Columns to display in the table - select in the checkbox; columns that should not be displayed - clear checkboxes.
  3. Click the Add button.

Result

The modal window closes. The selected columns are displayed in the registry.

2.3. Change Agent status

Goal

Change Agent status from Online to Pause

Preconditions
  1. Access to the Supervisor application;
  2. Access to the Agents section in the Supervisor application;
  3. The Agent is in Online status;
  4. The presence of a Lunch pause, for example.

Steps


  1. Click on the status change menu (Fig.2(4)). A drop-down list opens.
  2. Select Pause by clicking on it. The Choose a reason of pause modal window opens.
  3. Select Lunch by clicking. The OK button becomes active.
  4. Click the OK button.

Result

The Agent has entered the Lunch pause status.

2.4. Call the Agent

Goal

Make a call to the Agent

Preconditions
  1. Access to the Supervisor application;
  2. Access to the Agents section in the Supervisor application;
  3. The presence of at least one Agent.

Steps

  1. Click the Call button (Fig.2(3)). The call window opens (Fig.3).

Result

A call is made to the Agent.