{"resourceId":"eab-human-connection-student-success-leaders-survey-20261016","versions":[{"version":"external-57a3753b74334ce8d41db9195b1d2b8147e1423b3c29c862654d7aa7d6d26ed8","resource":{"id":"eab-human-connection-student-success-leaders-survey-20261016","title":"EAB: 75% of student-success leaders want staff interactions to remain the norm; few campuses use AI for retention-gap or early-support identification","organization":"EAB (Education Advisory Board)","sector":"Higher education student success / advising AI strategy (vendor research)","geography":"United States (EAB member/leader survey audience)","publishedAt":"EAB Student Success Blog, 16 October 2026, Tara Zirkel","publicationDate":"2026-10-16","eventDate":null,"sourceName":"EAB Student Success Blog","sourceLabel":"Vendor research blog citing proprietary leaders survey","sourceUrl":"https://eab.com/resources/blog/student-success-blog/how-to-keep-human-connection-at-the-center-of-your-campus-ai-strategy/","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["operating-model","accessibility-workforce","governance-procurement"],"finding":"On 16 October 2026 EAB published guidance based on its 2026 Student Success Leaders Survey: 75% of respondents favoured keeping staff interactions the norm (including 59% who supported AI for routine or repetitive engagements), while 25% cited potential loss of personal connection and 31% privacy or data-security risks as concerns about expanding AI. Only 17% said their institutions use AI to uncover retention gaps in student-success data and 15% to identify students who may need additional support. EAB recommends defining AI-led, AI-informed and human-led interactions, using AI to connect data signals of silent struggle, and making AI agents a door opener to personal support.","sledRelevance":"Published 16 October, this is a current readout of student-success leaders' preferred operating model for campus AI—human-norm with routine AI—and documents low uptake of AI for retention analytics.","evidence":"Proprietary leaders survey summarised by vendor; methods and n not stated in the opened article; no student outcome measures.","architectureImplications":"Interpretation: separate AI-led scheduling/FAQ from human-led counselling; require handoff with context; retention analytics need LMS, advising and tutoring data joins under policy.","governanceImplications":"Leaders want staff as the norm; privacy/security concerns are second only to connection loss—policy should define triggers for human takeover.","securityPrivacyImplications":"31% cite privacy/security risks; chat and early-alert data need clear notices and retention limits.","caveats":"Vendor blog; undisclosed survey methods; Navigate360 promotion; leader perceptions only.","streamIds":["student-success"],"roles":{"sales":"For sales, the framing point is human-norm advising with AI for routine work. EAB reports 75% of student-success leaders want staff interactions to remain the norm, while only 15–17% already use AI for early support or retention-gap finding. Open discovery on escalation design and analytics readiness. Stay bounded: this is a vendor survey summary without disclosed methods or student outcomes, so it cannot prove retention gains from Navigate360 or any chatbot.","engineering":"Engineering's framing point is designing AI-led, AI-informed and human-led interaction classes with reliable context handoffs into advisor queues. Pre-sales should verify intent routing, escalation triggers, advisor consoles and whether any retention analytics join only approved campus data under policy. Proof of value is local handoff completion and advisor time spent on high-judgment cases, not EAB's undisclosed survey percentages or Navigate360 marketing claims alone.","delivery":"Delivery's framing point is operating-model design before launching a student chat agent. Define interaction classes, staff the escalation path, publish privacy notices, then pilot routine AI questions with measured handoffs and advisor feedback. Acceptance criteria below are proposals. Applicability is limited to institutions with advisor capacity to receive escalations; generalisability of EAB's leader survey is unknown because methods and sample size were not disclosed."},"roleDetails":{"sales":{"customerProblem":"Campuses fear AI will erode advising relationships while still needing scale for routine student questions.","stakeholders":["VP student success","Advising directors","Retention committee","CIO","Privacy officer"],"discoveryQuestions":["Which interactions must stay human-led?","What share of chat volume can staff absorb if escalated?","Are LMS and advising data ready for early-alert AI?","How is privacy notice handled?"],"valueHypothesis":"Interpretation: positioning AI as routine-task relief with mandatory human pathways may match leader preferences; outcome benefits are unproven here.","potentialEngagement":"A bounded advising AI design workshop covering interaction classes, escalation and a 60-day routine-question pilot.","unsupportedClaims":["Retention improvement from EAB's model","That 75% preference equals student preference","Product-specific ROI"]},"engineering":{"fit":"Fits CRM/advising platforms that can classify intents, escalate with context and optionally join early-alert features.","architectureIntegration":"Chat agent for routine FAQs/scheduling; advisor summarization; optional retention-signal joins; explicit human handoff.","prerequisites":["Intent taxonomy","Escalation routing and SLAs","Data-sharing agreements for early alert","Advisor console"],"constraints":["Survey methods undisclosed","Vendor conflict of interest","Low current analytics uptake implies data gaps"],"security":"Early-alert and chat logs are sensitive; require purpose limitation, access controls and student notice.","proofOfValue":["Handoff completion within SLA","Advisor-rated context quality","False-escalation rate sample"]},"delivery":{"work":"Map AI-led/AI-informed/human-led interactions, staff escalation queues, and run a routine-question pilot with privacy review.","dependencies":["Student success ops","Advising units","IT/security","Communications"],"ownership":"VP student success with advising directors.","skillsAdoption":"Advisors need training on AI-prepared summaries; students need clear AI labelling and opt-in to humans.","governanceCheckpoints":["Privacy review","Escalation SLA approval","Pilot retrospective"],"acceptanceCriteria":["Proposed: published interaction-class matrix","Proposed: ≥95% of urgent triggers reach a human queue","Proposed: advisor feedback sample on handoff quality"],"risks":["Escalation overload","Students stuck in AI loops","Privacy complaints"]}},"retrievedAt":"2026-10-18T03:15:05Z","enrichedAt":"2026-10-18T03:22:58Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Keeping humans central protects belonging for students who need relationship-based support; workforce must be staffed for handoffs.","procurementImplications":"Interpretation: require AI-to-human escalation, role definitions and privacy controls in advising AI RFPs; do not buy analytics claims without local data readiness.","operatingModelImplications":"Student-success leaders own the AI/staff mix; advisors remain responsible for high-judgment conversations.","sourceVerification":{"openedUrl":"https://eab.com/resources/blog/student-success-blog/how-to-keep-human-connection-at-the-center-of-your-campus-ai-strategy/","referenceExcerpt":"75% of respondents favored keeping staff interactions the norm, including 59% who supported AI handling routine or repetitive engagements","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}