"Social Documentation" -- Cool but Problematic
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.
Sponsored
About Tom Johnson
I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, agent skills, tech comm careers, and more. Check out my AI courses for more on the latest in AI and tech comm. If you're looking for info about documenting APIs, see my API documentation course.
If you're a technical writer and want to keep on top of the latest trends in tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me.
Finally, I want to note a couple of things. I usually write the first drafts of my posts myself and then use AI to improve accuracy, clarity, and detail in places, so my writing is a mix of human and AI. (Hopefully that's not too off-putting.) Also, the opinions I express on my blog are my own perspectives, not those of my employer.