So You’ve Released A WordPress Product…. Now What?
summary
Three concrete steps define post‑release support: pick a consistent tone of voice (formal or informal, humor, sentence length), choose a scalable platform (slack for routed alerts, help Scout, kayako or Zendesk for tickets), and write rules of engagement (hours, refund/discount policy, when to say no). Open GitHub issues to feed devs, run regular ticket reviews, document transfer steps before hiring support, and use Help Scout templates for reply examples; forums work only with active moderation.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:17How are we going to communicate
- 3:32What language will we use
- 3:55Tone of voice
- 5:35Platform
- 6:01Scalability
- 7:21Rules of Engagement
- 7:37Having a backup plan
- 8:32Take a deep breath
- 9:14Forums
- 11:29WordPress Forms
- 13:34Communication
- 14:59Communicating
- 16:03Whitelabel options
- 17:05Help Scout
- 18:00Transition
- 18:38Ticket Reviews
- 21:18Take Over Support
