Service desk, knowledge support, and structured records.
IT operations / Automation / Applied AI
Human-led AI.
Human-led AI.
Practical IT systems.
I designed the underlying IT records, support processes, and knowledge resources—then configured a coordinated team of Grok bots to help maintain them. The work connects Microsoft Teams and Outlook, SharePoint, Excel, Power Automate, and reusable technical documentation, with the human administrator retaining final authority over consequential changes.
Including the coordinator, specialist agents, direct assistant, and test lab.
Isolated workbook trials passed final Excel Desktop verification.
01 / Connected systemsThree practical workflows.
Three practical workflows.
One coordinated approach.
These systems address different needs. I present them together because the value comes from structured information, repeatable processes, and a clear route from an employee request to a human-reviewed result.
01 Implemented / Service delivery
IT ticketing & AI-assisted service desk
I created a Microsoft Forms, SharePoint, and Power Automate ticketing workflow, then extended access to IT assistance through Grok in Microsoft Teams and Outlook. Employees can request help through familiar communication channels, while ticket records and routine notifications support the IT management process.
Explore the IT service desk case study02 Implemented / Employee knowledge
Grok bot, Cody knowledge base & file discovery
After testing Cody AI conversations in Microsoft Teams, I trained a Grok bot that successfully communicated in Teams through a connector and a standard user account. I made organized Cody knowledge resources available to the assistant, including reviewed and implemented SOPs. A script generates a daily shared-drive directory reference to help answer questions about where procedures and files can be found.
Explore the knowledge support case study03 Implemented system / Progressive automation
Asset records, call-queue assignments & specialist bots
I created centralized SharePoint-hosted Excel workbooks for company technology inventory and Voice for Pest phone/queue assignments, including device tags, assignments, employee references, and inventory summaries. I also shared the asset-tracking model for warehouse equipment use. Specialist Grok bots were trained to interpret conversational requests, suggest edits, generate reviewable workbook copies, and later make scoped, authorized updates to live workbooks under human oversight.
Explore the AI operations & inventory case study02 / Delegation modelSpecialized assistants.
Specialized assistants.
Human approval.
I initially worked with the IT Director and Data Manager bots on controlled inventory tasks, then expanded the system into a coordinated specialist team. The hierarchy below is a simplified reconstruction of responsibilities, not a live permissions diagram.
Human IT AdministratorFinal authority · Production approvals · Quality review
IT DirectorTask routing · Bot registry · Verification · Status reporting
SparkDirect personal assistant
Bot LabExperimentation, testing & bot training
Bot responsibilities and approval rules were defined through operating instructions. They should not be interpreted as an independently audited security boundary or proof of technically enforced editing locks.
03 / Engineering & validationTest the change.
Test the change.
Protect the workbook.
My early inventory automation trial focused on preventing apparently successful edits from damaging a complex operational Excel file. The trial used isolated workbook copies before broader authorization was considered.
Documented isolated inventory study61 worksheets · 15,800+ formulas
A conventional Python Excel save could remove three specialized dropdown validation rules. Working with the bots, I developed targeted Office Open XML (OOXML) cell-editing procedures designed to preserve the rest of the workbook.
Four workflows passed isolated testing
Adding devices, assigning assets, transferring equipment between employee profiles, and repairing missing profile formulas. Validation included SHA-256 fingerprints, formula and structural comparisons, dropdown checks, and final human review in Excel Desktop.
What this means: four of six planned modules passed the reported isolated trial. This is not a claim that every module or the specific OOXML publishing implementation was released to production.
01ProposeReview suggested changes
02Test copyCompare a new workbook version
03ValidateCheck formulas, layout, and intended values
04AuthorizePermit scoped production updates after trials
04 / Trust & boundariesAutomation should
Automation should
stay accountable.
I defined operating rules so assistant responsibilities were explicit, consequential changes required my approval, and results were checked before being reported as complete.
Human authority
Account creation, access changes, record deletion, and other consequential production changes require explicit approval from me.
Coordinated editing
One responsible bot per task stage; no competing edits to the same workbook; investigate errors rather than retrying indefinitely.
Evidence & reporting
Track requests, approvals, exceptions, assigned bots, and verification results in a coordinator-led task process.
Security-minded development
Earlier trials incorporated isolated files, data masking, sanitized reports, output checks, and documented recovery or incident procedures.
These reflect described policies and test practices, not an external audit of all production permissions or an assertion that bot prompts alone enforce technical restrictions.
05 / Maturity & next phaseSeparate what's live
Separate what's live
from what's still being designed.
Connected workplace assistance
Centralized service-desk intake, a working Teams Grok knowledge assistant, and scoped bot-managed edits to authorized SharePoint workbooks after progressive testing.
Targeted workbook automation
Four inventory modification or repair modules passed isolated testing and final Excel Desktop verification. Exact cross-environment production adoption of those implementations was not established by the earlier report.
Publish-only SharePoint integration
Microsoft Graph, Office Scripts, Power Automate, and narrowly scoped publishing identities were considered for a specific controlled OOXML publication workflow; no claim that this exact design was deployed.
Privacy and accuracy: All architecture views are conceptual. Real employee identities, asset assignments, phone extensions, internal drive paths, secrets, bot instructions, and production workbook files are excluded. No audited time-savings, universal AI accuracy rate, or zero-failure guarantee is implied.
More documented IT workExplore the
Explore the
underlying systems.
Each linked case study covers the tools, test boundaries, and documented implementation work in greater detail.