Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Student Success edition of October 11, 2026

Vendor claimEmergingUndated source

Morehead State University launches Beaker Chat, an EdSights SMS student-engagement bot for retention, with staff review of conversations

Morehead State University (Office of Retention); EdSights · Higher education student success / retention outreach chatbot · Kentucky, United States (regional public university)

Publisher
Morehead State University news
Original publication
Morehead State University news, October 2026 (URL path; no exact on-page date)
Source retrieved
2026-10-12
Read original source

What happened

Morehead State launched Beaker Chat, an SMS student-engagement platform powered by EdSights, as part of its retention strategy. It sends reminders about deadlines, resources and academic milestones, answers common questions on registration, financial aid and support services, and lets staff review conversations and respond directly when students need more help. The university says it will help identify student needs before they become barriers, and that students can opt out at any time. No usage, accuracy or retention data are reported.

Why it matters

A new October 2026 U.S. retention-office deployment of an SMS check-in bot, arriving the same month as student pushback over a similar unannounced check-in bot at USM; the explicit staff-review and opt-out statements are the controls to compare.

Evidence and measured results

Announcement only; no metrics, evaluation design or baseline.

Limitations and uncertainty

Institutional/vendor announcement; publication date only implied as October 2026; no outcomes; retention benefit is aspirational.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-12; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Retention offices want timely, low-friction outreach to students but must manage trust and staff capacity.
Stakeholders
  • Director of retention
  • Student affairs
  • Financial aid
  • Registrar
  • Privacy/FERPA officer
Discovery questions
  • Who reads student replies and are students told?
  • How are financial-aid answers kept current?
  • What retention metric and comparison group will judge the bot?
Value hypothesis
Proactive SMS check-ins with staff escalation might surface student needs earlier; no evidence yet.
Potential engagement
A bounded evaluation design for an SMS outreach pilot, including notice and accuracy checks.
Unsupported claims
  • Any retention improvement
  • Answer accuracy
  • Cost savings

Pre-sales engineering

Role takeaway
Fit
Institutions running or buying SMS engagement bots for retention.
Architecture and integration
Vendor SMS platform linked to SIS data feeds and a staff review/escalation queue.
Prerequisites
  • Student consent to texting
  • SIS data feed
  • Staffed review queue
Constraints
  • No published outcomes
  • Date only implied
  • Vendor-hosted data
Security
Limit SIS fields exposed to the bot; log staff access to conversations; publish FERPA notice.
Proof of value
  • Accuracy audit of top 50 questions
  • Median staff response time on escalations
  • Retention comparison vs prior cohort or holdout

Delivery

Role takeaway
Work
Operate the SMS bot with documented notice, a staffed review queue and an evaluation plan.
Dependencies
  • Vendor configuration
  • Retention staff
  • IT data integration
Ownership
Office of retention.
Skills and adoption
Staff learn to triage bot escalations and maintain answer content.
Governance checkpoints
  • Privacy notice approval
  • Content review each term
  • Mid-year outcome review
Acceptance criteria
  • Notice of staff review shown at first message
  • Escalations answered within one business day
  • Retention compared to a baseline
Risks
  • Students unaware humans read messages
  • Outdated aid answers
  • Staff overload

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?

Vendor-hosted SMS platform with automated answers and human-in-the-loop staff review; integration with student information systems not described.

Governance

Who approves, reviews and stays accountable for outcomes?

States opt-out at any time; does not state whether students are told staff read conversations before they reply.

Security and privacy

What data, permissions and controls need testing?

Staff access to conversation content and any SIS data use require FERPA notice; not detailed in the release.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Adds staff workload for conversation review; SMS reaches students without app installs.

Procurement

What should contracts, pricing and exit terms secure?

Vendor-provided platform; contract terms and cost not disclosed.

Operating model

Which teams own the service once it runs?

Owned by the director of retention; bot positioned as a layer alongside faculty and staff support.

Publication history

  1. 2026-10-11Student Success · Issue 353 resources
Read preserved resource versions (JSON)

Stable resource ID: morehead-state-beaker-chat-edsights-sms-retention-202610