The Rules of Supporting Customers Where and When it Matters
Think about a bad product experience. It probably ended with multiple phone calls that led to nowhere, leaving you frustrated. When customer support does not fulfill expectations, businesses generate detractors that are very hard to recover. Great overall support does not only enhance customer experiences, but it also improves business economics, both directly (e.g., faster resolution times) and indirectly (e.g., more propensity to buy and recommend your brand). Therefore, it is paramount for any organization to build a solid Customer Support Use Case that drives great experiences.
The following are a few rules TechTorch follows when building great Customer Support Use Cases:
1. Omnichannel support: First, make sure to engage with customers wherever and however they prefer to be supported. At a store, on the phone, via chats or email, checking social media…
More importantly, offer a consistent experience across all your channels.
2. Self-service: With customers becoming more comfortable with technology, we see huge growth in self-service support. Therefore, businesses must provide clear and easy-to-use self-service features: how to learn about a new product, how to resolve issues, how to change or buy more plans, how to provision new services, etc. Great self-service experiences increase satisfaction, generate revenues, and decrease costs. However, self-service capabilities are not simple to achieve as they not only require a well-structured customer portal, they also include self-diagnostic tools embedded in the product and a very well thought set of experience workflows.
3. Consistent customer view and experience: All areas of a business that interact with customers need to have access to the same consistent information. That requires support systems orchestrated and well-integrated into other capabilities such as Customer Success (refer to “The Subtle art of customer success”). In the same way, the support experience needs to be consistent across all channels. For example, users should not need to change their identity or credential depending on the means for contact.
4. Centralized knowledge: If customer information needs to be orchestrated, so does the information required to support those customers. A knowledge database and common diagnostic tools are exceedingly important so that the front-line can perform their job quickly and effectively.
5. Technology-enabled: The support organization must be enabled with suitable front-end and back-end tools. These tools include purposed-build contact center software, as well as robust ticketing systems that are able to route, recommend and orchestrate fast resolutions. Further integrations into deeper back-end systems (e.g., customer databases, monitoring tools, etc.) make it easier to diagnose and solve issues.
6. Clear expectations and SLAs: Support levels need to be clearly identified up-front when customers purchase services or sign contracts. For example, customers who buy SaaS software expect a baseline level of support with recurring payments. However, there might be an additional level of support that requires premium payments. Again, ensure consistency on what it’s agreed to versus what is delivered.
There is nothing better than a satisfied customer. And satisfaction is built every time a customer successfully engages with your business. So, make sure you have the right Customer Support capabilities. TechTorch can help you get there!
Eleifend ac scelerisque proin imperdiet enim. Ete luctus cursus elit, suspendisse ullamcorper. Eget condimentum eget pellentesque neque nisl. Mattis massa vestibulum etiam in aliquet vitae duis cursus.
Blandit et at nec sed et nunc, ut ullamcorper. Suspendisse amet, ultrices suspendisse id urna eu netus interdum. Vitae pharetra, laoreet arcu massa fames. Tempus dolor euismod et vitae sit ut fames. Eleifend ac scelerisque proin imperdiet enim. Et luctus cursus elit, suspendisse ullamcorper. Eget condimentum eget pellentesque neque nisl. Mattis massa vestibulum etiam in aliquet vitae duis cursus.
Nunc, cras luctus nulla suspendisse felis. Lectus urna, eu, in lobortis. Quis in arcu urna, nulla luctus aenean congue donec. Consectetur vulputate amet, orci, sit interdum consequat. Quis tincidunt egestas vitae a, elementum amet. Dis elementum donec duis varius libero sed.accumsan, amet. Aliquam nibh at amet, sollicitudin. A et arcu, diam cras neque, dignissim euismod. Gravida ultrices maecenas et risus. Non nisl accumsan blandit leo adipiscing ornare molestie. Massa pharetra, pulvinar orci tristique ipsum nec.
Static and dynamic content editing
“Mi integer sit feugiat bibendum et eget in lorem. Nullam odio adipiscing augue in quis. Viverra semper.”
How to customize formatting for each rich text
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
- Amet, arcu etiam fringilla ut.
- Amet, arcu etiam fringilla ut.