andrewlengly.com/campus-it-casestudy :: campus it triage agent case study
# A Salesforce Service Cloud backend for a campus IT agent. It tries a known-issue guide first and opens one Case when a person is needed.
designed page ......... /campus-it-casestudy
THE SHORT VERSION
Campus IT Triage Agent is a Salesforce Service Cloud backend for a help desk agent that tries a known-issue guide first and opens a Case when it is needed. A chatbot that only searches a FAQ opens duplicate tickets. This one is built as five Apex actions for an Agentforce agent, and it is public on GitHub with 29 test methods. the problem ........... Campus IT desks get the same requests every shift. A chatbot that only searches a FAQ opens duplicate tickets and can’t show what it settled. what i did ............ Built five Apex actions an Agentforce agent can call, with routing and response times kept in Custom Metadata. Every action writes a row to an audit object that a trigger keeps append-only. where it stands ....... Public on GitHub with 29 test methods. The chat layer isn’t in the repo, and the walkthrough video is a reconstruction. kind .................. Case study · Build role .................. Developer year .................. 2026 tools ................. Salesforce DX, Apex, Service Cloud, Agentforce, Custom Metadata what it does .......... A Salesforce DX and Service Cloud app that triages campus IT requests. the question .......... How should a campus IT request get routed, and who can check the decision later?
THE PROBLEM
# A campus IT desk answers the same requests every shift. The repo’s README opens with the problem. Campus service desks get WiFi, password, MFA, VPN and Outlook requests every shift, and hardware that needs a technician waits behind work a script could finish. A chatbot that only searches a FAQ makes that worse. It opens duplicate tickets, and nobody can prove whether it deflected anything. The backend here is built around those two failures. where the problem is stated The README # Who runs it service desk lead ..... Owns the known-issue articles and the rules for queues and response hours. technician ............ Works Cases in the Campus IT app. agentforce admin ...... Owns the topic instructions and which actions the agent can call. platform owner ........ Handles deploys and tests, and assigns the permission set.
WHAT IT DOES
# Five actions, and each one does a single job. # The five actions find a guide .......... Matches the request against six known-issue articles. A match returns the steps, and no Case is opened. escalate a ticket ..... Opens one Case on the queue for its category and links the student’s Contact. The Case carries a published comment and a first-response due time. add an update ......... Adds a comment to an open ticket. A closed ticket is refused, and the agent is told to open a new one. check status .......... Looks a ticket up by Case Number, and falls back to Student ID when the number is wrong. operations snapshot ... Reports the open agent-sourced tickets, how many are high priority, the oldest wait, a count for each queue and today’s deflection rate. # Two behaviors built in one ticket per problem An open Case for the same student and category is reused. Force New Ticket overrides that. lookups that survive speech A Student ID given as s 1000-0001 is stored as S10000001, and Case Number 1234 matches 00001234.
HOW I BUILT IT
# I built the backend first, then checked the walkthrough against the code.
# All six commits on main, in five steps
01. First build
The backend and all 29 test methods in one commit
Tagged: Release v1.0.0, with an 80-second explainer video
02. Public repo
A packaging guide and launch copy
A script for recording after a deploy
03. Demo video
A page rebuilt to look like the workspace
No network calls, and every agent reply scripted
04. Honest labels
The opening caption had called it a live desk
Added: “UI walkthrough · not a live org capture” on every caption
05. Audit, written down
Nine steps, starting with claims the code doesn’t back
A voice check the launch post passed
The label stays on screen for all 65 seconds of the walkthrough, and the README says the
same.
source ................ The pull request that fixed the labelsTHE QUESTIONS
# The snapshot answers what a desk lead would ask.
How many agent-sourced tickets are open?
measure ........... Open Cases with Agent Sourced checked
read from ......... Case
How many of those are high priority?
measure ........... Open agent-sourced Cases at High priority
read from ......... Case
How long has the oldest one waited?
measure ........... Whole hours since the oldest open ticket was created
read from ......... Case
Which queue is holding them?
measure ........... Open tickets counted by the queue that owns them
read from ......... Case and its queue
What share of today’s requests ended in chat?
measure ........... Deflection rate
read from ......... Campus IT Interaction rows created todayHOW IT WORKS
# This repo is everything the agent can do, minus the conversation.
# The path a student request takes
01. Find a guide
Keywords matched against the catalog
Steps read back to the student
02. Escalate
Reuse an open Case or insert one
Stamp Agent Sourced and the due time
Publish a Case Comment
Route to a Campus IT queue
Only when: The guide is missing, already tried, marked for escalation, or the student
asks for a person
03. Update and status
Comment on an open ticket
Look up by Case Number or Student ID
04. Snapshot
Open load by queue
Today’s deflection rate
Every action: Writes one Campus IT Interaction row
Each action is one Apex class with a single invocable method that takes a list and returns
a list. All five run with sharing.
The project deploys as Salesforce DX source on API version 64.0. The conversation is built
in Agent Builder inside an org, so it isn’t in the repo.THE MATH
# Deflection is the share of today’s requests a guide settled. # Deflection today deflection rate ....... guides matched today / guides matched today + new tickets created today A reused ticket counts as a follow-up and stays out of the bottom line. The rate is a percent to one decimal place, and it stays empty on a day with no volume. # Open load open load ............. open Cases with Agent Sourced checked, for the whole desk or one queue oldest wait ........... whole hours since the oldest of those Cases was created # First response due high .................. 4 hours after the Case is created medium ................ 16 hours low ................... 40 hours no matching rule ...... 16 hours These are clock hours added to the moment the Case is created. Nights and weekends don’t pause them, and changing a rule leaves open tickets as they were. # Priority from what the student says high .................. the urgency mentions critical, emergency, urgent, high, p1, p2 or sev1 low ................... the urgency mentions low, or the codes p4 and sev4 Everything else is Medium, including a request with no urgency given.
WHAT IT FOUND
# One test checks the deflection rate, and two of its rules go untested. # Test methods by class on main, 29 in all ticket escalation ..... 15 ticket status ......... 4 audit service ......... 3 ticket update ......... 3 self-service guide .... 2 demo data ............. 1 operations snapshot ... 1 Counted from the code, since no test run is on record. The snapshot test checks the rate against one mix of matched guides and new tickets. No test puts a reused ticket in that mix or runs the snapshot on a quiet day. source ................ The snapshot test
WHAT’S STAGED
# The walkthrough video is a reconstruction, and it says so on screen. The repo carries a 65-second walkthrough of the Campus IT workspace. It mirrors what the Apex does and was not captured from a live org. The README says so, and the video is labelled on screen. Any count that appears in the video belongs to the reconstruction. Every figure in this study comes from the code and the metadata. # In the repo apex .................. 15 classes. Five actions, two shared services, a demo data seeder and seven test classes. metadata .............. Four custom objects and metadata types, holding 14 Custom Metadata records. Five queues take the routed Cases. workspace ............. A Lightning app, a Case layout, list views and one permission set. demo data ............. A script that seeds three demo students, one for each walkthrough path. # Not in the repo the conversation ...... The Agentforce topic is built in Agent Builder inside an org. The repo carries the instructions to paste in. a live recording ...... No capture from a real org exists here. A script for recording one is in the docs. an install link ....... The README keeps a placeholder for a package URL and says not to invent one. a test run ............ No test result or coverage figure is recorded.
DECISIONS
# The rules live where an admin can change them. agent copy stays in agent builder A desk lead can change the wording with no deploy. rules in custom metadata Queue routing and response hours change in Setup with no Apex. So does the article catalog. one action, one job ... Each class takes a list and returns a list in the same order, so it stays safe in bulk. the audit never blocks a student Audit writes run in system mode and catch their own errors. A logging failure can’t fail the action a student is waiting on. append-only by trigger A trigger rejects every update and delete on the interaction object, so the numbers can’t be edited afterward. tests bring their own data No test uses SeeAllData. Test queues are named CIT_Test_* so they can’t collide with the shipped ones. no hardcoded ids ...... Queues are found by DeveloperName, and no Salesforce record ID appears in the code or the metadata. no secrets ............ The project needs no API keys and no OAuth client. Deploying takes the Salesforce CLI and one permission set.
DESIGN
# Technicians get a workspace that works without the agent. campus it app ......... A Lightning app for Cases, Contacts, Interactions and their due dates. case highlights ....... An optional Case layout puts Student ID and first-response due in the highlights. list views ............ Four of them. Two cover Cases and two cover the interaction log, with one scoped to today for a shift review. interaction numbers ... Each audit row carries an autonumber in the form INT-00000.
WHERE IT STANDS
# The code is public, and no run in a real org is on record. agent actions ......... 5 test methods in 7 test classes 29 custom metadata records 14 known-issue articles 6 The repo is MIT licensed, with release v1.0.0 and six commits on main. The first is from August 2026. Two pull requests are open, and one of them adds more tests and a one-command scratch org setup.
WHAT’S NEXT
# First, it needs a run in a real org. # Next tests in an org ....... Run the seven test classes in a scratch org and publish the coverage figure. An open pull request adds a script that sets one up and runs every test with coverage in one command. more tests ............ The same pull request adds tests that push 200 records through every action in one transaction, and one for the empty rate on a quiet day. A test with a reused ticket in the rate still needs writing. open decisions ........ Writing those tests turned up 13 issues, each listed in the pull request for a decision. In one, nothing decides which queue wins when two routing rules match. a live capture ........ Record the walkthrough from a Developer Edition org with Agentforce enabled. Then the on-screen label can come off. business hours ........ Work out first-response due times with BusinessHours.add() against the desk’s Business Hours record, so nights and weekends pause the clock. a classifier .......... Keep keyword matching as the floor and add a classifier above it for requests worded another way. # Known limits no run on record ...... The repo records no test run or coverage figure. Nothing in it shows a deploy to a real org. a reconstructed video The walkthrough is a labelled reconstruction. The script for recording a real one is in the docs. agentforce needs the right org A standard Developer scratch org doesn’t have Agentforce. The chat demo needs a Developer Edition org or a Trailhead Playground. clock hours ........... First-response times ignore business hours. keyword matching ...... Guides match on keywords from the catalog. A request worded another way finds no guide and goes to escalation.
TL;DR
built ................. A Salesforce Service Cloud backend whose campus IT agent tries a known-issue guide before it opens a Case. found ................. Of the 29 test methods, one checks the deflection rate, and two of the rate’s rules go untested. # by the numbers 5 ................... Agent actions 29 .................. Test methods in 7 test classes 6 ................... Known-issue articles the catch ............. No test run is on record. The 29 test methods are counted from the code. next .................. Run the seven test classes in a scratch org and publish the coverage figure.
LINKS
open campus it triage agent github.com/AndrewLengLy/Campus-IT-Triage-Agent read the architecture notes github.com/AndrewLengLy/Campus-IT-Triage-Agent/blob/main/docs/archi… release v1.0.0 ........ github.com/AndrewLengLy/Campus-IT-Triage-Agent/re… (explainer video) the developer side .... /machine/developer the analyst side ...... /machine/analyst
# end of /machine/campus-it-casestudy. andrew.leng.ly@gmail.com · leave machine mode