Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Contact Reason

The main reason a customer contacted support, tagged by the agent from a fixed, defined list so volume and other service metrics can be read by cause.
AnalyticsconceptUpdated

Definition

A contact reason is the category that records why a customer got in touch: a parcel has not arrived, an item is the wrong size, a charge looks wrong, a booking needs changing. Agents choose it from a fixed list, usually at the end of the contact, so each contact carries exactly one main reason. The list itself, sometimes called a set of reason codes, is the shared vocabulary that makes the counts comparable from agent to agent and month to month.

The reason is not the root cause. The reason is what the customer asked about, described in their terms; the root cause is why it happened, such as a courier delay, an unclear size guide or a confusing invoice line. Agents can record the reason reliably on every contact. The cause usually needs investigation across many contacts, which is why the tutorial on tagging support contacts by reason keeps the two apart and works out causes only for the largest reasons.

What a good reason list looks like

A list that produces usable numbers tends to share a few traits:

  • Written in the customer's words, so agents recognise the contact quickly rather than translating it into internal jargon.
  • Short enough to choose from without scrolling, with a second level only where it sends work to a different owner.
  • A definition and an example for each reason, kept next to the tag field, so borderline contacts are tagged the same way by everyone.
  • A rule for "other", read each month so that recurring themes become reasons of their own.
  • An owner and a change log, so that a reason that is split or merged does not silently break the trend.

In practice: reading metrics, saved replies and fixes by reason

Metrics. The guide to customer service metrics reads every metric by contact reason. A team can answer delivery questions quickly and struggle with billing questions that need another department; a reason with many repeat contacts points to an answer or process that does not work, and a reason with a high contact rate points to a page, an email or a promise that leaves customers unsure. That second kind is often marketing's to fix.

Effort. The guide to reducing customer effort uses the reason list as one of its main sources, because many reasons are effort in disguise: a question about where an order is often means the customer had to chase, and a question about changing a booking often means a missing self-service route.

Leaving. The guide to designing the cancellation experience writes the exit survey's options in the same wording as the support team's reason list, so exit reasons and contact reasons can be read together in one review.

Answers. The tutorial on building a library of saved replies starts from the contact reasons, turns each into the questions customers actually ask under it, and names each reply by reason and question so agents can find it mid-conversation.

Illustrative example — not a real result

A coffee pod subscription finds its largest reason

Skemparn Coffee Pods had never tagged its support contacts. For one month, agents chose one reason from a list of nine at the close of each of the 1,140 contacts the team handled. The largest reason, at 410 contacts, was changing the date of the next delivery, which customers could only do by writing in. The second, at 180, was where an order was. The product team added a "move my next delivery" option to the account page. Two months later, the same reason accounted for 95 contacts out of 820, and total contacts per active subscriber had fallen with it, while the order-tracking reason was unchanged.

Contact reasons give the Contact Rate its meaning: the rate says how often customers need help, and the reasons say why, so each reason can carry its own rate. When the same wording is used for exit surveys, reasons for contact can be set beside the reasons behind Churn Rate, showing which problems customers raise before they leave. And reading reasons by type of customer, new or long-standing, high value or occasional, is a form of Segmentation that shows whether a problem belongs to one group or to everyone.

Common confusions

  • The contact reason is the root cause. It records what the customer asked about; the cause is found later by investigating the largest reasons.
  • More reasons give more insight. Agreement between agents falls as a list grows; a short list applied consistently beats a long one applied loosely.
  • A contact can carry several reasons. One main reason per contact keeps the counts adding up and the trend readable.
  • The list can be edited freely. Splitting or merging reasons without a change log breaks comparisons with earlier months.
  • Contact reasons are a support team matter. Many of the largest reasons trace back to pages, emails, offers and promises that marketing owns.

More terms to look up

Where this term is used

Related