A.I. Phone | Standard Recordings
Standard-call webhook that logs the summary, tags answered/unanswered, and enables Call-only DND when the contact requests it.
When any standard AI voice call concludes, this automation fires via webhook — finding the contact, logging a call summary note, and extracting conversation data into the contact record. It checks whether the call was answered or not, tagging accordingly. Unanswered calls exit cleanly with the appropriate tag. For answered calls, the automation runs a DND check — if the contact has requested DND, it enables the restriction immediately. If no DND preference exists, the contact exits cleanly with the answered tag applied.
This is the compliance and data integrity layer for all standard AI voice interactions. Every call is logged, every outcome is tagged, and every DND preference is respected automatically — without anyone on the team needing to manually update records or check compliance status. The DND logic is particularly important for businesses operating under Australian communication regulations — automated enforcement means the business never accidentally contacts someone who has opted out, protecting both reputation and legal standing.
This automation is the operational backbone that runs underneath every standard AI voice interaction — the equivalent of a reliable filing system that ensures every call leaves a clean, accurate record in the CRM. While automations 5 (Inbound) and 5 (Callback) handle specific call scenarios with dedicated follow-up logic, this automation handles the broader standard call category — ensuring full coverage across all AI voice interactions regardless of type. Together the three recording automations create a complete, compliant, and fully logged AI phone system.
Process inbound AI phone call webhooks by locating the correct contact, recording a detailed call summary, updating call information, classifying the call outcome, and enabling Call-specific Do Not Disturb when requested during the conversation.
The build — trigger → steps → branches
Inbound Webhook
Inbound Webhook
Triggered whenever the external AI voice platform sends call information to the webhook. Typical webhook data includes contact phone number, call transcript, call duration, call status, and recording URL.
Find Contact
ActionFind Contact · Contact Phone Number = {{inboundWebhookRequest.lead.phone_number}}
Locate the correct CRM contact before processing the AI call results.
Add Call Summary Note
ActionAdd Note · AI Voice Recording (transcript, duration, status, recording URL)
Create a complete audit trail of the AI phone conversation directly on the contact record.
Update Contact Fields
ActionUpdate Contact Fields · Voice OS | Call Status, Voice OS | Call Back Time
Store the AI call status; save the callback placeholder received from the webhook for future processing.
Was the Call Answered?
Voice OS | Call Status contains "complete" — contacts who successfully completed an AI phone conversation.
Add Answered Tag
ActionAdd Contact Tag · ai call | answered
Identify contacts who successfully completed an AI phone conversation.
Did the Contact Request Do Not Disturb?
If / ElseDND Requested / No DND
Branch on whether the contact requested Do Not Disturb during the call.
DND Requested · Enable Do Not Disturb
ActionEnable DND · Calls Only
Prevent future outbound AI phone calls while allowing SMS, email, and other communication channels to continue normally.
No DND · End
ActionNo further actions configured
Contact completes the workflow after being tagged.
Add Not Answered Tag
ActionAdd Contact Tag · ai call | not answered
Identify contacts who did not answer the AI phone call; allow downstream automations and reporting to target missed calls.


