WISPAMERICA 2025 Conference Preview

Header image for WISPAMERICA 2025 preview blog

WISPAMERICA 2025

It’s been a mighty long winter in this neck of the woods, but spring is finally coming and that means, among many other things, that it’s time for WISPAMERICA 2025.

This year’s event will once again be held at the Oklahoma City Convention Center, from Monday, March 24th to Thursday, March 27th.

One of the main events in the Wireless Internet Service Providers Association (WISPA) calendar, WISPAMERICA 2025 will bring together more than 1,200 attendees and 100 exhibitors from around the world to OKC.

The skyline of Oklahoma City, site of WISPAMERICA 2025

This year’s conference will feature over 60 events and expert sessions throughout the week. As always, there’s a lot going on, and no one can possibly catch everything. Don’t worry, though—we’ve got your back. Our team has read the WISPAMERICA 2025 agenda and drawn up a list of events and sessions you won’t want to miss. View our recommendations below.

If you’re heading to the conference, drop by booth 429 to say hello to the Preseem Team during Exhibit Hall hours. Also, make sure to register for the Preseem Networking Event, and get set to mingle with our team and your colleagues at our open bar! 🍻

Events and Sessions to Attend at WISPAMERICA 2025

Monday, March 24th

  • TechVision Forum – This is an all-day event designed for CTOs that requires separate registration and payment. Sessions include discussions on AI, cybersecurity, networking tools, and more.
  • Preseem Networking Event: 3 p.m. to 5 p.m. – Whether or not you’re attending the TechVision Forum, you’re welcome to join Preseem in the afternoon for our annual Networking Event. If you haven’t attended before, the vibe is informal and a great chance to catch up and talk shop with your fellow industry professionals before the conference kicks into gear. You will receive NO sales pitches from us during this event! We’re providing an open bar so sign up and drop in for a drink 🍸
  • Welcome Reception: 5:30 p.m. to 7:30 p.m. – After our networking event, keep the good vibes flowing by heading to the Exhibit Hall for a Welcome Reception, a new addition to the conference calendar this year.
Attendees mingle at the Preseem Networking Event at WISPAMERICA 2024

It’s always nice to see friendly and familiar faces like these at the Preseem Networking Event!

Tuesday, March 25th

  • Keynote: Venture Capital—The Network Behind American Innovation: 9:30 a.m. to 10:15 a.m. – After the opening breakfast, stick around in the Painted Sky Ballroom to hear NVCA President and CEO Bobby Franklin talk about how VC funding helps the broadband sector.
  • Future-Proofing Network Monitoring: Vendor-Agnostic Strategies and Solutions – 1:45 p.m. to 2:45 p.m. – The first panel sessions of the day start after lunch, including this Tech Track discussion that will cover advancements in network monitoring, vendor-agnostic tools that offer cross-platform compatibility, and integrating multiple systems into one unified monitoring solution. Speakers include Preseem CPO, Dan Siemon.
  • Mastering Network Troubleshooting: Tools, Techniques, and Real-World Solutions – 3:15 p.m. to 4:15 p.m. – Learn effective network troubleshooting techniques to help you identify and resolve issues faster in this session that will include input from Preseem Senior Product Manager Jeremy Austin. Using real-world examples, you’ll also learn how to use tools to diagnose issues, enhance Quality of Experience (QoE), and maintain network stability.

Wednesday, March 26th

  • Tech Roundtable: 8:15 a.m. to 10:45 a.m. – This Deep Dive Tech roundtable will be moderated by our own Jeremy Austin, and will cover a variety of topics. Expect to dig into the details on redundancy and failover, network resiliency, threat identification, and much more.
  • Women of WISPA Leaders Series: 9 a.m. to 10 a.m. – As always, this free event is open to all WISPAMERICA attendees and WISPA members, regardless of gender. This year, the guest speaker is Emily Lampkin of the Women Leaders Series, who will deliver the first part of a three-part lecture series that will continue at WISPAPALOOZA and next year’s WISPAMERICA. Preseem is a sponsor of this event—if you’d like to attend, please RSVP here.
  • Expanding Your Toolbox: Integrating Multiple Technologies for Service Delivery – 11 a.m. to 12 p.m. – Delivering exceptional broadband service requires more than one technology. Find out how to assess which technology is the right fit for each use case, and learn useful strategies on how to integrate multiple tools and improve service reliability. Moderated by Matt Duench, Product Marketing Director at Preseem.
  • Automation and AI for Fiber Network Optimization – 11 a.m. to 12 p.m. – Join Preseem CTO Scot Loach as he moderates this discussion on how ISPs can use AI-driven analytics, predictive maintenance, automated provisioning, and intelligent traffic management to optimize fiber networks.
  • Sales-Driven Success: Building a Culture of Growth and Alignment – 3:15 p.m. to 4:15 p.m. – In this Marketing/Sales Track session, attendees will learn about data-driven decision-making and get actionable insights on how to foster a culture of collaboration that drives measurable results. Moderated by Rob Payne, Director of Sales at Preseem.
The Bricktown neighborhood in Oklahoma City

The scenic Bricktown area of OKC, close to the WISPAMERICA 2025 event site.

Thursday, March 27th

  • Closing Keynote: The Room Where It Happens – 9:45 a.m. to 10:30 a.m. – This closing keynote speech and roundtable will cover how regulatory changes and a changing political landscape may affect regional ISPs while providing a combination of opportunities and challenges.
  • Hands-On Training: 11:15 a.m. to 3:15 p.m. – Conference attendees with full registration or a Wednesday/Thursday badge can attend immersive training sessions for fiber, installers, or tower climbers. Boxed lunch is included.

Visit the WISPAMERICA 2025 Exhibit Hall

With over 100 vendors on the floor, the Exhibit Hall will be a busy spot at WISPAMERICA 2025. There are new and expanded hall hours this year, giving you more time to visit with vendors and check out all the latest gear. As mentioned above, Preseem will be at booth 429, so make sure to stop by and chat with our friendly team of experts.

Exhibit Hall hours:

  • Monday, March 24th: 5:30 p.m. to 7:30 p.m. (Welcome Reception)
  • Tuesday, March 25th: 12 p.m. to 5:15 p.m.
  • Wednesday, March 26th: 10 a.m. to 5:15 p.m.

Watch our video from last year’s WISPAMERICA for a little preview of what to expect.

In addition to all the informative sessions and industry networking, there’s also time to explore the city during conference off-hours. From water taxis on the Bricktown Canal and the city’s 70-acre Scissortail Park to museums on art, science, and cowboys, there’s no shortage of attractions to enjoy in the Big Friendly.

P.S. Don’t forget to register for the Preseem Networking Event on Monday, March 24th, from 3 to 5 p.m. at the Omni Oklahoma City Hotel. We’ll see you there!

Where Do the Minutes Go on a Tier 1 ISP Support Call?

A subscriber calls because the internet has been dropping out every evening, and your agent starts the call already behind. They open the account in billing, then the subscriber's radio or ONT in the vendor's portal, then the ticket history, and run a test against the CPE while narrating the wait to someone who was already annoyed when they dialled. That's often how a technical call runs in Tier 1 ISP support: much of it goes to searching, and the conversation fits in around it.

A seasoned agent knows which systems to open and in what order, but still has to open them, because the subscriber's experience, the state of the shared asset and the history of the account are stored in different places. As Wi-Fi or the Network? set out, each check answers part of the question and sends the agent somewhere else for the rest, so the difficulty lies in where the evidence lives rather than in the person reading it. When the call runs out before the answer arrives, the subscriber gets a callback, an escalation or a reboot script that may not address the fault.

Why Is One Agent Doing Two Jobs on Every Call?

Every technical call holds two jobs. One is finding the answer: gathering evidence across systems, comparing this subscriber with their neighbours and deciding where the fault is. The other is handling the person: listening and empathizing with what they've been living with, explaining what's wrong in terms they recognize and telling them what happens next. They're different skills, and on today's desk one agent does both at once.

On the evening-dropout call, the investigation takes the agent's attention first, because there's nothing to explain until it's done. The subscriber listens to typing while the agent moves between portals, and if the answer arrives after they've hung up, the explanation never happens, and the ticket moves to Tier 2. Repeated across a day, that's the reactive load that keeps ISP support teams stuck in firefighting mode.

What Does Tier 1 ISP Support Need on Screen to Close the Call?

Four pieces of evidence, read together:

The What Tier 1 Needs

Where It Usually Lives Today

What It Helps Determine

The What Tier 1 Needs

The subscriber's experience over the window they're describing (latency, packet loss, throughput against their plan)

Where It Usually Lives Today

A QoE system, if the operator collects it at all

What It Helps Determine

Whether the problem the subscriber describes actually happened, and when

The What Tier 1 Needs

The asset they sit on, and how other subscribers on that AP, sector or PON did over the same hours

Where It Usually Lives Today

The network management system, or one portal per radio and OLT vendor

What It Helps Determine

Whether others on the same asset were affected at the same time, which points to a shared issue

The What Tier 1 Needs

Has a problem that's in your network

Where It Usually Lives Today

The radio or OLT vendor's tool

What It Helps Determine

Whether the drop to the home is healthy, which narrows the search without placing the fault inside the home

The What Tier 1 Needs

What was tried on this account last time

Where It Usually Lives Today

The ticketing system or CRM

What It Helps Determine

Which steps not to repeat

None of these settles the question alone. Identifying an in-home Wi-Fi problem takes evidence from behind the CPE, and neighbours degrading at the same hours points to a shared issue without naming its cause. With all four in one view, an agent can reason through the diagnosis and explain what the evidence points to as they go, but reading them together mid-call is still the investigation, just done faster.

How Does an AI Support Assistant Get the Answer on Screen?

Preseem's Support Assistant, part of Preseem Plus, does the troubleshooting itself. Once the call is tied to a subscriber, it works through the same evidence an agent would chase across systems: the subscriber's experience over recent days, the other subscribers on their AP, sector or PON, the history of their radio or ONT, and the tickets already on the account. It gives the agent the cause and the next action in plain language, including whether the fault is in the home or on the network, and where, along with the evidence that places it there.

On the evening-dropout call, the agent opens the account and sees the pattern laid out: the subscriber's latency and packet loss climbing from around 7 p.m. on each of the evenings they described, their radio link healthy throughout, the other subscribers on the same sector showing the same pattern over the same hours, and the sector running at capacity while it happens. The assistant reads those together and places the problem on the shared sector as evening congestion, then routes it to the network team with that evidence attached. That reading is what it adds beyond four sources on one screen, since the agent isn't the one left to work out whether a healthy link and degraded neighbours add up to congestion.

The agent doesn't need another round of checks; they square the answer with what the subscriber is describing and act on it. Because the Support Assistant works alongside the agent, a person who knows the subscriber and the network sees its answer before the subscriber does, which is what separates an assistant from a tool placed in front of the subscriber, as covered in what AI actually does in ISP customer support.

What Does the Agent Tell the Subscriber?

With the investigation done, the rest of the call focuses on the subscriber. The agent can tell them that their own connection and equipment are fine, that the slowdown they've been seeing is on the part of the network they share with their neighbours and happens when it's busiest in the evening, and that it has been escalated to the network team with the evidence attached. Then comes what happens next: when they should see a change, that nobody needs to visit, and how they'll hear back.

The agent also has time to listen. If the subscriber mentions that the dropouts happen on weekend mornings too, that doesn't fit an evening congestion pattern, and an agent who isn't juggling portals can hear it, ask about it and check it against what's on screen before the call ends.

How Much Shorter Do Calls Get When Tier 1 Has the Answer?

Among Preseem customers using the Support Assistant, we've seen call times fall from over 30 minutes per call to under five. Read it as an indication of what's possible rather than a benchmark for your desk; your own call mix and network will shape where you land.

What Happens Next Once Tier 1 Has a Diagnosis?

A diagnosis on the call leads to one of three outcomes, and only one resolves the issue before the subscriber hangs up. When the assistant places the fault inside the home, the agent can often fix it with the subscriber on the line by moving the router or switching a device to a wired connection. Where the home network itself is what's holding the subscriber back, such as an ageing router or Wi-Fi coverage that doesn't reach the rooms they use, the agent can also offer a managed router service, so the operator looks after that part of the connection from then on. When it points to a fault on the shared network, as on the evening-dropout call, the ticket goes to the NOC with the fault confirmed. When it points to the subscriber's own link, a technician goes out with the fault already located.

The second and third outcomes still leave work for someone else, but they change what that work is. A call that runs out before the cause is found often escalates as little more than a description of symptoms, and Tier 2 or a network engineer starts the investigation again from scratch. With the diagnosis and its evidence attached, they start from the finding, and that's the metric for a support leader to watch: how many tickets reach Tier 2 needing the investigation started over. The engineers who would otherwise rerun it are often the same people planning upgrades and building out new areas, so each investigation they don't repeat is time back on that work. For how this fits with first-contact resolution, ramp time and the rest of the desk's numbers, see the complete guide to improving ISP support performance.

 

Take A Tour:

ISP Network Priorities

Explore how Network Priorities ranks network issues by subscriber impact, helping you focus on the fixes that make the biggest difference.

Take A Tour:

Support Assistant

See the Support Assistant in action! 

Frequently Asked Questions

 

When should a Tier 1 ISP support call escalate?

A call should escalate when the fix needs something Tier 1 can't do: a configuration change on the network, a field repair, or a fault the NOC has to work. An escalation made because nobody could identify the cause in time is the easiest kind to recover, since the information needed to settle it often already exists in the operator's systems. Sort a month of escalations into those two groups and you'll see how much of your Tier 2 load is diagnosis rather than repair. The ISP support performance guide covers the escalation measures that sit alongside it.

Is an AI support assistant for ISPs just a smarter knowledge base?

No. A knowledge base holds procedures that apply to any subscriber, while an assistant connected to network data works out what's wrong with this subscriber's connection today. The knowledge base still has a place, because it's where the steps for a router reset or a plan change live once the cause is known. What it can't do is locate the fault, which is why an agent working from articles alone ends up troubleshooting by elimination.

What does AI agent assist need from a broadband network?

It needs per-subscriber experience measured continuously, a map tying each subscriber to the AP, sector or PON they sit on, access-link telemetry from the radio and OLT vendors you run, and the account's ticket history. To place a problem inside the home rather than just rule out the access link, it also needs evidence from behind the CPE. The topology map is easy to overlook, and without it a tool can't compare a subscriber with their neighbours, which is how a shared fault is told apart from a single one.

What if the subscriber doesn't accept the help desk diagnosis?

Show them the evidence in terms of their own experience: the drops on the evenings they described, or the fact that their neighbours on the same sector saw the same thing. A help desk diagnosis is much easier to accept when it matches what the subscriber lived through, and an agent with the answer already on screen has time to make that connection instead of reading a conclusion off a script.

About Preseem

Preseem shows regional ISPs what every subscriber is actually experiencing, from the network into the home and across every major equipment vendor. Operators use it to improve subscriber experience and business results together: keeping subscribers happier for longer, running a more efficient operation at lower cost, and earning more from upgrades and services subscribers want. Preseem turns that intelligence into next steps for support, the NOC and sales, aimed at whatever helps the most subscribers. Support Assistant gives the rep on the call the cause and the next action in plain language, including whether the fault is in the home or on the network. Network Priorities ranks the sites, APs and PONs to fix first by how many subscribers each one is degrading, and Service Priorities shows which subscribers to contact and whether to fix something or offer an upgrade. Expert view keeps two years of history behind every subscriber, AP and OLT. Learn more at preseem.com.

[/et_pb_post_content][/et_pb_column][/et_pb_row][/et_pb_section]

Latest From Our Blog

Network insights, best practices, and product updates to help you get the most from Preseem.
Amplify AI: Preseem’s Support Assistant

Amplify AI: Preseem’s Support Assistant

Discover Preseem’s Amplify AI: Support Assistant, an AI-powered tool that helps ISPs diagnose subscriber issues faster, reduce escalations and truck rolls, and resolve support calls more efficiently.

STOP MANAGING COMPLEXITY

START RUNNING YOUR BUSINESS

Every week without visibility is another week of trucks that didn't need to roll and subscribers who left without telling you why.

Let's start with your network, your vendors, your subscribers.