From the Campus Operations edition of November 7, 2026
Cal Poly Pomona's Billy Chat texting bot sent an incorrect spring 2027 registration alert after a copied campaign, following the departure of a key bot manager
Cal Poly Pomona (California State University), Student Success / Billy Chat team · Higher education enrollment communications operations · United States (California)
- Publisher
- The Poly Post
- Original publication
- 3 November 2026 (student newspaper); incident on 20 October 2026
- Source retrieved
- 2026-11-08
- Event date
- 2026-10-20
What happened
On 20 October Billy Chat, Cal Poly Pomona's Mainstay-based texting bot, told students their spring 2027 registration window had opened although general registration opened on 22 October; a correction followed 30–60 minutes later. The associate vice president for student success said a staff member copied a 2025 campaign that included all registration date options, a human error after the departure of a co-founder who managed the bot; it is now run by two people. She met the vendor on prevention and plans better training and safeguards. Every student receives alerts unless they opt out, and each has a data feed including enrollment status and the tone they use with the bot. The administrator says the bot is AI but not a large language model and relates higher hold-clearing rates to it.
Why it matters
An operations lesson for any campus running automated, personalised outreach: campaign configuration, change control and staffing continuity are the failure points, not the model.
Evidence and measured results
Student journalism with named administrator and student quotes; no incident report, affected-student count or hold-clearance data was published.
Limitations and uncertainty
Single reported incident; not an LLM failure; outcome claims about hold clearance are unquantified administrator statements; student-success boundary noted, included for its operational-control lesson.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Automated student outreach depends on a few operators and reused campaigns without pre-send checks.
- Stakeholders
- AVP Student Success
- Registrar
- Communications
- Messaging platform vendor
- Discovery questions
- Who can launch campaigns and is there a second reviewer?
- How many people can operate the platform today?
- How are reused campaigns validated before sending?
- Value hypothesis
- Change-control and cross-training may reduce misfires in automated outreach; the source reports no incident rates.
- Potential engagement
- An operational-resilience review of automated student messaging with runbooks and pre-send controls.
- Unsupported claims
- Retention or hold-clearance gains attributable to the bot
- That this was an LLM failure
- Incident frequency across CSU
Pre-sales engineering
Role takeaway
- Fit
- Campuses running vendor texting or chatbot platforms with personalised campaigns.
- Architecture and integration
- Campaign calendar, per-student data feeds from SIS and a Q&A knowledge base in a vendor platform.
- Prerequisites
- Platform admin access
- Campaign templates inventory
- SIS data feed documentation
- Constraints
- Vendor feature limits on validation
- Opt-out default
- FERPA obligations
- Security
- Limit per-student feed fields to documented purposes and review access to conversation data.
- Proof of value
- Seeded test-audience sends before launch
- Approval workflow enabled for reused campaigns
- Audit log review of campaign changes
Delivery
Role takeaway
- Work
- Write runbooks, add two-person review, cross-train operators and define correction procedures.
- Dependencies
- Vendor cooperation
- Registrar calendar data
- Staff time
- Ownership
- Student Success leadership with communications and registrar.
- Skills and adoption
- Cross-train at least two operators on campaign build and validation.
- Governance checkpoints
- Pre-send review of reused campaigns
- Post-incident review with vendor
- Termly incident reporting
- Acceptance criteria
- Proposed: at least two trained operators
- Proposed: corrections issued within an hour
- Proposed: zero unreviewed reused campaigns
- Risks
- Key-person dependency
- Student distrust of automated messages
- Data-feed scope creep
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 platform with planned campaigns on a calendar, per-student data feeds and a 2,000 Q&A knowledge base; campaign templates reused across years.
Governance
Who approves, reviews and stays accountable for outcomes?
No described pre-send review or testing of reused campaigns; opt-out default for all students.
Security and privacy
What data, permissions and controls need testing?
Per-student feeds include enrollment status and conversational tone; students voiced uncertainty about who controls the bot.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Shows key-person dependency: loss of one experienced operator preceded the error.
Procurement
What should contracts, pricing and exit terms secure?
Vendor-hosted campaigns place prevention partly on vendor features such as validation and staging.
Operating model
Which teams own the service once it runs?
Automated outreach needs documented runbooks, cross-trained operators and pre-send checks for reused campaigns.
Publication history
- 2026-11-07Campus Operations · Issue 604 resources
Stable resource ID: cal-poly-pomona-billy-chat-wrong-registration-alert-20261103