Your technical support philosophy is losing money and angering customers
summary
Argues that shifting support from firefighting to an ambassador model increases retention and reduces churn, showing GiveWP’s results: advertised 2–4 business hour first reply and average 3–5 day resolution, plus many five‑star reviews. Describes practical tactics: replicate bugs in WP Sandbox, craft cross‑team “all y’all” tickets to involve theme/host developers, and use a crew checklist (confident, results‑driven, educational, welcoming) so first‑line reps solve or escalate cleanly rather than repeatedly passing blame.
AI-written summary · about
chapters (14)
- 0:00Introduction and personal story
- 3:56Old school support philosophy
- 8:31Flaws in old school support
- 16:59Building the all y'all team
- 19:03Ambassadors and empowerment
- 21:55Ambassadors as problem solvers
- 23:22Winsome communication in support
- 24:23The CREW tone guide
- 34:38Ambassadors deliver news effectively
- 37:06Customer trust and respect
- 39:14Creating raving fans
- 40:07Q&A collaboration with other teams
- 42:34Support in marketing and sales
- 44:43Discipline and post-mortems
