Skip to main content
Connect Chorus by ZoomInfo and every recorded call your team makes or takes in Allo is uploaded to Chorus, under the teammate who handled it. Chorus then transcribes the recording and runs its own analysis and coaching on it.

How to connect

Before you start

  • Chorus includes API access in its Enterprise package. On other packages, API access is a paid add-on. Check with your ZoomInfo account team if you’re not sure.
  • The Chorus user who creates the token needs a role with API permission. A Chorus admin can check it under Settings > Roles & Permissions.
  • Use the token of a Chorus admin. The token only sees what its user can see, and Allo needs to find the Chorus user of every teammate.

Generate a Chorus API token

1

Open your personal settings

In Chorus, open your profile, then go to Settings > Personal Settings > API Access.
2

Generate the token

Click Generate API Token and copy it.
If you don’t see API Access, your workspace may not have API access yet. Ask your Chorus customer success manager for a personal API token.

Connect in Allo

1

Open integrations

Go to web.withallo.com and navigate to Settings > Integrations.
2

Find Chorus

Find Chorus in the list and click Connect.
3

Paste your API token

Paste the Chorus API token.
4

Save and connect

Click Save & Connect. One connection covers your whole Allo team.

Before your first call

Allo finds the Chorus user by email. Each teammate whose calls should reach Chorus needs a Chorus user with the same email they use in Allo. Chorus may also require that user to hold a license that can own recordings (a Recorder license). If the emails differ, or Chorus refuses the user, the call doesn’t reach Chorus.

What gets sent to Chorus

After each recorded call, Allo uploads a new conversation to Chorus with:
  • The call recording, as an audio file
  • The teammate who handled the call, as the Chorus user who owns the conversation
  • A name that holds the call details: the direction, the other person (their name, or their phone number when Allo has no name), the start time in UTC, and the call’s tags
For example: Allo call · Outbound · Camille Martin · 2026-11-16 09:30 UTC · Pricing, Follow-up. A call from a hidden number shows Unknown caller. Chorus has no separate field for the direction, the phone number or the call time, so the name is the only place they appear. You can find calls with Chorus search by typing a contact name or a phone number. Chorus transcribes the recording and computes its own insights from the audio. Allo sends each call with its Allo call id and asks Chorus to keep that id unique, so a retried call should not create a second conversation. Sync direction: One-way (Allo → Chorus). Nothing comes back from Chorus into Allo.

What is not sent

  • Calls without a recording, such as missed calls
  • Calls from numbers that match no contact in Allo
  • Calls with a contact you marked as favorite in Allo
  • Allo’s transcript and call summary: Chorus builds its own from the audio
  • SMS and contacts

What is not linked

Chorus links a conversation to a CRM account or opportunity from the participants’ emails. An uploaded Allo call has no participant list, so Chorus doesn’t link it to an account or a deal. You find it under the teammate who owns it, not on the account page. The date Chorus shows can be the time of the upload, a few minutes after the call ended. The real start time is in the conversation name.

Changes after the upload

Allo doesn’t update a call once it’s in Chorus. If you add or change tags on a call after it reached Chorus, the change stays in Allo.

Troubleshooting

Check the sync status of any call from the call list on web.withallo.com. Each call has an integration indicator showing its sync state.
Only admins and managers of an Allo workspace can connect integrations. If you don’t see the option, ask your workspace admin or manager to set it up.If Allo refuses the token, check that:
  • You pasted the whole token, with no extra spaces.
  • The Chorus user who generated it has a role with API permission.
  • The token wasn’t regenerated or revoked in Chorus since you copied it.
Check the integration indicator on the call in the web app. The most common causes:
  • No Chorus user for this teammate. The teammate’s Allo email doesn’t match any Chorus user that the token can see. Invite them to Chorus with the same email they use in Allo, and use a Chorus admin’s token.
  • Chorus refused the user as owner. The teammate’s Chorus user may need a license that can own recordings. Ask your Chorus admin to check their license.
  • The call has no recording. Chorus only takes calls with audio, so missed or unrecorded calls are never sent.
  • The number matches no contact in Allo. Add the caller as a contact in Allo.
  • The token no longer works. It was regenerated or revoked in Chorus, or its user lost API permission. Generate a new one, then disconnect and reconnect Chorus in Allo.
Once you fix the cause, retry the sync from the call in the web app.
Chorus transcribes and analyzes the recording on its side, so the transcript and insights appear once Chorus has finished processing the conversation.
Chorus matches conversations to accounts from participant emails, and an uploaded call has none. Allo calls stay under the teammate who owns them. Search Chorus for the contact name or phone number, which are in the conversation name.