I hadn't heard of the term "social documentation" before, but it describes the Twitter responses, video replies, and other social media formats that support centers use to provide responses to technical problems customers ask about. This post by LugIron shows an example of a video response. The problem with social documentation is that, if it's not incorporated into the documentation, the support center will have to respond again -- and again and again. So while it may seem powerful and make the customer feel like a king, a better solution that benefits the rest of the customer base would be to update the documentation (and perhaps include a video in the documentation) and send the customer that link. Maybe they're already doing that.
Get new posts delivered straight to your inbox.
I'm a technical writer based in the California San Francisco Bay area. Topics I write about on this blog include the following technical communication topics: Swagger, agile, trends, learning, plain language, quick reference guides, tech comm careers, and certificate programs. I'm interested in information design, API documentation, visual communication, information architecture and findability, and more. If you're a professional or aspiring technical writer, be sure to subscribe to email updates using the form above. You can learn more about me here. You can also contact me with questions.