Scaling Support Systems
summary
Shopify frames support as a deliberate system that reduces customer effort and raises loyalty, citing data: about half of merchants use support, two thirds report moderate‑to‑high effort and high‑effort contacts are twice as likely to generate negative word‑of‑mouth. Practical moves: adopt KCS (knowledge‑centered support) so frontline interactions create reusable knowledge, use Zendesk backbone with tools like speech analytics, and form a product support network to link support with devs. Operational lessons: start 24/7 only when ready (Shopify did in 2014), add languages cautiously (email‑first in 2017), and measure value not call time.
AI-written summary · about
chapters (29)
- 0:00Introduction to scaling support
- 1:13Defining support systems
- 2:37Customer effort and loyalty
- 5:44Designing a learning system
- 6:27Support interaction continuum
- 8:12Deliberate system design
- 8:33Self-help resources
- 9:16Hours of operation
- 9:58Language support
- 10:40Channel selection
- 12:27Technology-enabled blur
- 13:29Customer segmentation
- 14:10Tooling for support
- 15:14Tracking and recording
- 15:56Proactive support
- 16:17Measuring support value
- 17:01Case study on metrics
- 19:08Key takeaways
- 19:52Q&A: Conversion impact
- 20:54Q&A: Capacity and motivation
- 22:20Q&A: Failure interactions
- 23:45Q&A: Profitability mistakes
- 24:49Q&A: Expertise maintenance
- 25:50Q&A: Team success metrics
- 26:54Q&A: Dev-support contact
- 28:18Q&A: Building structure
- 29:00Q&A: Tech team impact
- 29:41Q&A: Pricing support
- 30:22Q&A: Hiring support staff
