Skip to main content
Interaction Classification

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

A
Written by Anita Casanovas
Updated over 3 weeks ago

Verbatim

The customer's reason for contacting support, captured in their own words—without internal jargon.

Interaction Classification

OI enhances customer insights by classifying the customer's stated reason for contact using their exact language. Our language algorithms analyze large volumes of interactions, helping organizations better understand customer needs and operational trends.

While each organization has its own customer demand framework or rubric, tailored to its industry and business, interactions generally fall into three levels of classification:

Root Cause of Contact

The fundamental reason the customer reached out—not necessarily the underlying issue. Think of this as the event that triggered the contact; if it hadn't occurred, the customer wouldn’t have needed assistance.

Inquiry

The main topic of the interaction, directly related to the root cause.

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

Sub-Inquiry

A more specific detail about the inquiry, if applicable.

(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, but I didn’t receive a confirmation. I’m calling to check if my order went through."

This interaction could be classified as follows:

  • Root Cause: My order was placed

  • Inquiry: No order confirmation received

  • Sub-Inquiry: Has my order gone through?

Using the full interaction transcript, OI can also predict customer satisfaction and assess whether the issue was resolved.

Did this answer your question?