Voicemail With Automatic AI Transcription

Missing a call after hours no longer means losing the customer. With the Voicemail node in Omnifox's IVR, when nobody can answer the caller leaves a message that gets recorded, transcribed with AI, emailed to the admin, and turned into a conversation inside your inbox. The agent reads the text without listening to the audio and replies on whatever channel they prefer. This guide builds the full flow.

What AI-transcribed voicemail is for

A traditional voicemail leaves audio that nobody plays back. The Omnifox Voicemail node closes the loop: it records, transcribes with AI, and creates the conversation. It shines in two scenarios: after hours (no one available) and overflow (all agents busy). The result lands in your inbox as a searchable text message, with the audio attached in case you want to listen.

The flow node by node

Here is the path for the after-hours case:

1. Entry node (call starts)
2. Hours/Calendar → 3 branches: in hours / after hours / holiday
3. In hours branch → Transfer to team
4. After hours branch → Play audio (notice) → Voicemail → Hang up
5. Holiday branch → Play audio (holiday message) → Voicemail → Hang up

Step 1 · Decide with Hours/Calendar

The Hours/Calendar node evaluates the call time against your business hours and holiday calendar (set in configuration). It returns three outputs. Wire "in hours" to your normal routing (for example Transfer to team) and the other two to the voicemail path.

Step 2 · Announce with Play audio

Before the voicemail, add a Play audio node that explains the situation: "Thanks for calling. We're outside business hours. Leave your message after the tone and we'll get back to you as soon as we open." On publish, Omnifox pre-generates this audio as TTS.

Step 3 · The star node: Voicemail

Connect Voicemail. This single node does all the heavy lifting:

• Records the caller's message after the tone.
• Transcribes the audio to text with AI.
• Emails the admin with the transcript and a link to the recording.
• Creates a conversation in the inbox, tied to the contact (found via {{$call.from}}), with the transcript as the first message and the audio attached.

Your team sees the request in text, with context, and can reply on WhatsApp, email, or by calling back.

Step 4 · Close with Hang up

After recording, route to a Hang up node to end the call cleanly. Optionally, before hanging up, play a quick "Thanks, we got your message."

Overflow variant: voicemail when nobody answers

Voicemail isn't only for after hours. Use it as a safety net when the queue is jammed:

1. Play audio (greeting)
2. Transfer to team (ring_all or round_robin)
3. If nobody answers within the timeout → Voicemail → Hang up

The transfer node's "no answer" edge goes straight to voicemail. Nobody rings into the void.

Pair it with Offer callback

Before sending to voicemail you can offer a friendlier option: Offer callback ("we'll call you back"). If the customer accepts, you log the request; if they decline or don't respond, it falls to Voicemail. It's a ladder of options that cuts abandonment.

Common mistakes

• Not configuring holidays. The "holiday" branch of Hours/Calendar only works if you loaded the calendar in configuration.
• A too-long announcement. The caller wants to leave their message; keep it short before the tone.
• Not watching the inbox. Voicemail creates the conversation in the inbox; make sure it's assigned to someone or a team.
• Forgetting the final Hang up. Without Hang up, the call can sit in an ambiguous state after recording.

Best practices

• Use the {{$call.recording_url}} variable if you need to pass the recording to another node, like an HTTP request to your system.
• Add a Notify an agent node after voicemail if you want an instant ping on top of the admin email.
• Drop in an Analytics event to measure how many messages people leave after hours and decide whether to extend coverage.

What lands in your inbox

When the Voicemail node creates the conversation, your team doesn't see a loose audio file: they see a card with the contact's name (or the number if they're new), the full transcript as the first message, and the recording attached. Because everything flows into the unified inbox, the conversation can be tagged, assigned to a team, prioritized, or closed just like any other channel. If the contact already existed, the voicemail attaches the message to their history, so the agent sees prior WhatsApp or email interactions and replies with context instead of starting from scratch. That continuity is what turns a plain voice message into an actionable ticket.

In Omnifox the Voicemail node ships with AI transcription built in: you don't wire up a separate service. Drag the node, connect it, and on publish it's ready, with the message turned into a conversation your team can resolve.

Want to stop losing after-hours calls? Head to Omnifox and add an AI-transcribed voicemail to your IVR in minutes.