Business connectivity decisions
Wireless service can solve a real site problem, but its role matters more than its label. Compare what the location can actually support, what must keep working during an outage, and whether a wired alternative is the better fit.
Start with the job the connection must do at this address. A wireless option deserves consideration only if its actual service terms and site conditions fit that job. The same product might be adequate for occasional backup traffic and insufficient for the site's full working day.
Consider wireless as the main connection where a workable wired service is unavailable, poorly matched to the site, or difficult to bring in under the project's constraints. Test it against busy-hour applications, upload needs, support terms, and the consequence of variation. A small branch or temporary location may have a different threshold from a critical headquarters.
A cellular connection can provide another way out when a wired primary fails. Size and configure it for the traffic that must continue, not automatically for every normal workload. Decide whether staff can switch manually or whether the site needs a tested automatic changeover.
If qualification shows unsuitable signal, service terms, capacity, or application behavior, do not force 5G into the design. A shared business fiber service, dedicated internet access, or another backup path may fit better. SourceNet's comparison should be able to end with no wireless recommendation.
List the applications that cannot pause, the number of simultaneous users, peak upload and download activity, and acceptable outage duration before choosing a role. A quote for primary service and a quote for emergency backup are not comparable until those requirements are clear.
Fixed wireless describes an internet access method serving a fixed location over a radio link. It is not a synonym for 5G. A fixed-wireless offer might use 5G, LTE, or another radio technology, while a cellular backup may connect over LTE when 5G is not available or not the selected service. The FCC distinguishes fixed broadband availability from mobile coverage, including fixed-wireless service on its fixed map and 4G/5G coverage on its mobile map.
Ask what the provider is actually proposing at your address: access technology, equipment, location restrictions, service characteristics, and any data or usage terms. Do not assume that two offers labeled "wireless business internet" have the same capacity, IP options, installation model, or support. A backup quote may also rely on different hardware or policy than a primary connection. The proposal, not the technology label, is the document to compare. Performance also varies with network congestion and plan prioritization, so a connection can slow during busy periods even where signal strength is adequate.
Begin with the exact service address and the provider's qualification for that location. A broad coverage claim is a starting point, not proof that a particular suite or equipment room will have usable service. The FCC notes that its mobile coverage map reflects outdoor or in-vehicle conditions, not indoor coverage. Its fixed map reports provider-submitted availability, which still needs confirmation for the proposed commercial service and address.
Ask where the receiver or gateway would sit and how it connects to the existing network. Building materials, a basement network closet, window access, exterior placement, and property permissions can affect the usable design. A Verizon Business installation guide illustrates how one carrier's offering may involve receiver placement, cabling, and building permission; those requirements are an example, not a rule for every service. Confirm the actual provider's equipment and installation responsibilities.
For primary service, qualify performance under representative workloads at the intended placement, including upload, latency-sensitive voice or video, and busy periods. For backup, confirm the signal and available capacity while the primary is unavailable. Neither a coverage map nor a speed test at another building settles the decision for this site.
A working wireless path may keep selected traffic connected when a wired access cable is damaged or the primary service becomes unavailable. Because it uses a different access medium, it can avoid some physical dependencies of the wired last mile. That is useful, but it does not make the whole site redundant. The result depends on what failed and on the backup's own network path.
A primary access-circuit fault, some provider outages, or building-entry damage affecting only the wired route, provided the wireless service, local network, and changeover remain available.
Loss of power to the gateway or firewall, a failed shared router or LAN switch, an outage in a shared upstream dependency, weak signal, unavailable wireless capacity, or a failover policy that was never configured or tested.
Trace the whole path from the application through local power, firewall, LAN, wireless gateway, radio access, and provider network. Ask which of those elements both connections still share. If continuity during a building power outage matters, power for the relevant equipment belongs in the same conversation. A second subscription alone cannot answer it.
Carrier diversity means the services have different provider names. Medium diversity means, for example, pairing a wired primary with a wireless backup. Physical path diversity concerns where those connections actually run and terminate. These can improve resilience, but none proves the entire route is independent. Separate providers may still share facilities or other dependencies, and two circuits can still depend on the same site equipment.
CISA's communications resiliency guidance recommends identifying shared links and evaluating alternate paths. Apply that as a buying question, not as a promise that any two quoted services are fully diverse. Ask providers what they can document about the building entry, access path, equipment, and upstream dependencies, and note what remains unknown.
For some sites, a wireless backup is a sensible hedge against a local wired cut even without proof of complete end-to-end independence. For a site with a stricter continuity requirement, the proposal may need deeper path review, a separate router or power design, or another location-based recovery option. Match the depth of the investigation to the business impact of losing the site.
Owning two connections is only the first step. Manual switching requires someone to detect the failure and change the route or equipment. Automatic failover needs a capable router, firewall, or managed service, a health check that detects the right problem, and a policy for what should use the backup. Some sites also use both links during normal operation. Those are different designs with different operational responsibilities.
Decide what the backup should carry: all traffic, only cloud and voice, or only the most critical applications. Then test an actual primary-path failure and restoration. Check whether users can reach the tools they need, whether inbound and outbound calling work, and who receives an alert. Existing calls, video meetings, VPNs, and sessions tied to a public IP may need to reconnect after a path change. Do not assume an automatic switch is instant or invisible to applications.
Mplify's SD-WAN service framework describes policy-based forwarding across underlying connectivity services. A managed SD-WAN solution can help apply and monitor those policies across multiple sites, but the behavior still depends on its configuration and the available connections. If policy, visibility, or multi-site operations are the main buying problem, continue to SourceNet's managed SD-WAN guide rather than treating the wireless circuit as the whole solution.
Give each prospective provider the same address, role, required applications, and existing network design. Then compare what each proposal includes, rather than treating an advertised speed or monthly charge as the whole offer.
Exact technology and service type, qualified address, intended equipment location, any site check, and installation or property-access responsibilities.
Expected download, upload, and service characteristics; any data or usage policies; support commitments; monthly and one-time charges; and contract term. Identify which details are estimates or conditional. Wireless plans may carry different performance guarantees, or service-level terms, than dedicated wired connections, so compare the actual commitments rather than assuming equivalent guarantees.
Gateway and antenna requirements, handoff to the firewall or SD-WAN edge, public or static IP needs, and who configures and supports each device. Some wireless plans use carrier-grade NAT (CGNAT), which can restrict inbound connections and affect remote access, VPN termination, or on-premises servers; verify public-IP availability with the provider.
Manual or automatic changeover, detection and alerting, which applications use the alternate path, testing responsibility, and what happens when the primary returns.
What the wireless path does and does not share with the primary, including local power, equipment, and any known access or upstream dependencies.
Whether the actual site and workload support wireless as the main connection, plus the alternative wired proposal if wireless does not meet the requirement.
For a backup purchase, state the minimum applications that must work during an outage. For a primary purchase, compare normal busy-hour use and the plan for an outage of the wireless service itself. SourceNet can help scope those assumptions and compare suitable options; SourceNet is not the wireless carrier.
It may be for a qualified site whose applications, busy-hour needs, and outage tolerance fit the actual offer. Check service terms and performance at the intended equipment location; do not decide from a coverage map alone.
It can be a useful alternate medium for a wired primary. Its value depends on site signal, capacity for critical traffic, independent failure points, and a configured and tested changeover.
Fixed wireless is a way to serve a fixed location over radio. 5G is one technology that can provide it. A fixed-wireless proposal may use 5G, LTE, or another system, so check the actual service offered.
Only if the wireless service and local equipment remain available and traffic can switch to it. Test the specific failure scenario, applications, and return to the primary path before relying on it.
A different carrier can reduce some shared-provider risk, but the name alone does not prove path independence. Ask about known shared facilities, local equipment, and upstream dependencies.
Yes, wireless access can be an underlying connection in an SD-WAN design. The platform and configuration determine how traffic is monitored and moved between paths.
Match the site, primary or backup role, service type, equipment, usage terms, IP needs, support, charges, contract, and failover responsibilities before comparing price.
Bring the site address, current circuit, critical applications, and outage tolerance. SourceNet can help compare wireless as a primary path, a backup, or no fit at all.
