Like many districts, Longview was already communicating constantly and doing it well. There was a shared email address, a website contact form, district and campus receptionists, and countless staff members trying to help families.

But none of it added up to a system.

The ask@lisd.org inbox was the most visible symptom. Anything could go there: public records requests, questions about late students, enrollment inquiries, complaints. It hit every person on the list. And because everyone received it, no one knew who owned each question.

The result was predictable: A parent asks a simple question, a receptionist doesn’t have the answer, the call then gets transferred, someone sends an email, then someone else replies a day later, and so on. The family waits, staff time disappears, and nobody learns from the pattern.

Hefley saw the architecture problem immediately: questions were entering the district through too many disconnected doors, and the district had no clean way to track and resolve them.

Longview had already been using an AI chatbot on their website. The data scraping was slow. Updates took 24 to 48 hours to index. And it did not connect to any human support layer or task management system.

What Hefley wanted was something that could answer questions faster, route the ones that needed a human, track whether those requests were actually resolved, and give leaders visibility into all of it.

When Hefley saw Community Experience demoed at the Apptegy SchoolCEO conference, the decision was immediate.

“We were like, okay, we’re not even going to look at other options. We’re going to go with Community Experience. I’m going to sign up for the beta because I want to test it. Honestly, we were blown away at how fast the setup was and how instantly it was able to provide people with answers. It was seamless.”

Community Experience gave Longview the unified system Hefley desired: AI Search and Chat for instant answers, Smart Routing that automatically sends contact form submissions to the right place, Unified Task Management so every request is owned and tracked, and Action-Oriented Analytics so leaders can see what families are actually asking.

The clearest early signal did not come from analytics. It came from behavior at the front desk.

Before Community Experience, reception staff hit a familiar wall: they had the phone call, but not always the answer. The default was to transfer, which frustrated families and routed pressure further into the building.

Now, Hefley said, staff do something different. While still on the phone, they pull up their website and type the caller’s question into the AI Chatbot or Search and read the answer back directly.

“I think that they feel more comfortable,” he said.

Better customer service often starts with staff confidence. When the person answering the phone has a tool that helps them answer in the moment, fewer calls get transferred, fewer families wait, and fewer questions fall through the cracks.

Hefley also noticed a behavioral shift in how staff talk about the website. Instead of trying to walk callers through it manually, they now suggest people use the AI tools on the website themselves.

The front desk went from a bottleneck to a first-stop resolution point.

The ask@lisd.org inbox had one especially damaging flaw:

“If everyone gets this email, but you don’t have visibility into the response, you don’t ever know who took care of the ball,” Hefley said.

Task management changed that dynamic entirely. Instead of requests floating through inboxes, Longview routes them with clear ownership, oversight, and completion tracking. Every department receptionist in the admin building is now on the system. Campus rollout is next.

For Hefley, the most practical benefit was visibility: “I can see that you’ve completed it.” That matters more than it sounds. In a district system, accountability is often lost in the space between who received the question and who actually answered it. Task management closes that gap.

The system also protects staff identity. When a response goes back to the family, it appears as coming from Longview ISD, not from an individual employee’s personal work email. Staff stop becoming the permanent personal contact for future questions. Communication stays professional and district-owned.

This is where Longview’s story gets bigger than inbound communication.

Community Experience did not just answer questions better. It exposed where the district’s website was failing: which answers were buried in PDFs, which pages were too hard to find, which topics families were clearly looking for, but their website was not surfacing. What started as a chatbot rollout became a full audit of Longview’s digital presence.

Hefley’s response was not to pull back. It was to rebuild.

“My whole goal is to have the most AI-friendly district digital footprint as possible,” he said. The district began converting PDFs into CMS pages so the AI Search and Chatbot could index and serve the information families actually needed. CMS pages are not just easier to index; they can be translated into any language, and they are findable by other AI platforms families are already using to research schools.

“If you’re scared about turning on an AI chatbot because you think your website doesn’t have the information to be able to answer what people are asking, that should be the big red flag and warning siren going off,” Hefley said. “That’s the problem. You need to start working on content.”

Why Indexing Speed Matters

In schools, families often need answers right now. Not tomorrow. Not in 48 hours.

With our previous AI Chatbot, new content took 24 to 48 hours to become searchable. With Community Experience, Hefley said, “As soon as you hit publish on a page, it’s indexed and the AI can find it. I love that 10 times more.”

The difference showed up immediately during weather closures. When Longview published an emergency page about school being closed, the AI Chatbot answered “Is school open today?” right away.

That is the difference between a communication system that helps in real time and one that trails reality. In a district context, that difference is the whole point.

Before Community Experience, Longview had no meaningful visibility into inbound communication patterns.

“We had no metrics when it came to ask@lisd.org. If anything, it inflated people’s inboxes more than anything,” Hefley said.

Now, district and campus leaders can log in and see what’s being asked, when, and from which campus, in real time. That kind of access did not exist before.

One example surfaced quickly: summer reading questions accounted for 5.2% of total volume at one point. Hefley’s immediate read: “That tells me there’s no content about summer reading.” He added the information to the homepage the same day.

Questions become signals. Signals become content priorities. Content priorities become better service. Hefley envisions a future where the system surfaces those gaps automatically for department heads, without requiring the communications team to be the messenger.

Community Experience is not just helping Longview answer better. It is helping the district see better. As Hefley put it, in a world where families increasingly use AI tools to research schools before they ever call, that makes it “one more place where you can own the source of truth.”

Longview is still early in this journey. Task management is rolling out to all campuses this summer. The PDF-to-CMS conversion will be complete by fall. Customer service training, which will include Community Experience as a core tool, is being built into professional development across the district this summer.

Hefley is direct about what comes next: if you are hesitant to turn on an AI chatbot because your website cannot answer what people are asking, that hesitation is pointing to the real problem.

“Activate the chatbot. Then let the analytics tell you what content you need to work on. Either way, it’s beneficial , whether you’re starting from zero or starting with way too many pages.”

The Bottom Line

Longview ISD did not need a better chatbot. It needed a better system. And the clearest proof is not in the numbers. It is in what Hefley said when asked whether the district could imagine turning it off: “We’ve completely shifted our website strategy due to this system.”

More than that, it gave Longview a mirror. The district could finally see where its communication was working, where it was falling short, and what to do about it.

In a moment when K-12 districts are under pressure to move faster, explain more, and earn trust with less margin for error, that kind of visibility is not a nice-to-have. It is how districts get better.

Apptegy Community Experience helps districts answer questions faster, reduce staff burden, and turn inbound communication into strategic insight. Learn more at apptegy.com/community-experience