Cloud platform
Platform availability does not establish whether a particular office can reach it.
Trust · Business continuity
Continuity is a chain—not a single uptime claim.
A useful continuity answer identifies the service layer, location, paths, power, equipment, routing, capacity, and recovery process. It does not treat one available component as proof that the complete calling path remains usable.
Configuration-specific: This page makes no uptime, recovery-time, carrier-availability, cellular-coverage, capacity, power, or service-level guarantee.
Core distinctionCloud availability is not the same as office reachability.
The cloud service may remain available while a location loses internet, power, local equipment, or a usable route to its users.
Complete-path review
State which layer the continuity answer covers.
Office connections
Each wired or cellular path has its own delivery, independence, signal, service, and capacity conditions.
Managed edge
Hardware selection and configuration determine which paths can be used and how they may behave.
Power and local equipment
Connections do not keep unpowered network equipment or phones operating. Local dependencies require separate planning.
Call routing and users
Eligible inbound calls may need a tested alternate route when a location or its users cannot answer.
Behavior must be named accurately
Three alternate-path designs are not interchangeable.
Provisioned cellular recovery
Heritage activates the compatible provisioned cellular option remotely when requested and needed.
Not automatic failoverIt is a recovery process, not a continuously available or automatically selected path. Provisioning, activation, and usage charges may apply.
Dual-wired SD-WAN
Two appropriately designed wired connections can support live failover after delivery, independence, configuration, and capacity are confirmed.
Not complete-path assuranceLocal power, equipment, upstream dependencies, and alternate call handling still matter.
Persistent cellular backup
A provisioned cellular connection may remain available as an additional path according to the selected configuration.
Not unlimited capacitySignal, local conditions, selected service, capacity, competing traffic, and configuration affect suitability.
Before relying on the design
Verify the location-specific evidence.
No model name, diagram, second circuit, or cellular label establishes the complete result by itself.
Review the RabbitRun product boundaryPath evidence
Delivery method, path independence, carrier dependencies, signal conditions, service state, and available capacity.
Configuration evidence
Selected hardware, enabled services and features, path behavior, monitoring, activation process, and responsible operators.
Local evidence
Power, network edge, switches, phones, other equipment, user locations, and tested alternate inbound routing.
Commercial evidence
Applicable equipment, connectivity, cellular provisioning, recurring service, activation, usage, and support charges confirmed for the design.
Continuity review
Ask what happens in a specific failure.
- Which component or path is assumed to fail?
- What remains powered and reachable at the location?
- Is recovery automatic, continuously available, or manually activated?
- What traffic must the remaining path support?
- Where should eligible inbound calls go if local users cannot answer?
- Who detects the event, requests or performs recovery, and verifies restoration?