From the Student Success edition of October 23, 2026
ASU conference recap: President Crow says virtually all students use AI but fewer than half use the tools ASU provides; presidents describe agents that resolve bursar and financial-aid holds
Arizona State University · Higher education AI strategy, student services agents and AI literacy · Tempe, Arizona, United States
- Publisher
- ASU News
- Original publication
- ASU News, 23 October 2026 (conference 20 to 22 October)
- Source retrieved
- 2026-10-24
- Event date
- 2026-10-21
What happened
ASU News recapped on 23 October its Agentic AI and the Student Experience conference. President Michael Crow said ASU offers 20 AI programmes and has trained more than 4,000 faculty, but that virtually all students use AI tools and fewer than half use the tools ASU provides. On a presidents' panel, University of Tulsa President Stacy Leeds described a system that could check a student's bursar or financial-aid situation and remove a hold, with a person involved only on escalation, and suggested AI could shorten admissions decisions from months to days; Gateway Community College President Amy Diaz described students handling college business with AI on their own time. will.i.am described an ASU course in which students build private personal agents on a platform from his company, framed around data ownership and the lack of AI regulation.
Why it matters
A leader's statement that most students bypass institution-provided AI tools, alongside presidents' plans for agents that act on student accounts, frames adoption and governance questions for student-services AI.
Evidence and measured results
Speaker statements reported by the host institution. No usage data behind the fewer-than-half figure is given.
Limitations and uncertainty
Host-institution coverage of its own event, with a commercial partner of a speaker involved. Statements are not evidence of outcomes.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-24; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Institutions pay for AI tools many students do not use, and want to reduce bureaucratic barriers such as account holds.
- Stakeholders
- CIO or enterprise technology lead
- Bursar and financial aid directors
- Student services leadership
- Provost
- Discovery questions
- What share of students use the licensed AI tools, by group?
- Why do students choose consumer tools instead?
- Which student transactions would an agent be allowed to complete?
- How would agent actions be audited and reversed?
- Value hypothesis
- Interpretation: understanding why students bypass provided tools could improve licence value, and tightly scoped agents could reduce routine office visits.
- Potential engagement
- A bounded adoption assessment of provided AI tools plus a scoping study for a read-only student-account status agent.
- Unsupported claims
- Measured share of ASU students using provided tools
- Admissions decisions in days
- Time or cost savings from hold-removal agents
Pre-sales engineering
Role takeaway
- Fit
- Relevant to institutions with institution-wide AI licences and integrated student information systems.
- Architecture and integration
- Agents integrated with student information, bursar and financial-aid systems, with human escalation; separate personal-agent course platform.
- Prerequisites
- Licence usage telemetry
- Student information system APIs
- Role-based permissions for agent actions
- Audit logging
- Constraints
- Speaker statements only
- Financial and education-record rules
- Host-institution reporting
- Security
- Least-privilege access for any agent touching student accounts, with logged and reversible actions and human approval for exceptions.
- Proof of value
- Measure provided-tool active use from telemetry
- Sandbox tests of hold-check logic
- Permission-boundary tests
- Audit trail review
Delivery
Role takeaway
- Work
- Measure adoption of provided AI tools and scope agent support for routine student transactions.
- Dependencies
- Usage data access
- Bursar and financial-aid owners
- Integration team
- Student input on tool choice
- Ownership
- Enterprise technology with student services and business office owners.
- Skills and adoption
- Staff trained to handle escalations and review agent actions; students given guidance on provided tools.
- Governance checkpoints
- Approval of permitted agent actions
- Privacy review of data access
- Pilot review before write access
- Acceptance criteria
- Proposed: provided-tool active-use rate reported by student group each term
- Proposed: read-only agent pilot completed before any write action
- Proposed: every agent action logged and reversible
- Proposed: escalation path tested with business-office staff
- Risks
- Agents taking wrong account actions
- Low use of paid tools
- Overreliance on speaker claims
- Privacy exposure of financial records
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Agents described as acting in back-office systems (bursar, financial aid holds) with human escalation. Interpretation: write access to student accounts needs authorisation, audit and rollback design.
Governance
Who approves, reviews and stays accountable for outcomes?
Speakers stress responsible use without regulation; the account-acting agent idea raises approval questions not discussed in the recap.
Security and privacy
What data, permissions and controls need testing?
A course platform is described as keeping student agents private; no technical detail is given. Agents that remove holds would handle sensitive financial records.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Crow mentions supporting neurodivergent learners; staff roles shift toward escalated cases if agents handle routine holds.
Procurement
What should contracts, pricing and exit terms secure?
Students' preference for consumer tools over provided ones affects the value of institution-wide licences.
Operating model
Which teams own the service once it runs?
Presidents describe moving routine transactions to self-service agents with human escalation.
Publication history
- 2026-10-23Student Success · Issue 445 resources
Stable resource ID: asu-news-agentic-ai-student-experience-conference-recap-crow-students-not-using-provided-tools-20261023