OpenPhone

Connect OpenPhone to collect communications platforms evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In OpenPhone:

   1. Sign in to Quo (formerly OpenPhone) as a workspace Owner or admin and open Workspace Settings.
   2. Open the API tab and click Generate API key.
   3. Give the key a descriptive label without spaces (for example safeguard-readonly), then copy the key.

   OpenPhone is now Quo. Generating a key requires Owner or admin privileges in the workspace. Each key gives complete API access to the account; there is no read-only key. The docs do not say whether the key is shown only once.

   Source: quo.com, checked 2026-10-07.

   The permissions Safeguard needs. OpenPhone issues no read-only credential. Safeguard only reads with it, and you can revoke it at any time.

2. On Compliance › Connectors, open OpenPhone, click Connect, choose API token and fill in:

   Field	What to enter
   API key	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read OpenPhone and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Communications Platforms connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks