> ## Documentation Index
> Fetch the complete documentation index at: https://help.withallo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Avoma

> Send every recorded Allo call to Avoma, with Allo's transcript, so Avoma writes its AI notes

Connect Avoma and every recorded call your team makes or takes in Allo lands in Avoma, on the teammate who handled it. Avoma gets the recording and Allo's transcript, split between your teammate and the other person, and writes its AI notes from them.

## How to connect

### Create an Avoma API key

Only an Avoma admin can create an API key, and API access depends on your Avoma plan.

**1. Open the developer settings**

In Avoma, go to **Settings** > **Organization** > **Developer**.

**2. Add an API key**

Click **Add API Key**, name it `Allo`, and pick the scope **Organization - limited**. Allo uses this one key to add the calls of every teammate.

**3. Copy the whole key**

Avoma shows the API key as two parts joined by a colon (`key:secret`). Copy the whole string, including the part after the colon.

### Connect in Allo

**1. Open integrations**

Go to [**web.withallo.com**](https://web.withallo.com) and navigate to **Settings** > **Integrations**.

**2. Find Avoma**

Find **Avoma** in the list and click **Connect**.

**3. Paste your API key**

Paste the whole Avoma API key.

**4. Save and connect**

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

### Before your first call

Allo finds the Avoma user by email. Each teammate whose calls should reach Avoma needs an active Avoma user with the same email they use in Allo. If the emails differ, Avoma doesn't get the call.

## What gets sent to Avoma

After each recorded call, Allo creates a call in Avoma with:

* The call recording, which Avoma downloads
* The teammate who handled the call, as the Avoma user who owns it
* The other person on the line: name and phone number, and their email when Allo knows it
* The direction (inbound or outbound), the start and end time, and whether the call was answered or went to voicemail
* Allo's transcript, split between your teammate and the other person, which Avoma uses for its AI notes

Avoma names the call from the other person, for example **Call with Jane Prospect (+14155550123)** for an outbound call, **Call from Jane Prospect (+14155550123)** for an inbound call, or **Voicemail from...** for a voicemail. A call from a hidden number is named **Call from Anonymous**.

If Avoma refuses Allo's transcript, for example because Avoma doesn't support the call's language, Allo sends the call again without it and Avoma transcribes the recording itself.

Retrying a call never creates a second copy in Avoma.

**Sync direction:** One-way (Allo → Avoma). Nothing comes back from Avoma 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 call summary: Avoma writes its own notes
* SMS and contacts

### Very short recordings

Avoma skips very short recordings, such as a voicemail of a couple of seconds. The call still appears in Avoma, but without audio, transcript or notes.

### Changes after the upload

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

## Troubleshooting

Check the sync status of any call from the **call list on [web.withallo.com](https://web.withallo.com)**. Each call has an integration indicator showing its sync state.

> [accordion] I cannot connect my integration
>
> 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 API key, check that:
>
> * You pasted the whole key, including the part after the colon.
> * The key was created in Avoma under **Settings** > **Organization** > **Developer**, with the scope **Organization - limited**.
> * The key wasn't deleted in Avoma.

> [accordion] A call is not in Avoma
>
> Check the integration indicator on the call in the web app. The most common causes:
>
> * **No Avoma user for this teammate.** The teammate's Allo email doesn't match any Avoma user. Invite them to Avoma with the same email they use in Allo.
> * **The Avoma user is inactive.** An Avoma admin must reactivate them.
> * **The call has no recording.** Avoma 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 API key no longer works.** It was deleted in Avoma. Create a new one, then disconnect and reconnect Avoma in Allo.
>
> Once you fix the cause, retry the sync from the call in the web app.

> [accordion] The call is in Avoma without audio or notes
>
> Avoma downloads the recording and writes its notes on its side, so they appear once Avoma has finished processing the call.
>
> Avoma skips very short recordings. Those calls stay in Avoma without audio, transcript or notes.

> [accordion] The call is on the wrong person in Avoma
>
> Allo picks the Avoma user from the teammate who handled the call, matched by email. Make sure each teammate's Allo email belongs to their own Avoma user, and not to a shared or admin account.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.