Mastering Hybrid Networks with Preseem and Sonar: Webinar Recap

Header image for Mastering Hybrid Networks webinar recap blog

Mastering Hybrid Networks with Preseem and Sonar

We recently co-hosted a webinar with Sonar Software, where we looked at how our integrated solutions can help optimize fiber and fixed wireless hybrid networks.

During the webinar, co-hosts Gerrit Nagelhout, CEO and co-founder of Preseem, and Thomas Crawford, Regional Sales Director at Sonar, addressed some of the key benefits hybrid network providers using the two systems can enjoy, including:

  • A consolidated view of network metrics across fiber and wireless technologies
  • Efficient proactive and reactive operations with streamlined tools
  • Reduced training costs with a single, user-friendly platform
  • Increased deployment agility for faster expansion and adaptation

Read on for a recap of the webinar, or view the recording here.

Access Network and Subscriber Management for ISPs

For those unfamiliar with Preseem, Gerrit began by explaining how the platform helps fiber, fixed wireless, and hybrid operators understand and improve the subscriber quality of experience (QoE) and increase efficiency across vendors and access technologies.

For example, operators using Preseem can provide subscribers with improved QoE and a faster-feeling internet even when the network is busy or plan speeds are maxed out. The system also benefits all teams at an ISP by providing a wealth of data and tools to:

  • Find out where and why network bottlenecks are occurring
  • Troubleshoot customer issues to determine if the problem is in-network or in the home
  • Pinpoint areas in the network that have the capacity to add more subscribers

Checking under the hood, Gerrit also showed the three major components that make up the system. The Preseem Cloud is the home for all the data and built-in integrations that automatically retrieve information from systems like Sonar. This allows for a centralized view of your network across all vendors and subscribers, so you can access everything in one place.

Image showing the components that make up Preseem

Preseem Elements handle the QoE aspects of what we do, such as measuring and improving the subscriber experience, enforcing plan speeds, and mitigating any capacity issues. Finally, the Preseem Poller automatically maps the subscriber and network topology while collecting network metrics for analysis.

A Single Point of Plan Enforcement

After further explaining some of the capabilities of Preseem Elements, Gerrit looked at the benefits for hybrid networks that come with simplified provisioning across all of your access technologies and vendors.

For one, this greatly eases your integration burden. Rather than having your billing system connected directly to your ONTs and CPEs, and all of the configuration headaches that go with it, Preseem provides a single point of plan enforcement at the IP layer.

This reduces integration complexity (and cost), with no provisioning infrastructure required for each vendor and model that’s deployed in your network. It also doesn’t matter whether you have fiber, fixed wireless, cable, etc., because Preseem is access technology-agnostic. This also gives you deployment flexibility, as you’re free to add the best equipment for a given situation without being tied to one specific vendor.

Slide showing a diagram of the simplified provisioning provided by Preseem for hybrid networks.

As an added bonus, Preseem’s traffic shaping via active queue management (AQM) provides your subscribers with a much better experience than the basic shapers that are built into ONTs and CPEs. Congestion within the plan rate is one of the biggest causes of poor QoE, and Preseem handles this via AQM by separating bulk flows (system updates) from interactive flows (streaming, gaming) to ensure a low-latency, consistent experience.

Preseem For Your Teams

Next, Gerrit dove into how Preseem can benefit each of the teams at hybrid networks, and simplify their jobs. These include:

  • Core Network Operations: QoE measurements in Preseem can uncover many causes of a poor subscriber experience, including overloaded backhauls or APs, bad bonded link configs, overloaded routers, and more. This greatly reduces troubleshooting time and also allows for proactive fixes that can prevent future support calls.
  • Access Network Operations: For fixed wireless networks, you’ll be able to see which APs are delivering a poor experience, are over or under capacity, or have bad RF conditions, as well as which CPEs can be improved to free up airtime. In fiber networks, you can manage ONTs across OLTs, PONs, and vendors, and drive proactive operations with cross-vendor KPIs.
  • Support: Team members can find fixed wireless or fiber subscribers easily in Preseem, and quickly see which plan they’re on and the services they’re receiving. This eliminates having to learn and log into multiple systems, saving a ton of time. They can also use easy-to-understand data and metrics to see subscriber usage and whether any issues are in-home or in the network, reducing unnecessary escalations and time to root cause.
  • Sales and Marketing: By receiving accurate data on capacity, sales and marketing teams can pinpoint areas to add new subscribers and increase revenue. This empirical data eliminates any disagreements between network operations and sales & marketing about capacity issues.

Solutions for Regional Fixed Wireless and Fiber ISPs

As Thomas explained, for regional hybrid networks, there’s a variety of legacy systems in the market that are outdated, difficult to use, and expensive. This leaves operators with a complex tech stack consisting of multiple products that don’t communicate with each other. It also leaves them without a single source of truth platform that serves their end-to-end business needs.

Slide showing the challenges faced by hybrid networks

This is where Preseem and Sonar come in—modern, easy-to-use systems that integrate with each other and make life easier for each team at an ISP. For Sonar, this means making sure that the system is easy to use for CSR and Tier 1 support, allowing them to quickly determine the source of any service degradation with non-technical tools for fast troubleshooting. Thomas also explained enhancements for Tier 2 and Network Operations teams, such as planned and unplanned outage notifications tied to specific OLTs, ONTs, or APs.

In addition, Sonar has tools for outside plant and construction teams to update build progress documentation for addresses. There are also features specific to sales and digital marketing team members, such as the ability to market to customers through each stage of build progress. Sonar also provides benefits for regulatory teams, billing and finance, field operations, and inventory, warehouse and logistics staff.

How the Preseem-Sonar Integration Helps Hybrid Networks

Thomas then took a look at the integration between Preseem and Sonar. A few of the benefits specific to fiber and hybrid network operators include:

  • Tie ONTs to Subscribers Automatically: Sonar can automatically tie ONTs to subscribers based on device assignments in Preseem
  • Dynamically Link Subscribers to PON Ports: Subscribers are linked to the appropriate PON port to simplify remote support and troubleshooting
  • Tie Subscribers to Their OLT: Sonar links ONTs to the head-end OLT to simplify path-tracing exercises
Slide showing some of the benefits of the Preseem-Sonar integration

Topics also covered by Thomas include multi-vendor networks, fiber provisioning integrations, and how the Preseem-Sonar integration solves a lot of problems for hybrid networks by being vendor-agnostic, providing simplicity for multi-vendor deployments, and allowing for easier deployment and network configuration.

Click below to watch the full webinar. Reach out to us for a demo on a live network and see how Preseem can benefit your fixed wireless, fiber, or hybrid operation.

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.

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.