Recording, transcription, voicemail and IVR triggers

Automate the post-call: act when a recording is ready, a transcript lands, a new voicemail arrives, or the contact picks an IVR option.

Jun 26, 2026

Watch this step in the video · Orders, payments, calls and more

What it is and when to use it

Beyond the call lifecycle, Omnifox offers triggers for everything that happens after the hangup: the recording, its transcript, voicemail messages and IVR menu navigation. They're the foundation for automatic summaries, AI triage and routing by the option pressed. They live under the Call triggers group in the palette.

Requirements

  • A connected voice channel and a plan with call triggers (from Conecta; IVR triggers need IVR, from Crece).
  • For recording/transcription: recording must be enabled on the channel.
  • Transcription is asynchronous (automatic transcription runs in the background), which is why there are separate "transcribed" triggers.

The available triggers

  • Recording ready (call_recording.ready): the audio is available on S3. Variables: $recording.id, $recording.duration, $recording.url.
  • Recording transcribed (call_recording.transcribed): transcription finished. Adds $recording.transcription and $recording.transcription_lang (BCP-47 language).
  • Voicemail received (voicemail.received): the contact left a message. Variables: $voicemail.duration, $voicemail.audio_url and $voicemail.transcription (empty if STT hasn't run yet).
  • Voicemail transcribed (voicemail.transcribed): the voicemail text is ready. Use it when you need $voicemail.transcription guaranteed.
  • IVR: option selected (ivr.option_selected): the caller pressed a key. Filters: Specific digit and Specific IVR menu node. Variables: $ivr.digit, $ivr.option_label, $ivr.menu_node_id.
  • IVR: abandoned before choosing (ivr.abandoned): they hung up without picking an option. Variables: $ivr.last_node_id, $ivr.last_node_type.

Steps

  1. Go to Settings → Workflows and click Create workflow.
  2. In the palette, under Call triggers, pick the trigger.
  3. Set the filters: Specific channel and Direction on all of them; the IVR one also adds Specific digit and IVR menu node.
  4. Build actions with the event variables (for example, email $recording.transcription or pass it to an AI node).
  5. Save and turn the workflow on.

Examples

  • Call summary by email: with Recording transcribed, send $recording.transcription to the responsible agent.
  • AI voicemail triage: with Voicemail transcribed, pass the text to an AI agent to classify urgency.
  • IVR routing: with IVR: option selected and filter Digit = 1, assign the conversation to the Support team.
  • Recover abandons: with IVR: abandoned before choosing, schedule a callback.

Verify it

Leave a voicemail or navigate the IVR on a real test call. Check the workflow's runs tab and confirm the variables ($voicemail.transcription, $ivr.digit) arrived with data.

If it doesn't work

  • Empty transcript: use the ...transcribed trigger, not received/ready. Transcription is asynchronous and lands later.
  • No recording: confirm recording is enabled on the channel; without it, $recording.url is empty.
  • Digit filter never matches: leave Specific digit blank to catch any key.
  • Nothing fires: check Specific channel and that your plan has the feature enabled. Always test with a real call.

Tips

  • Chain them: use Recording ready to archive the audio and Recording transcribed for text analysis; they are distinct events.
  • $ivr.option_label gives you the human-readable label ("Support") so you don't have to map digits by hand.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp