When CTM's VoiceAI (or any AI agent) answers an inbound call, CTM marks that call as Answered — not Missed. Because Dazos derives the Missed - Returned call log status directly from CTM's call status, those AI-answered calls will never automatically receive the Missed - Returned status, even if the caller was never connected to a human.
​

This article explains why the built-in Missed - Returned logic does not apply to AI-answered calls, and describes the recommended workaround using CTM tags and Dazos reporting.

The Missed - Returned status in the Dazos Call Log is triggered automatically when:

When VoiceAI answers the call, CTM classifies it as Answered. Dazos maps that status directly into the Call Log, so the built-in Missed - Returned logic never fires — regardless of whether a human ever spoke to the caller.

⚠️ Important: There is currently no native way in Dazos to auto-link an inbound AI-answered call to a later outbound callback using the Missed - Returned status. This is a current platform limitation, not a configuration error.

If your CTM account applies a tag (for example, #AI) to calls answered by VoiceAI, that tag is automatically pushed into the Dazos Call Log as a separate tag column. You do not need to map it manually — it appears automatically and can be used as a filter in reports.

This means you can use the #AI tag as a proxy for "missed" when building reports, without requiring any manual input from your team.

You can build one report in Dazos that identifies AI-answered inbound calls and checks whether an outbound callback was made — all without any manual field updates.

💡 Why All Conditions (AND)? The #AI tag is only on the inbound call record associated with the Lead — not on the outbound call. Setting the filter to All Conditions means the report returns only records where the Lead has the #AI tag and a related outbound call exists. The outbound call itself does not need to be tagged.

The report will return Lead (or Account) records where:

This gives you a count of AI-answered calls that received a callback — without any manual work from your team.

💡 Date Ranges: If no date range is set in the report, it will run as All Time. To check specific periods (e.g., yesterday, last week), set the date range directly in the report filters or use the dashboard date filter when viewing on a dashboard.

💡 No Data Showing? If the report returns no results, verify that both conditions are true for at least one record: (1) the Lead has the #AI tag, and (2) a related outbound Call Log entry exists. Try setting the date range to All Time first to confirm data exists before narrowing the range.

⚠️ This is not a "Missed - Returned" replacement: This approach does not update the Call Log status field. It is a reporting workaround that identifies the same outcome — AI-answered calls where a callback was made — without relying on the built-in status logic.

✅ Best Practice: Ensure your CTM trigger for tagging VoiceAI calls is active and consistently applying the #AI tag. The accuracy of this report depends entirely on that tag being applied to every AI-answered call in CTM.