This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
You need thorough test coverage before release — that is, you need to see how your product’s features and functions perform with real customers in their actual environments. Taking shortcuts and cutting corners leads to unpleasant surprises down the road in the form of low star ratings, skyrocketing support costs, and hundreds of RMAs.
In The Book of Why , the author, Pearl, talks about the near-impossibility of the “counterfactual”—namely, analyzing what would have happened in the alternate decision path. As in the drug industry, CS teams could run an A/B test. They could perfectly separate out a set of accounts upon which to test an intervention (e.g.,
It is important to note that, contrary to its name, customer service problem-solving is not just about fixing customer complaints. Also, regularly test the system for ease of usability and accessibility. Main Reasons : Varying levels of supporttraining. Different support team structures.
Support needs installation guides, training sessions, FAQs, bug reporting categories. These (of course) don’t exist yet, since we’re still concept-testing problem statements and feature/function and technical requirements. Here is one set of replacements: “Problem validation” or “Concept test” ( NON-REVENUE ). Sound Byte.
We organize all of the trending information in your field so you don't have to. Join 96,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content