Cloud platform
Confirm what the hosted service supplies, then keep its availability separate from whether a particular office can reach it.
Reliability planning guide
Plan around the failure that matters.
Cloud availability and office reachability are different questions. Use this guide to identify local dependencies, compare path behavior, and prepare a location-specific continuity review.
Start with the complete path
A healthy cloud service cannot carry traffic through a disconnected office.
Document each dependency instead of treating “the internet” or a hardware model as the whole continuity plan.
Connection paths
Inventory every wired and cellular path, how each is delivered, and whether two ordered services actually provide useful path diversity.
Managed edge and local network
Include the router, switches, Wi-Fi, cabling, traffic prioritization, configuration, monitoring, and the equipment each user depends on.
Power and people
Identify what stays powered, who detects a problem, who can request or perform recovery, and how restoration will be checked.
Compare behavior, not labels
Four designs answer different continuity requirements.
The hardware name does not establish the number of paths, activation behavior, available capacity, or expected outcome.
Managed edge
A managed edge can prioritize voice traffic, provide visibility, and support remote management. It does not remove the remaining risk of a single office connection.
Dual-wired SD-WAN
Two appropriately designed wired connections can support live failover after delivery, path independence, capacity, and configuration are confirmed. Two orders do not by themselves prove diversity.
Provisioned cellular recovery
Heritage can remotely activate a compatible provisioned cellular option when requested and needed. This is manually activated cellular recovery—not automatic failover or a continuously available path.
Persistent cellular backup
A provisioned cellular connection may remain available as an additional path according to the selected configuration. “Persistent” describes path availability, not how traffic selects it; selection behavior must be confirmed. Signal, local conditions, service, capacity, competing traffic, and configuration still affect suitability.
Failure-mode review
Ask what remains usable after a specific dependency fails.
Work through more than a primary-ISP outage. A second connection cannot compensate for every local or upstream failure.
- Primary path unavailableWhich configured path remains, how is it selected or activated, and what traffic must it carry?
- Local equipment unavailableWhich router, switch, Wi-Fi, cabling, phone, or endpoint dependency prevents users from working?
- Power unavailableWhich network and user equipment remains powered, for what planned operating window, and who verifies it?
- Office users unreachableWhich eligible inbound calls should route to another location, team, or mobile destination?
Location worksheet
Bring evidence, requirements, and ownership to the design review.
This worksheet produces questions—not a configuration or guarantee.
Review the bounded RabbitRun product recordPaths and delivery
- Primary and alternate wired services
- Known delivery routes and shared dependencies
- Cellular conditions and service state
- Traffic and capacity required during recovery
Local environment
- Managed edge, switches, Wi-Fi, cabling, and endpoints
- Voice and competing traffic
- Power dependencies and planned backup
- Users working on-site, remotely, or elsewhere
Expected behavior
- Which paths remain provisioned and available
- How traffic selects an alternate path, including whether Heritage must activate it manually
- Eligible alternate inbound-call routing during an outage
- Detection, activation, escalation, restoration, and test owners
Facts to confirm
- Selected hardware and enabled services
- Coverage, capacity, configuration, and limitations
- Provisioning, recurring service, activation, and usage charges
- Support process without assuming a resolution time
Keep the conclusion bounded
Do not turn one component into a complete-path assurance.
QoS is not a second path
Traffic prioritization can help manage contention on a working path. It does not make an unavailable connection reachable.
Cellular is not unlimited capacity
Suitability depends on signal, local conditions, selected service, configuration, workload, and competing traffic.
Alternate routing is separate
Routing eligible inbound calls elsewhere can help when local users cannot answer, but the destinations and call behavior must be defined and tested.
“Failover” needs a named design
Dual-wired live failover, a persistent cellular path, and manually activated cellular recovery must not be represented as interchangeable.
Next step
Review one location and one failure mode at a time.
Heritage can use the completed worksheet to evaluate the path options and the facts that still require confirmation.