Hybrid Networks: Challenges and Best Practices | Webinar Recap

Hybrid Networks webinar recap blog

We recently co-hosted a webinar with Sonar Software where we looked at the rise of hybrid networks and the challenges and best practices associated with them.

During the webinar, co-hosts Dan Siemon, Chief Product Officer and co-founder of Preseem, and Sonar CEO Simon Westlake looked at the key issues for multi-access networks (e.g. fixed wireless and fiber). These included technical challenges, deployment methods, scaling ability, monitoring options, and more. They also considered some not-so-obvious obstacles that fixed wireless ISPs might face when adding fiber to their network mix.

Read on for a recap of the webinar or simply view it for yourself here!

Hybrid Networks Add Complexity

As Dan and Simon discussed, complexity is added when single-access technology networks move to hybrid. As well, hybrid networks can become a problem as ISPs grow.

Typical issues that ISPs might face as they move to a fixed wireless/fiber hybrid network include:

  • Access technology and multi-vendor expertise are required to access the root cause of problems
  • Provisioning requires either training non-technical staff on multiple tools or relying on technical staff to make changes
  • The support team has no single place to understand network quality and see problems
  • Once you get to multiple access technologies and multiple vendors within each access technology, provisioning and support become unmanageable when just using vendor tools because you’ll be accessing multiple systems all the time
Slide showing buffering as a major source of latency

Also, training on multiple systems can become painful and time-consuming. Onboarding L1 support and expecting them to become masters of multiple systems quickly is impractical.

Hybrid networks automatically become multi-vendor networks because no equipment vendors offer best-in-class products across all access technologies. That’s OK, however, because multi-vendor is a good thing—you want to be able to choose the best vendor and/or access technology for a given problem or situation. For example, fiber might make sense in an urban environment, whereas fixed wireless makes more sense in a rural area.

Scaling Your Team in Hybrid Networks

Having that flexibility is handy. However, with multiple vendors you add new complexity, so how can the business scale in this environment?

As the slide below shows, you can think of it as splitting the network into layers, with the access tech and vendor expertise being the responsibility of the technical team, while customer-facing support and provisioning should really only be concerned with the network quality and billing/monitoring systems. For example, the customer-facing teams shouldn’t need access to tech expertise. They should be focused on ‘are we delivering what our customers expect?’

Slide showing how packet loss can affect latency

Getting a single pane of glass where you can look at all your data and having it be accessible for your support people is critical to be able to scale. Support teams shouldn’t have to think or know too much about how the service is being delivered when they’re dealing with customer problems or simply upgrading a service plan.

Choosing a Billing/OSS System for a Hybrid Network

When it comes to choosing billing/OSS systems, Simon highlighted the following:

  • Look for systems tailored to abstract service provisioning methods
  • The ability to provision CPE and manage IP assignments is important
  • Look for strong APIs so you can extend where necessary

Individual network tools are still important for low-level debugging. However, high-level workflows don’t make sense to push from the semi-technical staff on down. You don’t want to have people logging into vendor management tools all the time. You can save time and become more efficient with the right tools in place.

Simon also talked about the importance of inventory mapping, especially as you get into multi-access networks—knowing where your resources are is key. For example, you need to know where your IPs are, where your equipment is, where your techs are and what they can do (e.g. what access technologies are they familiar with, can they climb, can they splice)? You need to be able to track this centrally.

Understand Your Network Quality

Dan then explained Preseem’s ‘top down’ and ‘bottom up’ approach to ensuring network quality.

On the ‘top down’ side, Preseem looks at subscriber traffic in an access-agnostic way, taking everything that characterizes IP/transport layer performance. This is then tied back to topology, and then we identify which parts of the network deliver a poor experience and which subscribers are getting a poor experience.

Slide showing how packet loss can affect latency

The ‘bottom up’ end involves extracting information from the network elements themselves. Preseem pulls RF parameters and builds up a model of each AP’s capability. This way, we can aggregate the data, understand the performance, and use this to drive scores. The goal is to provide an abstraction of quality without all the details support teams don’t need. This makes life easier for your support staff and enables proactive management of your network to give your subscribers a better experience.

Summary

To recap the main points of the webinar:

  • Hybrid/multi-access networks are here to stay
  • A multi-access network is a multi-vendor network
  • Multi-vendor networks are good but add complexity
  • Scaling and reducing operating costs requires abstracting the low-level details for most of the team (e.g. support, provisioning, admin)

Dan and Simon also discussed plan enforcement issues and reducing policy implementation complexity. View the entire webinar below!

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.