Skip to main content
Connect Gong and every recorded call your team makes or takes in Allo lands in Gong, on the teammate who handled it. Gong transcribes the recording and runs its call insights on it, the same way it does for your other calls.

How to connect

1

Open integrations

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

Connect Gong

Find Gong in the list and click Connect.
3

Authorize

You’re redirected to Gong. Sign in if needed, then approve the permissions Allo asks for.
4

Done

Once authorized, you’re redirected back to Allo. One connection covers your whole Allo team.

Before your first call

Gong only accepts a call for a person it knows, and only if that person is allowed to have calls imported. Check both for every teammate whose calls should reach Gong:
  1. Same email in both tools. Each teammate needs a Gong user with the email they use in Allo. Allo finds the Gong user by that email, including Gong email aliases.
  2. Call import turned on. In Gong, a Gong admin must enable telephony call import for each of these users. Without it, Gong refuses the call.

What gets sent to Gong

After each recorded call, Allo creates a call in Gong with:
  • The call recording, which Gong transcribes and analyzes
  • The teammate who handled the call, as the call owner
  • The other person on the line: name, phone number and email when Allo knows them
  • The direction (inbound or outbound), date and duration
  • Who spoke when, so Gong keeps your teammate and the other person apart
  • Your Allo call tags, in the call title and in the Purpose field, both searchable in Gong
  • The call result (for example answered or voicemail), in the Disposition field
Sync direction: One-way (Allo → Gong). Nothing comes back from Gong 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
  • SMS and contacts

Changes after the upload

Gong doesn’t let Allo edit a call once it’s uploaded. If you add or change tags on a call after it reached Gong, 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.
This is the most common cause. Gong refuses every call for a user whose call import is off, even when the integration is connected. The setting is per user, so check it for each teammate whose calls should reach Gong.A Gong admin fixes it in Gong:
  1. Open the Team members page in Gong.
  2. Edit the teammate’s Gong user.
  3. In their data capture settings, set telephony system calls to Import calls.
  4. Save.
If the option isn’t available, enable telephony call import for your company in Gong’s Data capture settings first.Calls that failed before the fix are not sent again on their own. Retry them from the call in the web app.
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.
Check the integration indicator on the call in the web app. The most common causes:
  • No Gong user for this teammate. The teammate’s Allo email doesn’t match any Gong user. Add them to Gong with the same email, or add their Allo email as an alias of their Gong user.
  • Call import is off in Gong. See Calls are not synced to Gong: turn on call import above.
  • The call has no recording. Gong only takes calls with audio, so missed or unrecorded calls are never sent.
  • Integration disconnected. The authorization was revoked in Gong. Allo still appears connected but requests fail. Disconnect and reconnect Gong in Allo.
Once you fix the cause, retry the sync from the call in the web app.
Gong downloads the recording and transcribes it on its side. Its transcript and insights appear once Gong has finished processing the call.
Allo sets the Gong owner from the teammate who handled the call, matched by email. Make sure each teammate’s Allo email belongs to their own Gong user, and not to a shared or admin account.