Question 1

Will a cloud phone system stay up if our office goes dark?

Accepted Answer

Yes — and the right way to say it is that the platform is rarely the problem; the network on your side of the wall is. A modern cloud phone system runs in carrier-grade US data centers with redundant upstream carriers, automatic upstream failover, and a published SLA. The risk lives at the edges: the QoS rule on your office router, a small UPS riding out the typical rural utility blip, and a wideband codec that opens a fallback path on a single ISP cut. We survey every site before cutover, define the QoS profile, and ship the platform-side config with a one-week baseline on the line you choose so your MOS scores and dropped-call rate are measured, not assumed. 30-day Archiving is on for every seat by default, so the rare incident lands in an exportable audit trail you can hand your reviewer.

Want a per-user number against your current bill?

Talk to engineering Take the 4-question qualifier

Question 2

What happens to our phones if the internet blips or bandwidth throttles?

Accepted Answer

Internet dependency is real but it is a manageable risk, not a reason to stay on the closet PBX. Every Leyline site survey produces a per-site plan: SIP/RTP traffic is prioritized on the office router so a Teams call or a Netflix stream does not crowd it out, a wideband codec falls back gracefully under 100 kbps, and a small UPS on the LAN switch covers the typical 5-minute outage. Sites on a single upstream get an LTE failover or a secondary link as part of the cutover plan. We also ship TLS for SIP signaling and SRTP for media, so the connection that survives the blip is the same pipe that keeps your voice and SMS encrypted end-to-end — a HIPAA posture most on-prem PBXs simply cannot give you.

Question 3

How does hosted VoIP compare to keeping our on-prem PBX?

Accepted Answer

The PBX hides its real cost in capex: the four-to-six-year hardware refresh, the per-seat feature licenses, the support contract, the PRI circuits, the long-distance surcharges, the tech-visit trip when somebody changes seats. A cloud phone system collapses all of that into a single per-user monthly line item the finance team can plan against — the operating-expense discipline most US small and mid-sized businesses already use for SaaS. The bill-shape comparison for a typical 25-seat US firm lands somewhere under 30% savings in year one and widens in the years the old PBX would have been re-amortised. Every seat ships the full Elevate stack — voice, video, chat, file rooms — and 30-day Archiving is in the line, not a paid add-on. The exact number depends on your inventory; we will come back with a per-user quote against your current bill and a side-by-side in plain language.

Question 4

Will the cutover itself slow down our operations?

Accepted Answer

Migration is the risk, and it is real — but it is mostly the choice of who runs the cutover window, not a natural cost of switching. A typical 5-to-50-seat firm moves in 10–20 business days end to end: a week of port coordination (we drive it), a half-day of staged user migration with a fallback path that stays live until each site signs off, and a wrap-up week for the stragglers. Hands-on engineer-led configuration is the through-line — pre-provisioned handsets ship to your address ahead of day one, the same engineer who ported your numbers signs the audit trail, and the named engineer is on the line when something needs adjusting. Larger or multi-site rollouts are scheduled in waves with a cutover plan and dates in writing before we kickoff — never a vendor-surprise portal ask.

Question 5

Does Leyline support HIPAA, and is the BAA available on day one?

Accepted Answer

Yes — and HIPAA posture is part of the platform, not an upgrade you discover mid-review. Every Leyline seat runs on the HIPAA-certified Intermedia Elevate platform with TLS for signaling, SRTP for media, encrypted-at-rest voicemails and recordings, tenant-scoped keys, and a US-resident infrastructure footprint. The Business Associate Agreement is available on day one; counter-signed at the cutover window by the same engineer who ports your numbers. 30-day Archiving is the operational floor Leyline configures by default — voicemails, recordings, message retention, and call detail records retained for thirty days in the exportable store a compliance reviewer can read on demand. Above that floor, hands-on engineer-led configuration is what makes the posture deck-readable: the role separation, the retention windows tuned to your reviewer, the secure-room setup per practice type, and the named engineer on speed-dial. The platform ships the eligibility; Leyline turns it into a working posture for the practice.

The five objections we hear most before a cutover.

What a Leyline rollout actually looks like.

Communications built for care.

Controls you can review.

Got a question that isn't here?

The five objections we hear most before a cutover.

What a Leyline rollout actually looks like.

Q1Will a cloud phone system stay up if our office goes dark?

Q2What happens to our phones if the internet blips or bandwidth throttles?

Q3How does hosted VoIP compare to keeping our on-prem PBX?

Q4Will the cutover itself slow down our operations?

Q5Does Leyline support HIPAA, and is the BAA available on day one?

Go deeper on the pieces that matter.

Communications built for care.

Controls you can review.

Got a question that isn't here?