We use Aircall + Missive at our business and want a simple workflow: if an inbound call isn't answered, the conversation gets flagged (task or label) for callback. We can't build this reliably today because the Aircall integration doesn't surface the call's disposition into the conversation in any way a rule can target.

Right now an inbound missed call looks like this in Missive:

New call coming from [Caller] on Office Number.

Looking for someone available in the Office Number team…

Call ended, duration: 3 seconds

The "Call ended" line is identical for answered and missed calls, so Content conditions can't distinguish them.

We've tried every workaround in the existing rule engine:

Content rules can't tell answered from missed - the strings are nearly identical.

Delay actions don't re-check Content after the wait, so we can't catch the later "answered the call" event when it eventually appears.

"Unassigned/Unreplied and open after" assumes the team always assigns or replies on answered calls, which isn't reliable for teams using pooled ownership.

We checked with Aircall support directly, and they confirmed the data exists in their webhook payload as a missed_call_reason field, with values like agents_did_not_answer, abandoned, abandoned_in_ivr, no_available_agent, out_of_opening_hours. Missive's integration just isn't mapping it into the conversation.

What would solve it: expose Aircall's call disposition somewhere a rule can target. Either:

A new rule condition (e.g., "Aircall call status is missed" / "Aircall call disposition is X"), or

A standardized line in the call event message (e.g., "Call ended - missed (no agent available)") that Content conditions could match on.

This is a near-universal need for teams on Aircall + Missive - flagging missed calls for callback is foundational in healthcare, services, sales, and anywhere a missed call has real cost.

Thanks for considering!