One AI operator for your team and your clients.
Clankee runs internal ops in Slack / Discord, and sits in shared rooms with customers. Skills and gates stay with you.
5-minute setup. No card to start.
#delivery
Maya @Clankee prep standup
Team already aligned. Standup skipped.
#acme-shared
CustomerJordan · Acme @Clankee status on OAuth?
Blocked on your callback. Rest of invoice export shipped Tue. Checkpoint Thu 11 ET.
How it works
Operator inside the company. Front door for the account.
- 01
Skills
Standup, changelog, client updates: encode once, run without a re-brief.
- 02
Scope
Read-only first. Write access per channel. Customers never see internal tools.
- 03
Gates
Writes, sends, and posts wait on a human. Destructive work never runs alone.
- 04
Learn
A one-off that works becomes a standing skill the next time it shows up.
Skills
Internal and customer work, same agent.
| Skill | Replaces | Time | Who |
|---|---|---|---|
| Standup synthesis | Manual check-ins | 15–20 min/day | Internal |
| Customer Q&A | Paging a PM for status | Always-on in shared chat | Customers |
| Client status updates | PM compiling recaps | 20–30 min/client/week | Customers |
| Sprint blocker digest | Scanning stuck threads | 10–15 min/day | Internal |
| Release notes | Hand-written changelog | 30–45 min/release | Internal |
Customers
They @mention Clankee. You still own the send.
Shared Slack or Discord with the account. Status, FAQs, and next steps from live tickets. Recaps wait for a human before they post.
- Answers grounded in that client’s sources only
- Internal channels stay invisible
- Outbound recaps stay behind approve
Same operator
Company-wide or per client. Different skills, not a different product.
Businesses
Internal ops
Standup prep, blocker digests, and silence when the team is already aligned.
Product shipping
Draft release notes from Linear and GitHub. A human still hits post.
Customer-facing
Put Clankee in a shared Slack or Discord with the account. They ask. It answers from live work.
Agencies
Per-client rooms
Each client channel gets its own skill set and integrations. No leaked context across the book.
Delivery + CS
Status, blockers, and kickoff FAQs in the same thread the client already uses.
Compounding skills
The fourth weekly recap should not need a re-explain. Save the pattern.
Gates
Customers can ask. They cannot ship.
Read-only answers go out. Recaps, tickets, and data changes wait on someone on your team.
- Target system
- Linear · Core App
- Action
- Create issue “Fix Safari Checkout Error”
- Priority
- Urgent (P1)
Access
Tight scope is what makes customer chat safe.
- 01
Start read-only
Index and answer before anything can write.
- 02
Scope per channel
A customer room does not inherit GitHub write from #engineering.
- 03
Approve outbound
Customer recaps and data changes wait on your team.
- 04
Review the log
See what ran, not only when something goes wrong.
Not a chatbot. Not a stack you babysit.
| Chatbot | Self-host | Clankee | |
|---|---|---|---|
| Interface | One-off Q&A | Your own infra | Skills in Slack / Discord |
| Customers | Not in the room | You wire it | Shared channels, scoped answers |
| Writes | Copy-paste yourself | You own the blast radius | Native approval gates |
FAQ
Start with one skill. Keep the gate on.
Internal ops and customer rooms. Flat-fee plans available.