IT spends its day answering the same questions in Slack. How do I get on the VPN, where do I request a license, who approves new software. Each one is a small interruption, and together they bury the work that actually needs a person.
sonnet4 daysSlackOpenAINotionConfluence
Claude
92ROI
74Scale
$4k91Saved
ROI for
README.md
Why this subagent
IT spends its day answering the same questions in Slack. How do I get on the VPN, where do I request a license, who approves new software. Each one is a small interruption, and together they bury the work that actually needs a person.
This bot answers from your internal knowledge base, linking the source page so people trust the reply and can read more. When something is not documented, it opens a ticket instead of guessing. The repetitive questions resolve themselves in the channel, and IT gets its focus time back.
How it runs
Used at step 01 to kick off the pipeline.
Write
Used at step 01 to kick off the pipeline.
WebFetch
Used at step 01 to kick off the pipeline.
WebSearch
Used at step 01 to kick off the pipeline.
Search the internal knowledge base in Notion and Confluence for the relevant procedure.
pending
Answer with the steps and link the source page so the asker can verify.
pending
Open a ticket for the IT team when the question falls outside the documented playbooks.
pending
Sample output
json
// Sample output
// (generated when the pipeline finishes)
Answer an internal IT question from the knowledge base, citing the source page; if undocumented, return a ticket draft instead.
Unlock the rest
The full agent definition, install snippet, and starter task are gated for community members.
Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.