All Collections
OI Definitions
Interaction Classification
Interaction Classification

This article explains the methodology for classifying interactions including what is a Root Cause, Inquiry and Sub Inquiry

B
Written by Brent Fitch
Updated over a week ago

Verbatim

The stated reason for contacting in the customer’s own words. Not in ‘internal language’.

Interaction classification

Operative Intelligence powers insights by classifying your customer’s stated reason for making contact in the customer’s own words. This can be applied over a large volume of interactions using language algorithms to help organizations understand their customers needs and operations.

While each organization will have it's own customer demand rubric which is tailored to your industry and business, interactions are generally grouped into three layers of classification:

Root Cause of Contact

The underlying reason for making contact with the organization, not necessarily the underlying issue. Think of this as the antithesis of the interaction: if this didn’t happen, the customer would not have needed to contact you.

Inquiry

The main topic of the interaction, specific to the root cause.

(Note: If your organization is based in Australia, New Zealand or the UK, this will be spelled 'Enquiry')

Sub Inquiry

The next layer of detail about the topic (if applicable). Specific to the inquiry.

(Note: If your organization is based in Australia, New Zealand or the UK, this will be spelled 'Sub Enquiry')

Example

A customer calls and says “Hi, I placed an order online about ten minutes ago, I didn’t receive any confirmation so I’m calling to find out if the order has gone through”.

This interaction could be classified as follows:

  • Root Cause: My order was placed and

  • Inquiry: No order confirmation was received

  • Sub Inquiry: Has my order gone through

Based on the full interaction transcript Operative Intelligence can also predict for customer satisfaction and resolution of the interaction.

Did this answer your question?