Public

How to calculate 'Cost Savings' within a Community

Khoros Oracle

costsave.png

In my previous article, I spoke about the most common value levers that we can measure within an Online Community in order to evaluate what the Community is doing for the business.  More often than not a stakeholder within an organization wants to know, “is this darned thing making me money or is it saving me money?”  I can never begrudge anybody with such a question that spent money on Khoros software and allocated employees to their Community endeavor.  In fact, I always want to do my best to answer these types of questions.  

It turns out that a majority of our Community customers (around 60%) are primarily looking to save money, and so it is often the case that I do the calculations and subsequently explains that the Community is saving them money.  There are, of course, exceptions.  If the Community is not successful, then that is a bigger problem, and so I do not really talk about what the Community is doing for the business, but rather, what the business is leaving on the table when they do Community incorrectly.  But even the Communities that do not have ‘saving money’ as their primary objective end up with a little bit of Savings anyway.  Why?  Because we are living in an era where people prefer to digitally self-serve.  When somebody solves their own problem by reading a knowledge-base article or peer-to-peer discussion, then that self-service *potentially* deflects a contact to their Customer Support center.

There is nothing new about people resolving their own issues with a brand’s products or services.  Have you ever heard of the team ‘shadetree mechanic’?  Back in the day when cars were a lot more simple, a great number of regular people knew how to fix them, and those folks could do it in a few hours (or minutes!) under the shade of a tree.  Time marches on though, and so much of the world has become more complex.  

For me, the peer-to-peer Community has always represented a light in this complex darkness.  No matter what I was interested in, there was a Community for it.  And within those Communities were subject-matter-experts that could help answer my questions on any arcane subject.  Better yet, I would commonly find that somebody else had already asked my question and that these subject-matter experts had already answered it.  The treasured knowledge, which had been delivered over a year ago unto a poor sap with a problem identical to mine, was now sitting right there for me to learn from.  Eureka!

But let us now make sure we really understand the mechanics of how a conversation saved money.  If a dialogue around somebody asking a question on a peer-to-peer Community is answered by another more knowledgeable peer, that is great.  Potentially, an inquiry to the brand’s Support team was avoided.  But the real action is in how that particular answer lives on in perpetuity within the Online Community.  In the field of self-service, the biggest cost savings are not found in the number of Accepted Solutions on a Community (i.e. - the Direct Contact Deflection of one person answering another), but rather in the subsequent views of those Accepted Solutions over time by large amounts of people that use the Community in an anonymous and passive manner (i.e. – Indirect Contact Deflection).  So it is not ask-and-answer where the magic happens.  It is in the ask-and-answer being viewed hundreds, thousands, or tens of thousands of times.  Some have called this a ‘force multiplier effect’.  Let us now examine it.  

The formula to measure the mechanics of traffic, interactions, and your business, looks like this: 

# of Visits to the Community during a given timeframe

% of Visits seeking support

% of Visits that are 'seeking support' who resolve their issue (aka - 'Resolution Rate')

% of those that were ‘seeking support’ and have successfully ‘resolved their issue’ which would have contacted Support if they had not solved their problem via the Community

Multiplied by the Average Cost-per-contact to the Support Center 

(NOTE - use the 'Fully Burdened' cost per contact)

= Gross Savings

So a savings story might look something like this....

5,000,000 Visits to the Community in 1 year

70% of those Visits were seeking support

40% of those 'seeking support' Resolved their issue

50% of those that were 'seeking support' and have successfully 'resolved their issue' would have contacted Support if they had not solved their problem via the Community

X $12 cost per contact

= $8,400,000 in (gross) savings

For the more visually inclined, here is a picture of the same formula (with the same numbers) in action:

JakeR_0-1619059953153.png

Measuring savings can be done on a weekly (or even daily!) basis, but our recommendation is to run the formula annually or, if it suits your business, quarterly

Though not required, it is recommended that the Khoros ‘Value Analytics’ survey be enabled on the Community.  This survey asks the precise questions in the exact order of the formula.  It is both included in the platform and an extremely non-fatiguing survey experience for the Community Visitor.  Although the questions in our Value Analytics survey cannot be customized, our Value Analytics survey feature has the necessary flexibility to accommodate 3 important contexts;  where it is served on the Community, when it is served on the Community, and to whom it is served on the Community

Though a brand may run their own survey (we have no problem with that!), be mindful of extraneous questions that are not relevant to the Community experience, much less the self-service experience.  When left to their own devices, brands run surveys too quickly in the customer experience and/or they simply do not ask the right questions.  The results are either an extremely low survey completion rate, or worse, a survey full of reactive (i.e. ‘mean spirited’) responses.

This is how you measure ‘Contact Deflection’ Savings in an Online Community.  Easy, right?

⬅️ Previous

Discovering Business Value within a Community

Next âžĄď¸

How to calculate 'Member Spend' within a Community

17 Comments