Skip to content
Case Study

Speech Analytics: 40+ Call Categories for a Membership Travel Company

A 500-agent contact center, two call studies, and a category framework that replaced 10 wrap codes with evidence



What Is Speech Analytics, and Why Does It Matter?


Speech Analytics processes every recorded call, using phonetic and acoustic pattern recognition to identify what customers are asking for, how agents respond, and what's actually driving volume. Manual quality monitoring reviews a sample, often a very small one. Speech Analytics reviews the population.

That difference in coverage matters more than it sounds. Most contact centers know how many calls they took. Far fewer can say why those calls happened at a level granular enough to act on. Without it, self-service investment, coaching priorities, and staffing decisions all get made from impressions rather than evidence.

Client Opportunity

A large membership retail travel company engaged Andrew Reise to design and build a Speech Analytics program for its 500-agent contact center, which handles millions of member calls a year across cruise, vacation packages, hotels, cars, and air. Andrew Reise began with cruise (the highest-priority and most complex line of business) and delivered the strategic framework for extending the capability everywhere else.

The Challenge

The contact center already had routing infrastructure, a quality monitoring program, and a workforce management function in place. What it didn't have was a reliable answer to why members were calling. Quality coverage ran at roughly 2 calls per agent per 28-day period, enough to spot-check an individual but not enough to see a pattern.

Six to ten wrap codes for an entire business

Agents classified calls using a taxonomy of 6 to 10 manual wrap codes covering every line of business. The categories were too broad to separate distinct call types within a single line, and agent-assigned coding introduced inconsistency that made trend analysis unreliable.

Repeat calls with no known cause

Members calling back on an unresolved issue accounted for 18% of all contact center interactions, more than 73,000 calls. The cost showed up twice: handle time on issues that should have closed the first time, and members who had to ask twice. The root causes were unknown.

Agents on hold with the cruise lines

Cruise carried the highest Average Speed of Answer in the contact center, driven in part by long handle times. Agents were routinely placing members on hold to call cruise lines directly for information or to complete a transaction. The behavior was widely observed but never quantified.

Our Role

Andrew Reise was engaged to build the analytical infrastructure (categories, studies, and framework) that would let the contact center diagnose its own call volume.

Discovery and category design

Structured discovery workshops with contact center leadership established the business context, the existing data, the call driver hypotheses, and what to build first. Those sessions produced the category taxonomy: more than 40 call types across three tiers, covering customer experience signals (repeat calls, confusion, escalation), call drivers common to all lines of business, and cruise-specific drivers for booking, pricing, cabin, dining, and cancellation.

Two call studies

The first analyzed 31,854 cruise agent interactions over one month to quantify agent-initiated calls to cruise lines, documenting 14 minutes and 26 seconds of average hold time per call, 1.61 holds per interaction, and the specific carriers and transaction types driving the behavior. The second isolated 73,144 repeat-call interactions and classified them by underlying driver using speech-detected patterns rather than agent-assigned wrap codes.

Strategic category framework

Andrew Reise delivered a prioritized blueprint mapping the extension of the program from cruise to vacation packages, hotels, cars, and air, with category definitions, build sequence, and the analytical logic for each line of business. The organization owns the roadmap and can run the expansion itself.

Industry
Hospitality

Case Study Attribute
Speech Analytics, Call Driver Analysis, Contact Center Intelligence, VoC Program Design

Results

  • 40+ speech categories built, validated, and activated across the cruise line of business
  • 73,144 repeat contacts (18% of total volume) identified and classified by root cause
  • 14 minutes and 26 seconds of average hold time per outbound cruise call quantified, connecting agent behavior directly to Average Speed of Answer
  • Manual wrap codes replaced by a consistently applied taxonomy that covers every recorded call, not a sample
  • A prioritized expansion roadmap for vacation packages, hotels, cars, and air, so the program extends without starting over

Contact Us

Ready to Find Out Why Your Members Are Actually Calling?

If your call driver data comes from wrap codes and a handful of monitored calls, let's talk about what every call would tell you.

Frequently Asked Questions

What is a Speech Analytics program, and how is it different from call recording?

Call recording captures and stores audio. It doesn't analyze it. Speech Analytics processes that audio using phonetic and acoustic pattern recognition to identify specific words, phrases, emotional signals, and behavioral patterns across every recorded interaction. Recording gives you a library. Speech Analytics means someone has read the books.

How do you design a speech category taxonomy for a complex contact center?

Taxonomy design starts with discovery: stakeholder workshops, a review of existing data, and hypothesis development to map the full universe of potential call types. Categories are then prioritized by business impact and built in sequence, beginning with the highest-volume and highest-impact call types. Each category is defined by a combination of keyword phrases, proximity rules, and speaker attribution logic that captures the specific behavior it represents. The taxonomy is validated through sampling and refined before it's activated at scale.

What is a repeat call, and why does repeat contact volume matter?

A repeat call happens when a customer contacts you more than once about the same underlying issue, usually because the first interaction didn't resolve it. The cost lands in three places: total call volume, agent capacity that could have gone to first-contact resolution, and the member's own experience of having to ask twice. Identifying what's actually causing repeat contacts is the first step toward the process, self-service, and training changes that reduce them.

How does Speech Analytics support agent coaching and quality management?

It makes quality management possible at a scale manual monitoring can't reach. Instead of reviewing 2 calls per agent per period, a speech-enabled quality program can analyze every call for the behaviors and phrases that predict quality outcomes. Supervisors get flagged to the interactions that actually need review rather than selecting calls at random, and coaching conversations are informed by patterns rather than a single-call impression. Over time that produces more targeted coaching and more consistent standards across the agent population.

What is a self-service deflection strategy, and how does Speech Analytics support it?

A self-service deflection strategy identifies which call types can be resolved digitally (website, app, IVR, chatbot) without agent assistance, then designs the changes needed to shift customer behavior toward those channels. Speech Analytics supports it by quantifying call volume by type, surfacing the questions and transactions most suited to self-service, and tracking volume changes after each deployment. Without accurate call driver data, self-service investment tends to go to the channels teams assume customers want rather than the ones they use.

How do you extend a Speech Analytics program across multiple lines of business?

Extension follows the same sequence as the initial build: discovery workshops to surface the call driver hypotheses specific to that line of business, category design and build, call studies to validate category performance, and a prioritized framework for activation. Categories built in the first line of business often transfer. Customer experience categories (repeat calls, confusion, escalation, positive experience) tend to apply universally, while product and transaction categories need line-specific development. A strategic category framework built at program outset is what keeps each subsequent line of business from starting from scratch.

 

 

Want to elevate your business' experiences?

Let's Connect
LOW-AdobeStock_617477667