the docs answer it. they ask in slack anyway.
i'm content side, not devrel, but the slack pattern looks the same. four people a day asking where the api keys live. three asking what the rate limit is. it's all in the docs. the docs are not the problem.
the problem is that people ask in slack because asking in slack is faster than reading. and replying to all of them yourself is how you end up not writing anything else that week.
a few months back we set up a system where a bot reads the docs and drafts a reply in-thread. the bot doesn't send. whoever is on rotation that day reads the draft, edits it if it's off, and hits send. response time stays human. the typing-out-the-same-thing-for-the-12th-time tax goes away.
what surprised me: the drafts being visible to the team turned into a docs gap detector. when the draft was wrong, that usually meant the docs were wrong or missing. we started fixing the docs instead of just answering the question. inbox got quieter over a few weeks.
curious how other devrel folks handle this. do you let a bot draft, or do you keep it fully manual? has the docs-feedback loop worked for you, or does it mostly stay noise?
writeup on the setup if it helps: https://runbear.io/use-cases/slack-auto-draft-internal-help-desk?utm_source=reddit&utm_medium=social&utm_campaign=slack-auto-draft-internal-help-desk