The college's Board of Trustees got its first look at the tool on the evening before WWNY's November 5 report. The name may not be final.
What JCC says Ask Jefferson does
Brian Topping, the college's Arts and Humanities chair, has been designing the tool. He calls it "a tool, not a crutch." WWNY reports that it is powered by Microsoft Copilot and pulls from JCC's internal data. It answers questions ranging from course availability to dining options. It is meant to give students facts rather than opinions.
Topping's pitch is about reducing friction. He says a lot of student anxiety comes from not knowing who to ask, or from being afraid to ask for help. An assistant that has all the information could help with that.
The examples point to a campus help-desk role, not a general-purpose tutor. The coverage doesn't describe it as one.
The service gap it targets
JCC President Dan Dupee hopes the tool can fill a gap in service, particularly on weekends and late at night. WWNY quotes Dupee as saying the college is staffed roughly "8 to 5, 8 to 6 most nights."
JCC's own technology services page lists help desk hours of 7:30 a.m. to 7 p.m. Monday through Thursday and 7:30 a.m. to 5 p.m. on Friday during fall and spring. It lists weekends as closed. That page covers the IT help desk, not every student-service office, so it doesn't contradict Dupee. It does show the weekend gap he describes.
Pilot timeline
- Next week: Some students will get access to Ask Jefferson. That means roughly the week of November 9, 2026.
- Who tests it: Topping says he is picking candidates who will try to break it. He wants a sample large enough to cover everything a student might eventually need help with. No numbers have been given.
- General release: If testing goes well and problems are fixed, the plan is to roll it out for general use in JCC's spring 2027 semester. That is a target, not a commitment.
What we don't know
The reporting leaves out most of the details an IT administrator would ask about first. None of these gaps suggests JCC lacks controls. They simply haven't been made public.
- Which Copilot product? The report doesn't say which Microsoft Copilot product or licensing tier is used, or which model or hosting setup.
- Which data? "Internal data" is vague. JCC runs a student portal, a records system called SOAR, student email on Microsoft's hosted service, and the Brightspace learning platform. Nothing indicates Ask Jefferson can see private student records, and readers shouldn't assume it can.
- Accuracy safeguards: "Facts, not opinions" is a design goal. It isn't a measured result. The report gives no word on source citations, refresh frequency, or handling of outdated or conflicting information.
- Privacy and access: The report doesn't cover sign-in method, prompt retention, whether prompts are used for training, accessibility, or escalation to a human.
- Success criteria: No pilot size, budget, error-rate targets or launch date have been published.
Student-facing Copilot setups can differ in important ways. Thomas Jefferson University, an unrelated institution, notes on its AI guide that employees signing in with university credentials get enterprise-level data protection. It also says students don't have a protected version of Copilot and can't access employee-built agents. That is another school's policy, not JCC's. It does show why the licensing and identity details matter when an institution builds a student-facing agent.
A bounded comparison: Jeffie, 2019
JCC has tried after-hours AI support before. In 2019 it launched "Jeffie," an AI texting chatbot developed with AdmitHub. The college said the bot had an answer roughly 80 percent of the time. A response team handled anything it couldn't answer. The college also reported 628 questions in its first week.
Those numbers describe a different tool with a different vendor, channel and admissions focus. They are not a forecast for Ask Jefferson, and Ask Jefferson shouldn't be called an upgrade of Jeffie. The history does show the college has experience measuring unanswered questions and routing them to staff. A pilot that logs misses and gaps would fit that approach.
What to watch
- Pilot findings: Does JCC publish what testers broke and how those problems were fixed?
- Data boundaries: Does the assistant stay with public and institutional information, or does it eventually touch personal records?
- Human fallback: After hours is when a wrong answer on deadlines or financial aid is hardest to correct, so a clear escalation path matters.
- Spring 2027 decision: Whether the general release happens as planned will show how the pilot went.
Bottom line
This is a small, early-stage story with a concrete Microsoft angle: Copilot built into a student-services workflow at a community college. The verified facts are a staged pilot starting next week, a conditional spring 2027 target, and a stated goal of factual, college-data-based answers. Most technical and governance questions are still open, so any claim about accuracy or privacy would be premature.