Is OpenPhone HIPAA compliant?
Business phone and texting app, formerly OpenPhone. Quo offers a BAA on its Business and Scale plans, requested through a form.
Signs a BAAConditional
Quo signs a Business Associate Agreement only under specific conditions. Customers on the Business or Scale plans can request a BAA through Quo's form.
A BAA alone does not make its use HIPAA compliant: you remain responsible for configuring it securely and covering it in your risk analysis.
Source: Quo Resource Center — Security and compliance · checked
Choosing a tool is one part of HIPAA. See everything you need to have in place → · Managing several vendors? Free Vendor & BAA Register →
BAA details
| Signs a BAA | Conditional | Quo Resource Center — Security and compliance |
|---|---|---|
| Plans that include a BAA | Business ($23 per user/month billed annually, $33 monthly), Scale | Quo — Pricing |
Limitations
- Quo's HIPAA guidance excludes text messaging (SMS/MMS), third-party integrations and connected services, and analytics sent to platforms outside the BAA from the Covered Services under its BAA. Do not assume that signing the BAA covers patient texting or connected apps: confirm contractual coverage for the actual processing before sending PHI, or use another covered channel. Quo suggests patient consent and limited PHI for texts; consent alone does not replace the contractual safeguards a service that stores PHI needs. source
- Not on the Starter plan. source
Against our criteria
| BAA without a sales process | No — Requested through a form. | Quo Resource Center — Security and compliance |
|---|---|---|
| BAA on entry-level team plans | No — Business and Scale only, not Starter. | Quo Resource Center — Security and compliance |
Alternatives
- 8x8 X Series →BAA: conditional
- Dialpad →BAA: yes
- Google Voice →BAA: conditional
- Nextiva →BAA: yes
- RingCentral RingEX →BAA: yes
- Weave →BAA: yes