A Tenant Chatbot Built in 2 Hours for a Shared Office: Claude Code Built the Slack Bot, It Answers First and Hands Water Leaks to a Person
- Level Intermediate
- Setup1–3 hrs (estimated)
- Evidence Some evidence
- CostNot stated in source
- No-codeNo
What they did
A shared-office owner in Tokyo has one employee running three locations, handling tenant messages, equipment trouble and viewings. He used Claude Code to build a Slack app that gives tenants a first reply. He wrote the rules himself: if this kind of message comes in, reply like this; if that kind comes in, report it to this channel in this format. Anything the bot can't answer, like a water leak, goes to a person. He also wants a summary of each day's inquiries every morning, and he'd already built a way to message all tenants at once. After a test run he planned to roll it out to about 40 tenant companies. He expects it to save the employee 1 to 3-4 hours a day (his estimate, not a measured result).
How it went
X post by the owner (Oct 30, 2026): Japanese shared-office operator; Claude Code built the Slack app and the system; owner wrote the reply and reporting rules; bot gives the first response and routes what it can't answer (e.g. water leaks) to a person; bulk message feature built Oct 22; daily morning summary planned; test run before rollout to about 40 tenant companies; 1 to 3-4 hours a day saved is his expectation, not a measured result
Worth knowing
- X post by the owner (Oct 30, 2026): Japanese shared-office operator; Claude Code built the Slack app and the system; owner wrote the reply and reporting rules; bot gives the first response and routes what it can't answer (e.g. water leaks) to a person; bulk message feature built Oct 22; daily morning summary planned; test run before rollout to about 40 tenant companies; 1 to 3-4 hours a day saved is his expectation, not a measured result.
Prompt
Cleaned version rewritten from the source — not a direct quote.
Build a Slack bot that answers tenant messages for my [business type] at [locations]. Use these reply rules: [list of message types and how to answer each]. If a message is about [urgent issues, e.g. water leaks, lockouts, broken equipment] or anything you can't answer from the rules, don't guess: post it to [#channel] in this format: tenant, location, issue, time, what they asked. Every morning at [time], post a short summary of yesterday's inquiries to [#channel]. Before going live, let me test it with sample messages.
Recommended
Try it in Grok Bot
- Copy the prompt (button below).
- Open Grok Bot chat and paste it. Replace any [bracketed] placeholders.
- Connect the listed tools (Slack) as connectors when Grok Bot asks.
- If the task repeats, ask: "Make this a daily routine."
Alternatives: the same prompt works in Claude Code, Claude, ChatGPT Agent, OpenClaw.
Set it up
Tools: Slack · Stack: Claude Code
- Read the original source for full context.
- Connect the tools your agent needs.
- Paste the prompt and replace [bracketed] placeholders.
- Run once manually and check the output before scheduling it.
Generic suggested steps, not from the source.
Evidence
X post by the owner (Oct 30, 2026): Japanese shared-office operator; Claude Code built the Slack app and the system; owner wrote the reply and reporting rules; bot gives the first response and routes what it can't answer (e.g. water leaks) to a person; bulk message feature built Oct 22; daily morning summary planned; test run before rollout to about 40 tenant companies; 1 to 3-4 hours a day saved is his expectation, not a measured result
Source: X · 2026-10-30 · Verified by us: not yet · Report broken or outdated