Are support and service synonymous in your organization? You would be among good company if it were. Many organizations view these business functions as the same. Of the ones that do differentiate, few actually leverage them for the opportunity they offer. Let’s look at the differences.
Support is what product manufacturers do to keep the product running as advertised. It involves repair, maintenance, parts, and all the other work required to keep the machine performing its intended function. Most manufacturers have founded their warranty and contract business on support.
Service is work done for others as an occupation or business. Think of it as anything over and above “keeping the machine running as advertised.” We can call them “Value-added” services.
Many manufacturers confuse the two. I argue their differences are distinct.

By thinking about them separately, the doors to opportunity and growth swing open and many more possibilities exist. Achieving this understanding is the first step to uncovering the strategic potential remote technologies offer.
Let’s illustrate with an example. Are remote software updates a value-added service? Maybe to the manufacturer - it turns out updating software and firmware is a major support cost. But to the customer, it is something they view necessary to keep the equipment running properly. They might even say, “for us much as we paid for this thing, it shouldn’t need any patches.”
I would put remote software updates in the “service efficiency” category under support.
Here is a different example. Let’s say the industry is regulated where the equipment is being used. Let’s say there are laws that require the equipment owner to keep certain records of their operations and these records determine whether they are in compliance or not.
Let’s also say that every once in a while, the “Man” comes and audits those records to ensure compliance. Of course the “man” gives little or no notice of when he is coming. Rude, isn’t he?
For years and years, the equipment owner has made records management a part of daily operations of the business - for better or worse. Consider it a cost of doing business. When the “Man” comes by, everyone drops what they are doing and goes to the basement to sift through years of illegible paperwork hoping they can connect the dots and get out of the audit alive. Meanwhile, the day to day operations get thrown out the window and their customers suffer for it.
Can you smell that? Yep, that’s the smell of opportunity.
Along comes a young enterprising lad and approaches the equipment owner. He says, “Mister, let me take that burden of records management off your shoulders and I’ll make sure you’re ready for all your inspections from here on out.” The equipment owner is intrigued. “In fact”, he says in somewhat cocky manner, “We’ll keep an eye on things and if we see something that could lead to a compliance problem, we’ll let you know about it before it is a reportable problem.”
Ahh, the beginning of a valuable partnership.
At this point, the equipment owner is seeing visions of actually focusing on customers (patients in this case), operational excellence, quality assurance, being able to do more with less, trumpets, angels, and doves…all the makings of a value-added service.
You might be asking yourself at this point, “What does this have to do with remote service?” Well, as it turns out in this case, and this case happens to be the health care industry, many of the records necessary for regulatory compliance can be remotely monitored and stored by the equipment manufacturer. And, they can be stored is such a way that they are within fingertip reach if the “Man” happens to stop by.
If you are an equipment manufacturer, I bet you wish you were having these kinds of conversations with your customers (if you’re not already).
Support is vital to the services story. In most cases, remote support will be the way a manufacturer gets their foot in the door so they can be in a position to sell Services. Keeping the concepts separated, and that means how you package and offer them, is how you can make double word score in the market. That is, achieve both the cost savings potential of remote support and the revenue generation of remote service.
Now there you have it - the difference between support and service.
4 Responses
Tom Ellwood
02|Apr|2008 1From my perspective, support is really just a subset of a vast array of services which can be positioned with a customer. Product support groups many times fail to see the bigger picture since the concept of value-added services is the domain of another organization; Professional Services.
Basically, there needs to be a shift in thinking which brings the the services and product support organizations together. The emphasis needs to change from supporting your respective product to supporting your customer’s business. After all, isn’t that why the customer purchases a product; to drive their business. The more a services organization can do to contibute to the success of their customer’s businees; the greater impact they will have on creating a barrier to the competition.
Historically, remote activities were focused primarily on product support and was essentially a method of reducing support costs. Thus, were considered to be a ‘Support Tool.’ Today, the technologies enable us to do much more; however, the Professional Services groups have yet to exploit the benefits of this platform to deliver a braoder suite of services. This will only happen when product support and professional services begin to coalesce around the need’s of the customer; not the needs of their respective product.
JohnH
03|Apr|2008 2The professional services group at my company reports up to a separate department. Too many things would have to change to get them working with the support group. They would not see the point.
Jim Pendergast
15|Apr|2008 3My experiences are that Support and Services are two distinct entities, and should be kept separately. Support is generally a post deployment/product acquisition activity, where they play the role of customer advocate, solve customer problems, and allow the customer to use the product as it was designed to be used. Services drive activities that enable the customer to use the product (deployments), along with activities that allow the customers to use the product in a more efficient/optimized/customized manner (VAS). Support is measured by customer satisfaction and are generally positioned as cost centers, while Services are measured by margin and revenue, and are profit centers. Public school versus Parochial school. From an industry standpoint, albeit unfair, support is sometimes looked at as “the guys in the white hats who rescue the day”, while services are the “guys in the black hats” that just focused on the almighty dollar. Certainly not my perspective, but you’ve all heard it before. I’ve been in hybrid support organizations that were profit centers based on incoming M&S revenue, and were measured on profitability. When upcoming quarterly revenue looked thin, Value Added Services were designed and implemented. Suddenly customers were confused, and the group they once looked at as their advocate suddenly became “services driven”. Customer Satisfaction and Customer Loyalty suffered. My view is keep Support and Services separate entities, and maintain the clear perspective of “who does what” from the customer.
Tom Ellwood
30|Apr|2008 4Jim,
I understand your perspective; however, how the support and services groups are aligned from an organizational perspective should not raise barriers to collaboration between the teams. Each should be focused on maximizing the value they deliver to the customer. Granted their success criteria (margin dollars for PS or cost avoidance for support) may differ but customer loyalty is the end result for both groups.
My major point here is that as long as companies view remote capabilities as the domain of product support, it will not capture the ‘hearts and minds’ of the executives. There needs to be a linkage which demonstrates how these technologies can be applied to both organizations. For example, assume the PS organization used the remote support technology to deliver consulting services or performance and tuning services from a remote facility vs. being onsite. Now the technology is not just being leveraged for remote support; rather, it is viewed as a mechanism for remote services (Smart Services). This is a more compelling business case.
Value-added services are not intended to be a short term fix for revenue shortfalls, they need to be a component of an overall customer support and services strategy aimed at meeting customer needs. I can see where customers would get confused with a slew of new services being thrust at them.
I would also add that the role of the support organization should be expanded beyond break/fix efforts to problem prevention. To the extent that remote technology is an enabler, the greater the customer’s perceived value of the support effort overall. I understand this is dependent upon the company’s overall philosophy on the role of product support
Leave a reply
Search
Subscribe by Email
Recent Posts
Recent Comments
Archives
Links