Skip to main content
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

While the transferred call is ringing or ongoing, the receiving agent sees an in their Aircall phone app: the transfer reason, caller sentiment, a session link — whatever your workflow puts on it.
The same workflow can post a with the AI conversation summary, so the context survives after the call ends and is visible in Aircall’s dashboard and analytics.
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.

​
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.
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.

Connect

Generate an Aircall API ID and token.

Post Call Context Action

Configure the workflow action end to end.

AI Phone agent configuration

Transfer destinations and workflow hooks on the phone agent.

Troubleshooting

Call not found, credential errors, comment limits.