How did Brian Jolley solve the privacy problem in WGU's SMS rollout?

Brian Jolley solved the teacher privacy problem in WGU's SMS rollout using virtual numbers through Genesys Cloud. Each teacher was assigned a virtual number that routed through Genesys — students texted the virtual number, the teacher received it through their work interface, and no personal phone numbers were ever exposed. Opt-in was required from students, opt-out was instant and reliable, and no platform could expose student contact information to another system that didn't already have it. This privacy constraint shaped every other architectural decision.

What made the WGU SMS rollout organizationally complex?

Western Governors University's SMS rollout required integration across five platforms — ServiceNow, Salesforce, Genesys Cloud, Microsoft Teams, and the telephone system — each with its own routing logic, data model, and department politics. The deeper complexity was organizational: multiple university colleges needed SMS but none could agree on how it was supposed to work. They couldn't agree internally within each college, let alone across colleges. There was no clear direction, no chain of command for the decision, and no shared vocabulary for what one-to-many and many-to-one messaging looked like in practice. Brian Jolley and his team built a working solution and demonstrated it to each college individually, forcing the conversation from abstract to concrete.

Why did Brian Jolley use the WGU Service Desk as the SMS beta group?

Brian Jolley chose the WGU Service Desk team as the SMS rollout beta group because they were the most equipped to document problems with the technology, the implementation, and the process. Using a trained support team as the beta group meant that issues were caught and reported with the rigor of professional support documentation — not the frustration of end users encountering problems without context. This was a deliberate change management decision, not a convenience.

SMS Rollout

Five Platforms, Zero Agreement, One University

The Embarrassment

In 2018, Western Governors University — an online-only university — had no teacher-to-student messaging system. For a brick-and-mortar school, that might be a minor gap. For an institution whose entire student experience happens online, it was a painful point of embarrassment. Students becoming old enough for college expected to be able to text their university. The absence of SMS wasn’t just an inconvenience — it was a reputational liability.

The Problem Beneath the Problem

Adding SMS to a university is not the same as adding texting to a phone. The technical and organizational complexity was significant on every dimension.

Privacy. How do you let a student text a teacher without giving away the teacher’s personal phone number? How do you let a teacher message an entire class without exposing their cell? The solution was virtual numbers through Genesys Cloud — each teacher gets a virtual number that routes through Genesys, students text the virtual number, the teacher receives it through their work interface, and no personal numbers are ever exposed.

Routing. Which teacher gets the message? For which class? What about last semester’s students — can they still text the teacher? What if a teacher has several concurrent classes?

Broadcast and response. How does a teacher message the entire class at once? How do individual responses to a class-wide broadcast get handled?

Liability. Without a formal messaging system, there was no guardrail for appropriate behavior — partly inconvenience and partly legal exposure.

Integration. Messages had to be consumed by every system different departments used: ServiceNow for IT support, Salesforce for enrollment counselors, Microsoft Teams for internal collaboration, and Genesys Cloud for the contact center — plus the actual telephone system. Five platforms, each with its own routing logic, data model, and department politics.

The Real Challenge: Nobody Could Agree

The technical solution — virtual numbers through Genesys Cloud — was the straightforward part. The real challenge was organizational.

Multiple university colleges needed SMS, but none could agree on how it was supposed to work in practice. They couldn’t agree internally within each college, let alone across colleges. There was no clear direction, no chain of command for the decision, and no shared vocabulary for what “one to many and many to one” actually looked like in an implementation. “We want one to many and many to one” was all Brian Jolley heard from anyone. That doesn’t clarify much.

Once again, Brian Jolley found himself in the middle of a multiway tug-of-war — the same organizational fracturing pattern he encountered in every major initiative at WGU.

The Approach

Without clear requirements, Brian Jolley and his team built a working solution, then demonstrated it to each college individually. This forced the conversation from abstract (“we want messaging”) to concrete (“here’s what messaging actually looks like — does this work for you?”).

Resistance was either based in an incomplete understanding of the technology or in the inflexibility of departmental processes. Jolley met with department heads to demonstrate the technology, address their specific concerns, and emphasize the value to the end user: students should be able to communicate with the university consistently and easily, regardless of the reason for the communication.

The rollout started with the Service Desk team — the group most equipped to document problems with the technology, the implementation, and the process. Using them as the beta group meant that issues were caught and reported with the rigor of a trained support team, not the frustration of an end user. Objectors relented once they could see the system working.

The Result

SMS messaging is now used broadly across Western Governors University — by enrollment counselors, support agents, and instructors. Students can communicate with the university through a consistent channel regardless of which department they need. The five-platform integration (ServiceNow, Salesforce, Genesys Cloud, Teams, and the phone system) routes messages appropriately across departmental boundaries.

Why It Matters

This case study is less about SMS and more about what happens when a major capability requires alignment across departments that have no shared process, no shared vocabulary, and no shared authority. The pattern is the same one that appears throughout Brian Jolley’s WGU work: fragmentation creates friction, and someone has to make the structure visible — sometimes by building the thing and showing it to people — before alignment is possible.