Voice-Agent Alert Emails Missing Post-Call Data

This article explains why a voice-agent alert email can arrive containing only the caller's phone number, with the call summary, recording link, and tags left blank. It applies to Octacer automation workflows that send operator alerts after a voice-agent call ends.

After reading this article, you will understand:

To apply the fix described here, you need:

• Access to the automation workflow configuration for the voice-agent alert
• Ability to view the workflow's trigger settings and email composition step
• Understanding of the difference between call-end and analysis-complete events in your voice platform

Call-end vs. analysis-complete

Voice platforms typically emit two distinct events for a single call:

The analysis.complete event fires later because the platform must process the audio, generate a transcript, extract a summary, and apply tags. This processing takes time after the call itself has ended.

Alert email composition

The alert workflow composes its email body from fields passed into the workflow. If the workflow triggers on call.end, the summary, recording, and tag fields are empty because the analysis has not finished yet. Only fields available at call-end — most notably the caller's phone number — are populated.

The workflow trigger is configured to fire when the call ends. At that moment:

• The phone number is available because it is known at the start of the call
• The summary is blank because transcription and summarization have not completed
• The recording link is blank because the recording is still being processed
• Tags are blank because tag assignment happens during post-call analysis

Confirm this diagnosis before changing anything.

1. Open the voice-agent alert workflow.
2. Inspect the trigger event. Look for a call-end event such as call.end or call.ended.
3. Check the email composition step. Confirm that the body references summary, recording, and tag fields.
4. Review a recent alert email that contained only a phone number.
5. In the voice platform, locate the same call and check whether summary, recording, and tags were populated after the call ended.

If the platform has the enriched fields but the alert email does not, the trigger timing is the cause.

Step 1 — Change the trigger to the analysis-complete event

Open the workflow trigger configuration and change the event from the call-end event to the analysis-complete event. The exact event name depends on your voice platform. Common options include:

• analysis.complete
• call.analysis_completed
• post_call_analysis.finished
• recording.ready

Use the event your voice platform exposes for post-call analysis completion.

Step 2 — Keep call-end as the sole trigger

Replace the call-end trigger entirely. Do not configure the workflow to fire on both events.

If the workflow fires on both, you will receive one incomplete alert at call-end and one complete alert after analysis finishes — which duplicates notifications and leaves the incomplete email in the operator's inbox.

Step 3 — Add a guard for the enriched fields

In the email composition step, add a condition that requires the summary field to be present before sending. This prevents an alert from sending if the analysis-complete event fires but the enriched data is unexpectedly missing.

An illustrative condition might look like:

IF summary is not empty THEN send alert email

Step 4 — Re-test with a live call

Place a test call and let it run through the full post-call analysis.

Verify the following:

• The alert arrives after analysis completes, not at call-end
• The email contains the call summary
• The recording link is present and resolves
• Tags are populated
• The caller's phone number is still included

Step 5 — Monitor the next production calls

For the next several production calls, confirm that alerts arrive complete. Also verify that you are not receiving duplicate alerts for the same call.

After the fix:

• The alert email arrives after the analysis finishes, not at call-end
• The email body includes the summary, recording link, tags, and phone number
• Only one alert is sent per call
• Operators receive actionable information on the first alert

This fix applies to workflows where the voice platform provides a distinct analysis-complete event with enriched fields. It does not apply when:

If your platform provides no analysis-complete event, you cannot trigger the alert on one. In that case, options include delaying the alert with a scheduled wait step before composing the email, or polling the platform for analysis status before sending. Confirm which mechanisms your voice platform supports.

The analysis-complete event does not appear in the trigger options

Likely cause: Your voice platform names the event differently, or does not expose it as a webhook trigger.

Check: Review the voice platform's event documentation and webhook configuration.

Resolution: Use the platform's actual event name, or configure the workflow to poll the platform's API for analysis status instead of relying on an event trigger.

The alert still arrives with only the phone number after changing the trigger

Likely cause: The workflow is still firing on the call-end event, or the trigger change was not saved and published.

Check: Inspect the trigger configuration in the live version of the workflow, not just the draft.

Resolution: Confirm the analysis-complete event is the active trigger, publish the workflow, and place a new test call.

Two alerts arrive for the same call

Likely cause: The workflow is configured to fire on both call-end and analysis-complete events, or two workflows exist that both handle the same call.

Check: Review the trigger configuration and search for other workflows subscribed to the same voice platform events.

Resolution: Remove the call-end trigger and delete or disable any duplicate workflow.

The alert arrives complete but delayed longer than expected

Likely cause: The voice platform's post-call analysis takes longer than the operator team expects.

Check: Review the platform's typical analysis duration and compare it to the delay between call-end and alert delivery.

Resolution: This is expected behavior. If the delay is unacceptable, confirm whether the platform offers a partial-analysis event, or discuss notification expectations with the operations team.

• Configuring operator alert notifications for voice-agent calls
• Working with voice platform webhook events
• Handling missing fields in automation email composition
• Scheduling delayed actions in workflow automation