{"id":3591,"date":"2024-04-29T11:41:20","date_gmt":"2024-04-29T09:41:20","guid":{"rendered":"https:\/\/help.ino.cx\/?post_type=ht_kb&p=3591"},"modified":"2025-06-03T16:57:47","modified_gmt":"2025-06-03T14:57:47","slug":"terms-and-vocabulary","status":"publish","type":"ht_kb","link":"https:\/\/help.ino.cx\/index.php\/help-center\/terms-and-vocabulary\/","title":{"rendered":"Terms and vocabulary"},"content":{"rendered":"\n

[Reading time: 3 minutes]<\/em><\/p>\n\n\n\n

Overview<\/h2>\n\n\n

Welcome to the INO cx glossary! This article provides an overview of key terms and concepts used within the INO cx application, including essential vocabulary related to features, functionalities, and key performance indicators (KPIs).<\/p>\n\n\n

\"\"<\/figure>\n\n\n

Whether you’re a new user or looking to refresh your knowledge, this guide will help you understand the terminology you’ll encounter throughout the platform to maximize your experience and effectiveness with INO cx.<\/p>\n\n\n

Interactions vocabulary<\/h2>\n\n\n\n

Diagrams<\/h3>\n\n\n

Here are two diagrams for incoming and outbound interactions, with details of when the waiting, communication and post-interaction times start.<\/p>\n

Incoming:<\/strong><\/p>\n

\"\"<\/p>\n

Outgoing:<\/p>\n

\"\"<\/p>\n\n\n

Interaction<\/h3>\n\n\n

An incoming interaction begins when a customer initiates a call, sends an email, a whatsApp\/messenger\/telegram\/SMS message or starts a new conversation from the chat plugin.<\/p>\n

An outgoing interaction begins when an advisor opens the dial pad on its Banner and clicks on the green button (launch call – start writing an email – start writing an SMS). Campaigns can also automatically start outgoing interactions (voice or SMS).<\/p>\n\n\n

Wait time<\/h3>\n\n\n

The wait time corresponds to the moment when distribution begins, and ends when the agent or customer accepts the interaction.<\/p>\n\n\n

Distribution<\/h3>\n\n\n

Distribution is the passage of the interaction through a queue or campaign (Smart interactions only).<\/p>\n\n\n

Processing<\/h3>\n\n\n

Processing time begins after distribution, when the agent\/customer accepts the interaction. It ends with the start of the post-interaction (if the agent fills in a qualification questionnaire, for example).<\/p>\n\n\n

Post-interaction<\/h3>\n\n\n

Post-interaction starts when the interaction ends: the advisor or customer hangs up, the messaging session closes, etc.<\/p>\n\n\n

Overflow<\/h3>\n\n\n

Overflow<\/strong><\/a> refers to a situation where an interaction (such as a call) cannot be accepted into a queue because certain predefined conditions are met \u2014 for example, the queue is full or no agents are available to handle it.<\/p>\n

When an overflow occurs, the interaction does not enter the queue.<\/strong> Instead, it is automatically redirected based on the overflow strategy that has been configured.<\/p>\n\n\n

Dissuasion<\/h3>\n\n\n

Dissuasion<\/strong><\/a> refers to a rule or condition that forces an interaction to leave a queue after it has already entered it. This can happen, for example, after a certain wait time or based on customer input.<\/p>\n

A dissuasion triggers the interaction to exit the queue it was in.<\/strong>
Once removed from the queue, the interaction will follow the configured dissuasion behavior.<\/p>\n\n\n

Statistics vocabulary<\/h2>\n\n\n\n

ACW<\/h3>\n\n\n\n

After-Call Work (ACW)<\/strong> refers to the tasks that a customer service agent completes immediately after finishing an interaction with a customer. These tasks are essential for wrapping up the interaction and preparing for the next one.<\/p>\n\n\n\n

Examples: updating the CRM card, open a new case, create a task, fill in a qualification questionnaire, etc.<\/em><\/p>\n\n\n\n

Reducing ACW without compromising accuracy is a common goal in optimizing contact center performance.<\/p>\n\n\n\n

AHT or APT (DMT or TTM)<\/h3>\n\n\n\n

Average Handling Time (AHT)<\/strong> [also called Average Processing Time (APT)<\/strong> or TTM in french<\/em>] is a key performance indicator (KPI) in customer service and contact centers. It measures the average amount of time spent handling a customer interaction<\/strong>, including:<\/p>\n\n\n\n

    \n
  1. Talk Time<\/strong>: Time spent speaking with the customer.<\/li>\n\n\n\n
  2. Hold Time<\/strong>: Time the customer is put on hold.<\/li>\n\n\n\n
  3. After-Call Work (ACW)<\/strong>: Time spent completing tasks related to the interaction after it ends.<\/li>\n<\/ol>\n\n\n\n

    Formula \u27a1\ufe0f AHT = (Talk time + Hold time + ACW) \/ Number of interactions.<\/p>\n\n\n\n

    Lower AHT often indicates better performance but must be balanced with quality to avoid rushing customer interactions.<\/p>\n\n\n\n

    ATT (DMC)<\/h3>\n\n\n\n
    \n

    Average Talk Time (ATT)<\/strong>\u00a0is a contact center metric that measures the average duration of time an agent spends speaking with a customer<\/strong> during an interaction.<\/p>\n\n\n\n

    Formula \u27a1\ufe0f ATT = Total Talk Time \/ Number of interactions.<\/p>\n\n\n\n

    While shorter talk times may suggest efficiency, it\u2019s important to balance ATT with call quality to ensure customer needs are fully addressed.<\/p>\n<\/div>\n\n\n\n

    Hold Time (MEA)<\/h3>\n\n\n\n

    Hold Time<\/strong> refers to the duration during which a customer is placed on hold by an agent during a live interaction. This happens when the agent needs to:<\/p>\n\n\n\n

      \n
    • Perform backend tasks like system checks or updates.<\/li>\n\n\n\n
    • Retrieve additional information.<\/li>\n\n\n\n
    • Consult a supervisor or another department.<\/li>\n<\/ul>\n\n\n\n

      QS (SQ)<\/h3>\n\n\n

      QS<\/strong> stands for Quality of Service<\/strong>. It is a measure used to evaluate the overall performance and reliability from a customer’s perspective. This measure focus on the experience of the end user.\u00a0<\/p>\n

      SLA (ANS)<\/h3>\n

      A Service Level Agreement (SLA)<\/strong> is a formal agreement between a service provider and a client that defines the expected service standards<\/strong>, including performance metrics (r<\/strong>esponse time, resolution time, uptime…)<\/p>\n

      Formula \u27a1\ufe0f Number of interactions processed in SLA \/ (Number of interactions aborted + Number of interactions processed) x 100<\/p>\n

      It ensures accountability, reliability, and clear expectations to maintain customer satisfaction.<\/p>\n\n\n

      Other vocabulary<\/h2>\n\n\n\n

      API<\/h3>\n\n\n

      APIs (Application Programming Interfaces) are tools that enable different applications to communicate and share data, without needing to know the internal details of either.<\/p>\n

      How does it work?
      \u2753Request: An application sends a specific request to an API.
      \u2705 Response: The API processes this request and returns the requested information.<\/p>\n\n\n

      SSO Connector<\/h3>\n\n\n

      An SSO (Single Sign-On) connector is a tool that allows users to log in to multiple apps or systems with just one set of credentials (like one username and password). Instead of signing in separately to each app, you log in once, and the connector handles access to everything else securely. It\u2019s like having a master key that opens multiple doors.<\/p>","protected":false},"excerpt":{"rendered":"

      This article will serve as a glossary to explain the terms used in the INO application: when does an interaction start? When does it end and when does the post-interaction begin?<\/p>\n","protected":false},"author":3,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[103],"ht-kb-tag":[],"class_list":["post-3591","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-ino-get-started"],"_links":{"self":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/3591","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/comments?post=3591"}],"version-history":[{"count":13,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/3591\/revisions"}],"predecessor-version":[{"id":5092,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/3591\/revisions\/5092"}],"wp:attachment":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/media?parent=3591"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-category?post=3591"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-tag?post=3591"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}