From Bright Pattern Documentation
(Marked this version for translation) |
|||
| Line 1: | Line 1: | ||
| − | <translate>= overflow_counters= | + | <translate>= overflow_counters= <!--T:1--> |
This table contains metrics for the distribution of inbound interactions among various routing targets, including overflow destinations. The metrics are provided for all services defined in your contact center configuration. Note that if a service can be accessed via multiple access numbers, the metrics are provided for each access number separately. | This table contains metrics for the distribution of inbound interactions among various routing targets, including overflow destinations. The metrics are provided for all services defined in your contact center configuration. Note that if a service can be accessed via multiple access numbers, the metrics are provided for each access number separately. | ||
| + | <!--T:2--> | ||
Unless noted otherwise with respect to a particular metric, any ''call'' mentioned in this table shall be interpreted as a call that requested the service specified in the ''service_name'' field. | Unless noted otherwise with respect to a particular metric, any ''call'' mentioned in this table shall be interpreted as a call that requested the service specified in the ''service_name'' field. | ||
| − | == Description of Data == | + | == Description of Data == <!--T:3--> |
The following table offers the name (i.e., ID), data type (e.g., BIGINT, BINARY, BIT, DATETIME, ENUM, INT, VARCHAR, etc.), and description for each metric (i.e., column) of the ''overflow_counters'' table. | The following table offers the name (i.e., ID), data type (e.g., BIGINT, BINARY, BIT, DATETIME, ENUM, INT, VARCHAR, etc.), and description for each metric (i.e., column) of the ''overflow_counters'' table. | ||
| + | <!--T:4--> | ||
{|border="1" style="border-collapse:collapse" cellpadding="5" | {|border="1" style="border-collapse:collapse" cellpadding="5" | ||
|'''Column Name''' | |'''Column Name''' | ||
| Line 21: | Line 23: | ||
|''destination_phone'' specifies the access number for this service as defined in the Dial-in Scenario Entry associated with service. | |''destination_phone'' specifies the access number for this service as defined in the Dial-in Scenario Entry associated with service. | ||
| + | <!--T:5--> | ||
If a service is associated with multiple access numbers, metrics specified in this table will be provided for each access number separately. | If a service is associated with multiple access numbers, metrics specified in this table will be provided for each access number separately. | ||
|- | |- | ||
| Line 43: | Line 46: | ||
|This is the interaction media type. | |This is the interaction media type. | ||
| + | <!--T:6--> | ||
Possible values include VOICE, CHAT, and EMAIL. | Possible values include VOICE, CHAT, and EMAIL. | ||
| + | <!--T:7--> | ||
If set to CHAT, any ''call'' mentioned in this table shall be interpreted as a service chat interaction in the same context. | If set to CHAT, any ''call'' mentioned in this table shall be interpreted as a service chat interaction in the same context. | ||
|- | |- | ||
| Line 56: | Line 61: | ||
|This metric specifies the number of calls that abandoned while ringing after being routed to the given destination. | |This metric specifies the number of calls that abandoned while ringing after being routed to the given destination. | ||
| + | <!--T:8--> | ||
It includes only calls that were abandoned outside of the configured service level threshold. | It includes only calls that were abandoned outside of the configured service level threshold. | ||
|- | |- | ||
| Line 70: | Line 76: | ||
|''routed_to'' refers to the target destination to which the calls were routed, the name of the team for internally routed calls, and/or the external number for externally routed calls. | |''routed_to'' refers to the target destination to which the calls were routed, the name of the team for internally routed calls, and/or the external number for externally routed calls. | ||
| + | <!--T:9--> | ||
If calls were routed to multiple destinations, metrics specified in this table will be provided for each destination separately. | If calls were routed to multiple destinations, metrics specified in this table will be provided for each destination separately. | ||
|- | |- | ||
Revision as of 22:54, 16 August 2019
• 日本語
<translate>= overflow_counters= This table contains metrics for the distribution of inbound interactions among various routing targets, including overflow destinations. The metrics are provided for all services defined in your contact center configuration. Note that if a service can be accessed via multiple access numbers, the metrics are provided for each access number separately.
Unless noted otherwise with respect to a particular metric, any call mentioned in this table shall be interpreted as a call that requested the service specified in the service_name field.
Description of Data
The following table offers the name (i.e., ID), data type (e.g., BIGINT, BINARY, BIT, DATETIME, ENUM, INT, VARCHAR, etc.), and description for each metric (i.e., column) of the overflow_counters table.
| Column Name | Data Type | Description |
| agg_run_id | BINARY (16) | Aggregator run that produced this record |
| destination_phone | VARCHAR | destination_phone specifies the access number for this service as defined in the Dial-in Scenario Entry associated with service.
If a service is associated with multiple access numbers, metrics specified in this table will be provided for each access number separately. |
| end_time | DATETIME | End time of the aggregation interval; time is given in Universal Coordinated Time (UTC) |
| handling_time | BIGINT | Total time that the answered calls were handled at the given destination (the sum of talk, hold, and after-call work times) |
| id | BINARY (16) | Primary key |
| is_overflow | BIT | TRUE if the given destination is an overflow destination |
| media_type | ENUM | This is the interaction media type.
Possible values include VOICE, CHAT, and EMAIL. If set to CHAT, any call mentioned in this table shall be interpreted as a service chat interaction in the same context. |
| no_team | BIT | TRUE if the given destination is an external number; FALSE if the given destination is a team |
| num_calls_abandoned_
after_threshold |
BIGINT | This metric specifies the number of calls that abandoned while ringing after being routed to the given destination.
It includes only calls that were abandoned outside of the configured service level threshold. |
| num_calls_answered | BIGINT | Number of calls that were answered at the given destination |
| num_calls_received | BIGINT | Total number of calls that requested this service and were routed to the given destination |
| routed_to | VARCHAR | routed_to refers to the target destination to which the calls were routed, the name of the team for internally routed calls, and/or the external number for externally routed calls.
If calls were routed to multiple destinations, metrics specified in this table will be provided for each destination separately. |
| service_name | VARCHAR | Name of the service as defined in service configuration |
| start_time | DATETIME | Start time of the aggregation interval; time is given in Universal Coordinated Time (UTC) |
</translate>