---
name: slack-unanswered-questions
description: "Hourly on weekdays: questions in your support and shared customer channels that have had no reply for 2 hours, with a link to each. Use when the user asks for this, or when it runs on a schedule."
---

# Slack unanswered questions

Hourly on weekdays: questions in your support and shared customer channels that have had no reply for 2 hours, with a link to each.

In a shared Slack Connect channel, an unanswered question is visible to the customer and to nobody on your side who happens to be busy. Internal support channels have the same problem: everyone sees the question, and everyone assumes someone else has it.

Once an hour during the working day, the agent reads the channels you list, picks out messages that ask something, and checks whether anyone other than the person asking has replied in the thread. Anything older than two hours with no answer goes on one card, with a link straight to the message.

## Two ways to get the data

Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used.

## Route A: API or MCP server

### What you need

- A Slack app you create in your own workspace, with the `channels:history`, `groups:history` (for private channels), `channels:read` and `users:read` scopes, added to each channel; its bot token in `SLACK_BOT_TOKEN`. A Slack connector works too.
- The IDs of the channels to watch, and the hours and time zone of your working day.

If something is missing, say what and stop; do not invent numbers.

### Steps

1. **Read recent messages** (Slack): For each channel ID you list, call `conversations.history` with `oldest` set to now minus 24 hours and `limit: 200`, following `response_metadata.next_cursor`. Skip messages with a `subtype` (joins, channel events) or a `bot_id`.
2. **Spot the questions**: Treat a message as a question when it contains a question mark or starts with how, why, what, when, can, could, does, is or any. In Slack Connect channels, look up the author with `users.info`: people from the other company have a different `team_id`.
3. **Check for an answer** (Slack): A question is answered when `reply_count` is above 0 and `reply_users` includes someone other than the asker, or when a teammate reacted with an emoji you name, such as `eyes` or `white_check_mark`. Use `conversations.replies` when you need to see who replied.
4. **Keep the old ones** (Slack): Keep unanswered questions whose `ts` is more than 2 hours old, and get a link to each with `chat.getPermalink`.
5. **Ask who takes them**: Post one action card with each question's channel, asker, wait and link, and ask who picks them up. When nothing is waiting, post the same `item_key` as an update that says the channels are clear, so the ask goes away.

## Route B: the browser

### What you need

- Signed in to Slack in the workspace that holds the channels, as a member of each channel on the list (private and Slack Connect channels only show to members).

If something is missing, say what and stop; do not invent numbers.

### Steps

Start at https://app.slack.com/client. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.

1. **Open each watched channel**: Slack opens on the last workspace; switch to the right one if you have several. Open each support and shared customer channel on your list in turn and scroll back to messages from the last **24 hours**.
2. **Pick out the questions**: Treat a message as a question when it contains a question mark or starts with how, why, what, when, can, could, does, is or any. Skip app and bot posts and join messages. In Slack Connect channels, hover over the author: people from the other company carry that company's name next to theirs.
3. **See whether anyone answered**: A question is answered when its thread (the **replies** link under the message) has a reply from someone other than the asker, or a teammate reacted with the agreed emoji, such as eyes or white_check_mark. Open the thread when the reply count is not enough to tell who replied.
4. **Keep the ones over 2 hours old**: Hover over the timestamp to read the exact time; keep unanswered questions posted more than **2 hours** ago. Use the message menu, **More actions**, then **Copy link**, for each one.
5. **List them**: Channel, who asked (and their company in shared channels), the question in a short quote, how long it has waited and the link. Then ask who picks them up.

Note: Scrolling back through busy channels is slow, so this route suits a handful of channels. Slack search (`in:#support after:yesterday`) narrows the list but cannot filter on thread replies, so each candidate still has to be opened.

## The report

- **Waiting questions**: each with channel, who asked, how long it has waited and a link.
- **The ask**: who picks them up.
- A clear card when nothing is waiting.

## Post it to Briefkin

When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on.

```bash
[ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env
curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \
  -H "authorization: Bearer $BRIEFKIN_TOKEN" \
  -H "content-type: application/json" \
  -d @- <<'JSON'
{
  "v": 1,
  "event_id": "slack-unanswered-questions/<date of this run, e.g. 2026-10-16>",
  "item_key": "slack-unanswered-questions",
  "project": "Acme",
  "source": "Slack unanswered questions skill",
  "kind": "action",
  "title": "4 customer questions waiting over 2 hours",
  "summary": "Four questions across **#support** and two shared customer channels have no reply from anyone on the team. The oldest has waited 5 hours.",
  "action": {
    "request": "Who should pick these up?",
    "options": [
      "I will",
      "Ping the on-call engineer",
      "Ping #support-team",
      "Leave until tomorrow"
    ]
  },
  "widget": [
    {
      "type": "Table",
      "props": {
        "columns": [
          "Channel",
          "Question",
          "From",
          "Waiting"
        ],
        "align": [
          "left",
          "left",
          "left",
          "right"
        ],
        "rows": [
          [
            "#ext-contoso",
            "\"Is the EU data residency option live yet?\"",
            "Contoso",
            "5 h"
          ],
          [
            "#support",
            "\"Does the API rate limit reset per minute or per hour?\"",
            "Fabrikam",
            "3 h 40 min"
          ],
          [
            "#ext-wingtip",
            "\"Can we add a second admin without buying another seat?\"",
            "Wingtip",
            "2 h 50 min"
          ],
          [
            "#support",
            "\"Any idea why webhook retries stopped last night?\"",
            "Tailspin Toys",
            "2 h 10 min"
          ]
        ]
      }
    },
    {
      "type": "Links",
      "props": {
        "items": [
          {
            "label": "Open the #ext-contoso question",
            "url": "https://acme.slack.com/archives/C07EXT0001/p1760596200001100"
          },
          {
            "label": "Open the oldest #support question",
            "url": "https://acme.slack.com/archives/C05SUP0001/p1760600400002200"
          }
        ]
      }
    }
  ]
}
JSON
```

Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report.

## Run it on a schedule

Suggested: Hourly, 9:00 to 18:00 on weekdays (`0 9-18 * * 1-5`). From cron, with the agent signed in on that machine:

```bash
0 9-18 * * 1-5 claude -p "Run the slack-unanswered-questions skill"
# Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run
```

Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/slack-unanswered-questions#schedule

Source: https://briefkin.dev/skills/slack-unanswered-questions
