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

# Aircall overview

> Hand calls from the OpenCX AI phone agent to your Aircall team with the full conversation context attached to the Aircall call.

OpenCX connects to Aircall through workflows. When the AI phone agent transfers a call to your Aircall line, a workflow finds that call in Aircall and attaches the conversation context — so the human agent picking up knows who is calling, why, and what the AI already covered.

## What you get

<AccordionGroup>
  <Accordion title="A live insight card during the call" icon="id-card">
    While the transferred call is ringing or ongoing, the receiving agent sees an <Tooltip tip="A card Aircall displays in the agent's phone app during an ongoing call. It disappears when the call ends.">insight card</Tooltip> in their Aircall phone app: the transfer reason, caller sentiment, a session link — whatever your workflow puts on it.
  </Accordion>

  <Accordion title="A permanent note on the call record" icon="note-sticky">
    The same workflow can post a <Tooltip tip="Aircall calls these comments or notes. They persist on the call record after the call ends and show up in the Aircall dashboard timeline.">call comment</Tooltip> with the AI conversation summary, so the context survives after the call ends and is visible in Aircall's dashboard and analytics.
  </Accordion>

  <Accordion title="Reliable call matching, no webhooks needed" icon="magnifying-glass">
    OpenCX finds the transferred call by searching Aircall for the caller's phone number, most recent call first. The search polls briefly to absorb Aircall's indexing lag and tries both `+`-prefixed and bare phone formats, so a format mismatch never loses the context.
  </Accordion>
</AccordionGroup>

## How it fits together

1. A caller talks to your OpenCX AI phone agent.
2. The AI decides to transfer and forwards the call to your Aircall number (a **Phone** transfer destination pointing at the Aircall line).
3. The transfer fires the **Voice Call Transferred** workflow trigger.
4. The workflow's **Post Call Context to Aircall** action searches Aircall for the caller's number, finds the just-arrived call, and posts the comment and/or insight card.

<Note>
  Aircall is a closed cloud PBX — calls reach it over the regular phone network, not via direct SIP. Point a **Phone**-type transfer destination at your Aircall number. The caller's number is preserved on the forwarded leg, which is exactly what the workflow searches by.
</Note>

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="Connect" icon="plug" href="/integrations/aircall/connect">
    Generate an Aircall API ID and token.
  </Card>

  <Card title="Post Call Context Action" icon="phone-forwarded" href="/integrations/aircall/post-call-context-action">
    Configure the workflow action end to end.
  </Card>

  <Card title="AI Phone agent configuration" icon="gear" href="/phone/agent-config">
    Transfer destinations and workflow hooks on the phone agent.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/integrations/aircall/troubleshooting">
    Call not found, credential errors, comment limits.
  </Card>
</CardGroup>