Legal - Effective May 17, 2026

CallOrbit Emergency Services Disclaimer

This Emergency Services Disclaimer explains the limitations of using CallOrbit, VoIP, browser phones, softphones, SIP trunking, cloud PBX, hosted PBX, virtual PBX, and internet-based business phone systems for emergency calling.

Effective date: May 17, 2026. Review cadence: Reviewed with emergency calling rules, carrier capabilities, product coverage, and country support. Contact: support@callorbit.tech.

  • 1. Emergency Calling Is Limited
  • 2. When Emergency Calls May Fail Or Be Limited
  • 3. Customer Responsibilities
  • 4. International Emergency Calling
  • Can I rely on CallOrbit as my only emergency phone?
  • Does emergency calling work from a browser phone?

Policy snapshot

  • Effective date: May 17, 2026
  • Review cadence: Reviewed with emergency calling rules, carrier capabilities, product coverage, and country support
  • Contact: support@callorbit.tech

1. Emergency Calling Is Limited

CallOrbit is a cloud communications platform for business calling, contact center operations, messaging, routing, and productivity. It is not a replacement for traditional emergency services, public safety systems, or a dedicated emergency communications plan.

Emergency calling availability, routing, call-back number delivery, location delivery, and dispatchable location support vary by country, number type, carrier, product configuration, customer location, device, browser, internet connection, and regulatory eligibility.

2. When Emergency Calls May Fail Or Be Limited

  • Power outage, battery failure, internet outage, broadband degradation, Wi-Fi failure, mobile network failure, or device failure.
  • Browser permissions, microphone permissions, blocked scripts, headset problems, device audio issues, VPNs, firewalls, NAT, SIP blocking, or unsupported networks.
  • Incorrect, missing, stale, or unavailable registered location or dispatchable location information.
  • Use from a different address, remote work location, hotel, shared workspace, mobile location, or country than the registered location.
  • Use of non-native phone numbers, international numbers, virtual numbers, temporary numbers, forwarding, IVR, queues, or routing configurations that do not support emergency services.
  • Carrier outage, platform outage, maintenance, fraud controls, account suspension, non-payment, number status issues, or regulatory restrictions.

3. Customer Responsibilities

  • Do not rely on CallOrbit as the sole way to reach emergency services.
  • Maintain an alternative emergency calling method for every user, site, office, remote worker, and agent.
  • Tell users and agents that VoIP, browser phone, softphone, SIP, hosted PBX, cloud PBX, and virtual PBX emergency calling may be limited.
  • Keep registered location and emergency contact information accurate where emergency calling is supported.
  • Do not route emergency calls through IVR, queues, forwarding, call recording, or automation unless the emergency service configuration expressly supports it.
  • Test emergency procedures without placing live emergency calls unless local authorities permit testing and provide a non-emergency test process.

4. International Emergency Calling

Emergency numbers, emergency routing, caller location rules, and VoIP emergency obligations differ by country. A number that supports normal inbound or outbound business calling may not support emergency calling in every country or from every user location.

If your team operates internationally, you must maintain local emergency procedures for every country and location where users work.

5. No Life-Safety Use Without Written Approval

Do not use CallOrbit for safety-critical, emergency dispatch, medical alert, alarm monitoring, elevator phone, industrial safety, public safety, or high-risk use cases unless CallOrbit has expressly approved the use case in a signed written agreement and the service configuration supports it.

6. Outage Notices And Support

If CallOrbit becomes aware of a service condition that materially affects supported emergency calling, we will use reasonable efforts to notify affected customers through available service channels. Customers remain responsible for notifying their own users, agents, employees, and sites and for maintaining alternative emergency calling methods.

Quick answers

  • Can I rely on CallOrbit as my only emergency phone? - No. You should maintain an alternative emergency calling method for every office, remote user, and agent.
  • Does emergency calling work from a browser phone? - It may be limited or unavailable depending on product configuration, number type, carrier, location, browser, power, internet, and country support.
  • Who must tell agents about VoIP emergency limitations? - The customer must inform its users, agents, employees, contractors, and locations about emergency calling limitations and alternatives.