Skip to content
Agentguiden.no
Submit

Collect bug reports from customer Slack channels in one place

A software founder noticed his developers were being pulled into more and more shared Slack channels with enterprise customers. Every customer has its own channel with questions, feature requests and the occasional bug. With Claude Code he built a simple bot in a few minutes that scans the customer channels several times a day for possible bugs. When it finds one, it forwards the message to a central escalation channel and tags the right developers.

Done with Claude CodeModerate

This is a public report, not advice from Skatteetaten, NAV, Altinn or an accountant. Check figures, deadlines and decisions against the original.

What was done

A software founder noticed his developers were being pulled into more and more shared Slack channels with enterprise customers. Every customer has its own channel with questions, feature requests and the occasional bug. With Claude Code he built a simple bot in a few minutes that scans the customer channels several times a day for possible bugs. When it finds one, it forwards the message to a central escalation channel and tags the right developers.

How to do it

  1. Paste the prompt into the tool, and replace the text in brackets with your own.
  2. Read the answer through. Do not send, delete or publish anything until you have seen it yourself.
  3. Check the original before you trust a figure, a name or a date.

Try it with Claude Code

Build a simple Slack bot that reads our shared customer channels several times a day. Look for messages that may be about bugs or technical problems, not ordinary questions or feature requests. Forward each one to [central channel] with a link to the original, and tag [developers]. Never reply to customers yourself. Run it for a week first where you only log what you would have sent. You are done when I have approved the matches.

Replace text in brackets with your own.

Read the original

@LukeWarrd on X ·

More examples

  • Make a sale plan and buyer list for a company

    Pat Simmons asked Dots, OpenAI's always-on agent, to help sell the laser printer repair company run by Simmons's father. It built a website with the sale plan: buyer shortlist, what transfers, price, sales process and the first 30 days. It also made a spreadsheet of 136 potential buyers, each with a fit score, and will check in with the father weekly. Simmons does not write that any buyer was contacted or that anything sold, but the plan is ready.

    DotAI for Mortals ·

  • Track staff work hours with n8n, Telegram and Google Sheets

    A convenience store owner in Poland built a system with n8n, Telegram and Google Sheets where six employees log shift start and end. They can also see shift information and correct mistakes. If something is entered wrong, the flow stops until it is fixed, and the employee and the owner get a message. It has run for about three months. Schedules are still made by hand, and the time saved is not measured, but the owner notices a lighter workload.

    n8nn8n Community ·

  • Build sales demos with the prospect's own data, no developers

    From OpenAI, the company behind Codex. According to OpenAI, the COO of a small fleet software company now builds four to six custom demos a month in Codex without knowing how to code. Each demo takes 30 to 45 minutes and uses the prospect's own data. The company estimates this saves 40 to 60 engineering hours a month and moves 50 to 60 percent more deals past first contact. The figures are the company's own estimates.

    CodexOpenAI (the company behind Codex) ·

Five agents a day

A short email each morning with five concrete examples of what people use AI agents for. Each example links to its source. You can unsubscribe at any time.

You will first get an email to confirm the address.