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
For QA managers, coverage is the name of the game. That means fewer show-stopping issues — and less damage control for your support team. Beef up your self-help documentation, supporttraining, and videos with step-by-step processes and specific use cases from real-world customer testers. QA Managers.
These can be challenging to quantify in monetary terms and include improvements in internal business processes leading to increased productivity or improved customer service , to name just a couple. Why is it important to calculate the ROI of a software system?
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. “Sure those accounts did well, but were they going to do well anyway?”. Sure adoption went up, but wouldn’t that happen naturally?”.
It is important to note that, contrary to its name, customer service problem-solving is not just about fixing customer complaints. Main Reasons : Varying levels of supporttraining. Different support team structures. Solution : Start by providing consistent training and resources to service reps across all platforms.
Have we named things correctly? That includes fully tested software, documentation, pricing/packaging, part numbers, marketing assets, targeted lead gen, competitive intelligence, supporttraining, problem escalation, partner/channel materials, etc. Goal: See if sample users can complete a task. What inputs are we missing?
What does a leader of Customer Success, Professional Services, Support, Training, etc. What’s In a Name? Just a week earlier, David Sakamoto , Vice President of Customer Success at GitLab, had a similar thought from the “post-sales” perspective: I’ve written about this quandary in the past. use as a title ?
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