Slack Auto-Draft: AI Replies for Internal Help Desk Pings

Your team didn't sign up to run a help desk. But once the company hits a few hundred people, every senior IC has a Slack inbox that looks like one.

A PM gets fifteen "quick questions" a day from sales engineers who couldn't find the spec. A people-ops lead has the same five PTO questions in DM rotation. The CS lead's DMs are a queue of "do we support X?" that someone could answer from the help center.

The setup that breaks

The work isn't hard. It's the interruption that's expensive. Each ping pulls a senior person off their actual job to type the same answer for the third time this week.

The usual fixes don't work:

• "Just point them to the docs." They didn't read the docs the first time.
• "Build a bot." The bot answers in a channel. People still DM you because they trust you.
• "Office hours." Now you have a meeting and a backlog.

What Slack auto-draft does

Slack auto-draft. A reply Runbear writes for you in your Slack inbox the moment a message lands. The draft pulls from your team's connected knowledge sources (Notion, Salesforce, Zendesk, your help center). You review, edit, and send. Runbear never sends on your behalf.

Slack auto-draft watches the messages landing in your Slack inbox, DMs, mentions, thread replies, and writes the reply for you. You read it, edit if needed, send.

The draft uses what the team already knows: your help center, your runbooks, the answers you've given before, the systems you've connected (Notion, Salesforce, Zendesk, Linear, the rest). When the draft is right, sending takes one click. When it's wrong, you fix the angle and ship it. Either way, you didn't start from a blank textbox at 4:47 PM on a Tuesday.

The draft sits in your inbox, not theirs. The reply still comes from you, with your voice, on your timing. Slack stops looking like a queue. It starts looking like Slack.

Who this is for

• CS leads drowning in internal "what's our policy on X?" pings from AEs and CSMs
• People ops answering the same benefits, PTO, and onboarding questions every Monday morning
• PMs and tech leads whose DMs are a permanent help desk for spec questions, integration questions, "where does this live?" questions
• Founders past the 50-person mark who became the answer-everything function by accident

If you'd describe a chunk of your week as "answering things I've already answered," this is the tool.

How it works

1. Connect Slack and your knowledge sources. Notion, Google Drive, Confluence, your help center, your CRM, your ticketing system. Whatever your team uses to store the truth.
2. Runbear watches your inbox. New DM, new mention, new thread reply that needs you. The draft is ready before you open the message.
3. You review and send. Edit one word, send. Edit five words, send. Reject the draft and write it yourself. Runbear learns from what you keep and what you change.
4. Hard questions get escalated, not answered. When the draft confidence is low or the question needs a real decision, Runbear flags it instead of guessing.

What changes

The volume of pings doesn't change; the typing does. Across 30+ teams running auto-draft today, Runbear has prepared drafts for over 25,000 Slack messages since launch. The draft is ready in your inbox before you open the message. Your inbox stops being the bottleneck. The help-desk dynamic that was eating your senior people's afternoons quietly stops happening.

We've seen the shape of an ops lead's afternoon shift inside a week. The same number of DMs land. The time spent typing replies drops to near zero.

You still own the relationship. You just stop typing the same answer twice.

Try it

Try Runbear at runbear.io. Set up takes about ten minutes. If it doesn't reclaim real hours in the first week, you'll know.