Claws
Ready-made claws for your agent to run
Watch vendor status pages
-
Watches your stack vendors' status pages every 15 minutes -
Maps each incident to your surface area and suppresses the irrelevant ones -
Hands over a ready-made customer-facing acknowledgement -
Drops resolved incidents and stays silent when nothing affects you
Cluster support tickets
-
Clusters the day's inbound support mail by underlying issue every morning -
Flags new bugs spreading across customers and release-driven spikes -
Attaches volume and tone to each cluster with a routing read -
Sends nothing on quiet days
Draft support template updates
-
Compares which templated responses are used for which topics each week -
Flags templates heavily edited every send and topics with no template -
Catches templates that no longer match the product surface -
Drafts the proposed change so the team edits, not authors
Watch public product questions
-
Watches the product subreddit, Stack Overflow tag, and Hacker News every 4 hours -
Surfaces unanswered questions and questions carrying wrong answers -
Ranks by audience reach and your published position on the topic -
Never posts anything; the team chooses what to answer
Digest known issues
-
Builds a daily known-issues digest from ticket patterns, vendor status, and the open-issue file -
Updates each ETA from engineering status notes in the drive -
Removes resolved issues automatically so the digest stays current -
Flags what is ready to publish to a public known-issues page
Catch stale knowledge base articles
-
Cross-references KB articles against recent releases each week -
Pinpoints stale screenshots, renamed UI labels, and changed API parameters -
Surfaces the specific line to fix, not a generic this-is-old signal -
Stays silent when nothing has gone stale
Draft incident follow-ups
-
Reads the incident log and builds a per-customer follow-up brief each evening -
Drafts the impact acknowledgement, remediation, and any applicable SLA credit -
Deprioritizes customers who already acknowledged it and escalates the un-updated -
Sends nothing to customers; the team reviews and sends
Catch FAQ drift
-
Compares recurring ticket clusters against the published FAQ each week -
Flags stale, hard-to-find, or wrong answers that keep getting asked -
Surfaces topics that have become FAQ-worthy but are not on the page -
Drafts an updated answer for each so the docs team edits, not authors
Catch support escalations
-
Watches inbound threads hourly for the language that precedes an escalation -
Catches going-public, contract, and leadership-contact signals early -
Surfaces each the same hour with full context and customer tier -
Drops closed threads and stays silent on quiet hours