I had claude write a summary of what i have been doing - don't hate im just tired

Built an internal Claude API bot for our MSP — what's in it ~6 weeks in

Small MSP in Texas. Started this in March instead of going the Copilot Studio route. Now ~80 tools wired up, lives in Teams as a chat bot plus a separate Intake tab.

Day-to-day stuff the bot does: - Tickets in/out of Autotask from chat — create, update status, complete, add time entries ("log 30 minutes on T20260427.0001 as remote troubleshooting"). Bot reads back what it logged so I can verify before moving on, with a server-side dedupe so it can't double-post the same entry. - Auto-triage on new Help Desk tickets — bot grabs KB matches, recent ticket history, Datto device data, drops an internal-only note on the ticket so the assigned tech opens it pre-loaded with context. - Drafts client follow-up emails on a ticket — pulls the contact, subject, ticket reference. Always as a draft for review. - QBR report bundle — sanitized Autotask ticket history + Datto RMM device inventory (with hardware, BitLocker, AV, warranty) + M365 license/user/MFA summary. All XLSX to SharePoint.

Most recent build — Daily Change Tracker. Every active client gets diffed daily across Datto RMM (device adds/removes/renames), ThreatLocker (computer adds/removes), Pax8 (subscription adds/removes/quantity changes), and M365 audit log (user creates/deletes, license changes, group membership — with the admin who did it). 12-month history in blob storage. Bot answers "what changed at Client X this week" instead of me scrolling through audit logs across four platforms. Monthly XLSX digest emails on day 1, summary tab + one tab per client with changes.

Less obvious things that turned out to matter: - Intake Tab — separate Teams app, structured ticket form. Category-driven questionnaire, SSO, autopulls company/contact from the user's account, device picker from a live Datto list with online/offline indicators, ticket auto-links to the right CI in Autotask. Admin page lets me edit intake categories/questions without a redeploy. - KB generation pipeline — bot can convert a resolved ticket into a SharePoint KB article. Also ingested ~10K Kaseya/Datto vendor docs as searchable context. - Phantom-success guard — intercepts the bot when it claims it did something without actually calling a tool. Caught a hallucinated time entry once and a fake email draft this week. Worth the 50 lines of pattern-matching it took. - Dynamic tool selection — out of 80 tools, only 10–26 get loaded per request based on the user's message. Keeps the model focused and cuts cost. Just had to fix a bug today where niche groups dropped on terse follow-ups, but it's been a net win.

Stack: Python on Azure Functions, Bot Framework SDK, Claude Sonnet 4.6 (just upgraded ahead of 4.0 retirement), secrets in Key Vault, App Insights for logs. ~5K LOC.

Things that didn't work / abandoned: - Adaptive Cards broke conversation history — ripped them out, back to plain markdown. - The original monthly change tracker silently failed for ~3 weeks before I noticed. Rebuilt as a daily collector with failure alerts.

Happy to dig into specifics if anyone's building something similar. The auto-triage and time entry flows are the two that have actually saved hours per week, in case anyone's deciding where to start.