How contact center platforms define service level and abandon and handle time differently

See also

Sources

1. 1
   The Amazon Connect data lake reference query for Contacts abandoned in X seconds counts contacts with is_abandoned = 1 and queue time at or under X, which is how a short-abandon bucket can be derived since abandonment rate itself has no short-abandon exclusion.

   Reference queries for the Connect Customer data lake · Contact and queue metrics > Contacts abandoned in X seconds · Checked 2026-10-02
2. 2
   Amazon Connect computes Abandonment rate as (Contacts abandoned / Contacts queued) * 100, where an abandoned contact is one the customer disconnected while in queue before connecting to an agent.

   Metrics definitions in Connect Customer · section Abandonment rate, Calculation logic · Checked 2026-10-02
3. 3
   Amazon Connect Average after contact work time averages over every contact record that has either an ACW duration or an agent-connected timestamp, counting connected contacts with no ACW as zero.

   Metrics definitions in Connect Customer · section Average after contact work time, Calculation logic · Checked 2026-10-02
4. 4
   The Amazon Connect data lake reference query defines average handle time as the time from contact connection to ACW completion, averaging handle_time_ms over handled contacts only.

   Reference queries for the Connect Customer data lake · Agent performance metrics > Average handle time · Checked 2026-10-02
5. 5
   Amazon Connect does not count contacts queued for callback as abandoned in the Abandonment rate metric.

   Metrics definitions in Connect Customer · section Abandonment rate, definition paragraph · Checked 2026-10-02
6. 6
   Amazon Connect delivers contact records at least once, so exact counts from the data lake need de-duplication on primary keys.

   Reference queries for the Connect Customer data lake · Best practices > Deduplication · Checked 2026-10-02
7. 7
   Amazon Connect GetMetricData only returns historical metrics for the previous 24 hours, while AWS recommends GetMetricDataV2 for the last 3 months.

   GetMetricData - Amazon Connect API Reference · Note at top of page; Request Body > StartTime · Checked 2026-10-02
8. 8
   Amazon Connect contact InitiationMethod distinguishes TRANSFER from QUEUE_TRANSFER, along with INBOUND, OUTBOUND, CALLBACK, API and other values.

   Contact - Amazon Connect API Reference · Contents > InitiationMethod valid values · Checked 2026-10-02
9. 9
   In Amazon Connect, Abandonment rate shows 0 when results are grouped by routing profile, because an abandoned contact never reaches an agent and so has no routing profile.

   Metrics definitions in Connect Customer · section Abandonment rate, note on Routing Profile grouping · Checked 2026-10-02
10. 10
    The Amazon Connect GetMetricData API accepts a SERVICE_LEVEL threshold of any whole number of seconds from 1 to 604800 and requires the comparison LT (less than).

    GetMetricData - Amazon Connect API Reference · Request Body > HistoricalMetrics > SERVICE_LEVEL · Checked 2026-10-02
11. 11
    The Amazon Connect data lake reference query for service level counts contacts that were handled with queue answer time at or under X and divides by all queued contacts, so abandoned contacts sit in the denominator and never in the numerator.

    Reference queries for the Connect Customer data lake · Contact and queue metrics > Service level (anchor data-lake-rq-service-level) · Checked 2026-10-02
12. 12
    The Amazon Connect GetMetricData reference links the SERVICE_LEVEL metric's UI name to Average queue abandon time, which is a documentation labelling error rather than the metric's meaning.inferred

    GetMetricData - Amazon Connect API Reference · Request Body > HistoricalMetrics > SERVICE_LEVEL > UI name · Checked 2026-10-02
13. 13
    A contact answered exactly at the threshold counts as within service level in the Amazon Connect data lake sample query (<=) but not under the GetMetricData LT comparison, so the two can differ slightly at the boundary.inferred

    Reference queries for the Connect Customer data lake · Service level query (<= 20000) compared with GetMetricData SERVICE_LEVEL Comparison LT · Checked 2026-10-02
14. 14
    A single Amazon Connect GetMetricData request can include up to 20 SERVICE_LEVEL metrics, so several thresholds can be pulled at once.

    GetMetricData - Amazon Connect API Reference · Request Body > HistoricalMetrics > SERVICE_LEVEL · Checked 2026-10-02
15. 15
    All Amazon Connect data lake timestamps are UTC and the reference queries bucket contact metrics by disconnect timestamp.

    Reference queries for the Connect Customer data lake · Best practices > Time zones; WHERE clauses of contact and queue queries · Checked 2026-10-02
16. 16
    The Amazon Connect data lake reports contacts transferred out of a queue with separate internal and external transferred-out flags.

    Reference queries for the Connect Customer data lake · Contact and queue metrics > Contacts transferred out · Checked 2026-10-02
17. 17
    Amazon Connect models each agent-customer interaction as an independent contact segment with its own contact record, and a transfer leg is linked to the previous segment by previousContactId.

    Model contact transfers and conferencing in Connect Customer · introductory bullet list before Workflow for warm transfer · Checked 2026-10-02
18. 18
    For Amazon Connect TRANSFER and QUEUE_TRANSFER contacts the InitiationTimestamp is when the transfer was initiated, not when the customer first called.

    Contact - Amazon Connect API Reference · Contents > InitiationTimestamp · Checked 2026-10-02
19. 19
    Five9 describes abandon rate percentage as the share of inbound calls disconnected by customers before reaching an agent, without publishing a formula or threshold on that page.

    What is Abandon Rate Percentage · FAQ What is Abandon Rate Percentage, opening paragraph · Checked 2026-10-02
20. 20
    Genesys Cloud abandon intervals default to column A (Short) under 6 seconds, then B 6-20, C 20-40, D 40-60, E 60-120, F 120-240 and G over 240 seconds.

    Configure contact center analytics options · section Configure abandon intervals · Checked 2026-10-02
21. 21
    Genesys Cloud computes Abandon % as (Abandoned count / Offered count) * 100, where Abandon counts end users abandoning an interaction in a queue.

    Metric definitions · metric rows Abandon and Abandon % · Checked 2026-10-02
22. 22
    Genesys Cloud warns that Avg Talk plus Avg Hold plus Avg ACW does not equal Avg Handle because only some interactions include holds.

    Metric definitions · note near Avg Handle column definitions · Checked 2026-10-02
23. 23
    Genesys Cloud's Include Callback Virtual Wait in SLA option is off by default and, when on, judges callbacks on callback outcomes (reached, not reached, abandoned) using virtual wait from callback offer to outcome.

    service level (glossary) · glossary entry service level, Include Callback Virtual Wait in SLA paragraph · Checked 2026-10-02
24. 24
    Genesys Cloud handle time includes contacting, dialing, talk, hold and after-call work time.

    handle time - Genesys Cloud Resource Center · glossary entry handle time · Checked 2026-10-02
25. 25
    Genesys Cloud counts Answered in the interval when the agent answered but counts Handle in the interval when all of the agent's handle segments including ACW finished, using 30-minute intervals.

    What is the difference between the answered and handle metrics? - Genesys Cloud Resource Center · FAQ paragraph on timing, 10:25 AM example · Checked 2026-10-02
26. 26
    Editing Genesys Cloud contact center analytics settings requires Analytics > Insight Configurations > Edit and Analytics > reportingSettings > Edit permissions.

    Configure contact center analytics options · Prerequisites / permissions block · Checked 2026-10-02
27. 27
    Genesys Cloud defines short abandons as abandons disconnected within an interval set by the organization's short abandon setting, which is group A of the abandon interval configuration.

    short abandons - Genesys Cloud Resource Center · glossary entry short abandons · Checked 2026-10-02
28. 28
    Genesys Cloud's customer short disconnect time, used by the Customer Short Disconnect metric in Flows Performance views, defaults to under 10 seconds and is separate from the 6-second short abandon interval.

    Configure contact center analytics options · section Configure analytics settings, short disconnect time · Checked 2026-10-02
29. 29
    With abandons included, Genesys Cloud service level is (tAnswered − nOverSla) / (tAnswered + tAbandon), so every abandon counts as missing the target.

    service level (glossary) · glossary entry service level, formula for Include abandons · Checked 2026-10-02
30. 30
    Genesys Cloud defines service level as conversations answered within the target time divided by the total conversations included in the calculation, with the included set controlled by configurable options.

    service level (glossary) · glossary entry service level, opening definition and basic formula · Checked 2026-10-02
31. 31
    When flowouts are included, Genesys Cloud counts conversations removed from the queue by a flow action before answer as missing service level, using (tAnswered − nOverSla) / (tAnswered + tFlowOut).

    service level (glossary) · glossary entry service level, flowouts option and formula · Checked 2026-10-02
32. 32
    When short abandons are excluded, Genesys Cloud service level becomes (tAnswered − nOverSla) / (tAnswered + tAbandon − tShortAbandon).

    service level (glossary) · glossary entry service level, short abandons option and formula · Checked 2026-10-02
33. 33
    Genesys Cloud exposes three organization-level service level options in contact center analytics settings: Include flowouts, Include short abandons and Include abandons in calculation.

    Configure contact center analytics options · section Configure analytics settings, Settings tab > Service Level · Checked 2026-10-02
34. 34
    In Genesys Cloud a direct agent-to-agent transfer gives the receiving agent a Handle but no Answered, while a transfer routed through a queue gives the receiving agent both.

    What is the difference between the answered and handle metrics? - Genesys Cloud Resource Center · FAQ paragraph on transfers · Checked 2026-10-02
35. 35
    Webex Contact Center Analyzer's Agent Transfer measure counts inbound contacts an agent transferred to another agent after consult, as the sum of Agent To Agent Transfer Count.

    Webex Contact Center Analyzer Stock Reports · Agent Details report, Agent Transfer row · Checked 2026-10-02
36. 36
    The Webex Contact Center Analyzer Agent Details report computes average handle time as (sum of connected duration + sum of wrap-up duration) / sum of connected count, for inbound calls.

    Cisco Webex Contact Center Analyzer User Guide · Historical Reports > Agent Details, Average Handle Time row · Checked 2026-10-02
37. 37
    Webex Contact Center AHT can differ between the KPI card, Analyzer Agent Details and the Agent Performance Dashboard because the documented formulas differ in whether hold is named and in the denominator used.inferred

    Webex Contact Center Analyzer Stock Reports · Agent Performance Dashboard AHT compared with cisco-help-tajemk-wxcc-analyzer-user-guide Agent Details AHT and cisco-help-63s0bj-wxcc-kpi-cards AHT · Checked 2026-10-02
38. 38
    Webex Contact Center Analyzer reports Conference Count as the number of times an agent initiated a conference call.

    Webex Contact Center Analyzer Stock Reports · Agent Details report, Conference Count row · Checked 2026-10-02
39. 39
    The Webex Contact Center Analyzer Agent Performance Dashboard computes average handle time as (hold + connected + wrap-up durations) / count of contact sessions with termination type Normal.

    Webex Contact Center Analyzer Stock Reports · Agent Performance Dashboard, Average Handle Time row · Checked 2026-10-02
40. 40
    Webex Contact Center Analyzer counts contacts handled for an agent as outdial connected count plus connected count.

    Cisco Webex Contact Center Analyzer User Guide · Historical Reports > Agent Details, Contacts Handled row · Checked 2026-10-02
41. 41
    The Webex Contact Center Total Contacts Abandoned KPI counts contacts terminated in queue before reaching an agent, regardless of handling in earlier queues, and excludes short calls.

    View your contact center KPI cards · KPI Total Contacts Abandoned · Checked 2026-10-02
42. 42
    The Webex Contact Center Average Handle Time KPI card includes connected time and wrap-up time.

    View your contact center KPI cards · KPI Average Handle Time · Checked 2026-10-02
43. 43
    The Webex Contact Center Average Service Level KPI counts contacts that were connected, opted out of the queue, dequeued or terminated in queue within the SLA time as within service level.

    View your contact center KPI cards · KPI Average Service Level · Checked 2026-10-02
44. 44
    Because the Webex Contact Center service level KPI counts contacts terminated in queue within the SLA as within service level, early abandons appear to raise that KPI, the opposite of Genesys Cloud and the Amazon Connect data lake query.inferred

    View your contact center KPI cards · KPI Average Service Level read against genesys-glossary-service-level and aws-connect-data-lake-reference-queries Service level · Checked 2026-10-02
45. 45
    Webex Contact Center's Short Call Threshold is a tenant voice setting in seconds that decides whether a call is short or abandoned, and it defaults to 0 seconds for a new tenant.

    Set up voice settings for Webex Contact Center · Control Hub > Contact Center > Tenant Settings > Voice, Short Call Threshold · Checked 2026-10-02
46. 46
    Webex Contact Center caps the queue service level threshold at 86400 seconds for telephony and chat, 604800 for digital and 1209600 for email.

    System limits in Webex Contact Center · Contact service queues limits, Service level threshold rows · Checked 2026-10-02
47. 47
    In Webex Contact Center the service level threshold is a per-queue advanced setting giving the time a request can wait in queue before being flagged outside service level, and it cannot be set for social channels.

    Create queues and configure routing patterns · section Advanced Settings, Service level threshold field · Checked 2026-10-02
48. 48
    Webex Contact Center's Sudden Disconnect Threshold, defaulting to 30 seconds, decides whether an agent-connected call counts as handled or as ended suddenly.

    Set up voice settings for Webex Contact Center · Tenant Settings > Voice, Sudden Disconnect Threshold · Checked 2026-10-02
49. 49
    Short-abandon defaults differ: Genesys Cloud's short abandon interval defaults to under 6 seconds, while a new Webex Contact Center tenant's Short Call Threshold is 0 so no abandons are treated as short until changed.inferred

    Set up voice settings for Webex Contact Center · Short Call Threshold default compared with genesys-configure-analytics-options Configure abandon intervals · Checked 2026-10-02
50. 50
    The same call traffic can produce different service level percentages on Amazon Connect, Genesys Cloud and Webex Contact Center because their documented treatment of abandons in the formula differs.inferred

    service level (glossary) · service level formulas compared with aws-connect-data-lake-reference-queries Service level and cisco-help-63s0bj-wxcc-kpi-cards Average Service Level · Checked 2026-10-02
51. 51
    A transferred call can count as more than one handled contact on a platform that writes one contact record per leg, such as Amazon Connect, so per-call totals from a migrated platform need stitching by initial contact ID before comparison.inferred

    Model contact transfers and conferencing in Connect Customer · intro bullets on contact segments, read with aws-connect-api-contact-datatype InitialContactId · Checked 2026-10-02
52. 52
    Because Five9 service level drops calls abandoned in queue before the threshold and calls shorter than the minimum time, a Five9 service level figure is not directly comparable with a platform that keeps all offered calls in the denominator.inferred

    Administrator - Setting Key Performance Indicators (KPI) · Speed of Answer threshold and Speed of Answer Minimum Time sections · Checked 2026-10-14

Documents

Cite this page

WarmTransfer. (2026, October 14). How contact center platforms define service level and abandon and handle time differently. WarmTransfer. https://warmtransfer.net/knowledge/contact-center-metric-definition-differences

@misc{warmtransfer-contact-center-metric-definition-differences,
  title  = {How contact center platforms define service level and abandon and handle time differently},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/contact-center-metric-definition-differences},
  note   = {Verified 2026-10-14}
}