Voicemail to Email Setup for Australian Businesses (2026)

Voicemail to email sends a recorded voicemail as an audio file attachment (usually MP3 or WAV) to a nominated email address whenever a caller leaves a message. The staff member receives it in their inbox, can listen from any device, and can reply or call back without needing to dial in and navigate a voicemail system.

For a business with multiple staff sharing call handling, voicemail to email also allows messages to be shared across a team: the voicemail arrives in a shared inbox that the whole team monitors, rather than sitting silently in an extension voicemail box that one person checks intermittently. This guide covers how the feature works, how to configure it on the most common Australian business phone platforms, and how to troubleshoot the most common delivery failures.

If your business does not yet have an auto-attendant set up to route calls to voicemail correctly, see our auto-attendant setup guide first.

How Voicemail to Email Works

When a caller reaches a voicemail box and leaves a message, the phone system saves the recording as an audio file. Voicemail to email takes that audio file, attaches it to an email with the caller's number, the time and date, and any other metadata available, and sends it via SMTP (the same email delivery protocol used for regular email) to a configured address.

The email is sent by the phone system itself, either using the phone system provider's own outbound email server or an SMTP relay you configure (such as your Microsoft 365 or Google Workspace email account). This distinction matters because the delivery reliability and spam filtering behaviour are different depending on which sending path is used.

Some platforms also offer voicemail transcription: the audio is converted to text and the transcription appears in the email body, so the recipient can read the message without listening to the audio. Transcription accuracy varies by platform and by caller accent. Australian English is generally handled well by major platforms but regional accents and background noise reduce accuracy.

Key Decisions Before You Configure

Missed voicemails are missed business. Voicemail to email is one of the simplest features to enable on a cloud phone system and one of the highest-value. If your business is on a cloud phone system and voicemail to email isn't configured, it is worth doing today.

Some phone systems can delete the PBX copy after emailing it, while others provide configurable retention settings; check the options for the specific platform. You can also configure voicemail to email to send to a shared team inbox rather than individual addresses, so messages are visible to whoever picks up first. Whether voicemail to email is included or charged separately varies by provider and plan tier.

Before opening the configuration portal, decide:

• Individual mailbox delivery or team inbox delivery? Per-extension voicemail to email sends messages to that extension holder's email. A ring group or queue voicemail sends to a shared address. For small businesses, a shared inbox that the whole team monitors is usually more reliable than relying on a single person to check their extension voicemail.
• Delete after email delivery? Some platforms offer deletion after email delivery; others use configurable retention periods, so confirm the behaviour on the specific system. This keeps the voicemail box from filling up but means if the email is lost or filtered to spam, the message is gone. For compliance-sensitive businesses, keep the voicemail in the system and deliver to email as a copy.
• Use the provider's SMTP server or your own? Provider-hosted voicemail email can sometimes be filtered as spam; the cause may involve authentication, domain alignment, sender reputation or recipient filtering. Using an authenticated relay may improve alignment and deliverability when configured correctly, but it does not guarantee inbox delivery.

Setup on Maxotel cloud phone system

Maxotel's Hosted PBX includes voicemail to email as a standard feature, configured current as of 2026 via a separate Voice Mailbox object rather than directly inside an extension: you create a Voice Mailbox, set its email delivery and options, then assign it to the extension or call flow that should use it.

Per-extension voicemail setup

In the Maxotel portal:

1. Go to Voice Mailboxes and create a new Voice Mailbox (or edit an existing one).
2. Set a PIN (used to retrieve voicemail by phone if needed) and a greeting: upload an audio file or use the platform's default.
3. Under the mailbox's email options, enable email delivery and enter the destination address, individual or shared inbox. Set message retention according to your policy; confirm in the current portal whether an option to remove the copy in the mailbox after email delivery is available for your account, this is not guaranteed on every configuration.
4. Assign the Voice Mailbox to the extension (or ring group/queue timeout destination, see below) that should use it.
5. Save and test: call through to voicemail, leave a test message, and verify delivery to the nominated email address.

If the email does not arrive promptly, check the spam folder and verify the configured destination address. Maxotel sends voicemail emails from its platform domain, which may be unfamiliar to your email system's spam filter on the first delivery.

Ring group voicemail

For voicemail to email on a ring group or queue (the main business line voicemail, not a specific extension), set the ring group or queue's timeout destination directly to Voice Mailboxes, New Voice Mailbox, rather than routing to a dummy extension. That Voice Mailbox's email delivery setting routes messages to a shared team inbox.

This is the most robust configuration for a small business: all missed calls on the main number, regardless of which staff members were unavailable, land in a single shared mailbox that the team monitors. Combine this with a clear team process for who responds to messages and by when, and no voicemail message goes unactioned.

Setup on 3CX

3CX V20 handles voicemail to email delivery through its system-wide email configuration, which can be set up through a Microsoft 365 or Google Workspace integration, a service such as SendGrid, or a custom SMTP relay. Before individual voicemail to email settings will work, the 3CX Admin Console must have a working outbound email configuration under one of these methods.

System-level SMTP configuration

In the 3CX Admin Console (V20):

1. Go to the system email settings.
2. Where 3CX is integrated with Microsoft 365 or Google Workspace, configure system email through that integration rather than entering raw SMTP credentials, this is the current preferred method and avoids the account-level authentication issues that plain SMTP username/password setups run into.
3. If you are not using either integration, configure Custom SMTP with your relay's documented host, port and authentication details (a service such as SendGrid, or your own authenticated relay).
4. Set the From address to your business email address (e.g., [email protected]).
5. Send a test email from the console to confirm the configuration is working before configuring individual extensions.

Note that SMTP authentication, SPF and DKIM are separate mechanisms: successfully authenticating to a relay does not by itself mean your outbound mail passes SPF or DKIM. See the SPF/DKIM section below.

Per-user voicemail in 3CX

Once system email is configured:

1. In the Admin Console, go to Users and select the user to configure.
2. Set the user's email address on the General tab, then use the Voicemail tab to enable voicemail and select the required email-delivery option.
3. Set the voicemail PIN and greeting.
4. Optionally enable voicemail transcription if your 3CX licence and edition include it.
5. Save and test by calling the user's extension and leaving a message.

For Ring Group or Queue voicemail in current 3CX, use the native voicemail handling under the Ring Group's or Queue's own notification/call-handling settings (greeting, email delivery, and in supported configurations distributing the message to member mailboxes or additional recipients) rather than routing to a separate dummy extension.

Setup on FreePBX

FreePBX voicemail to email relies on the Asterisk voicemail module and a working outbound email path from the server. Current FreePBX 17 runs on Debian 12 and requires a working outbound mail configuration. This can be configured through System Admin Email Setup where the PRO module is available, or manually at operating-system level. The outbound mail configuration is an important point to check when FreePBX voicemail email fails.

Configure the SMTP relay on the FreePBX server

FreePBX uses the system's mail transfer agent (commonly Postfix) to send voicemail emails. The built-in direct-send configuration can receive higher spam scores or fail where network or recipient policies reject direct SMTP, so an authenticated external relay is often preferable. The solution is to configure Postfix to relay outbound mail through an authenticated SMTP relay.

FreePBX 17 / Debian 12 (current): package installation and paths follow Debian conventions (apt, not yum). Verify the exact package names and Postfix configuration steps against current Sangoma FreePBX 17 documentation before making changes, since exact paths can change between releases. The general steps are: install the Postfix SASL authentication support for your distribution, add relay configuration in Postfix pointing to your chosen provider's SMTP host with TLS and authentication enabled, create and compile the SASL password map with your relay credentials, then reload Postfix and send a test message.

For Microsoft 365 relays, note that Microsoft is retiring Basic Authentication (plain username/password) for SMTP AUTH; check current Microsoft documentation for the supported authentication method before relying on a username/password relay configuration long-term.

Legacy FreePBX 16 / older CentOS-based FreePBX Distro systems: these used yum-based package management (e.g. yum install cyrus-sasl-plain) and typically logged mail activity to /var/log/maillog. Do not apply these commands or paths to a current FreePBX 17/Debian 12 system.

Configure voicemail per extension in FreePBX

Once the SMTP relay is confirmed working:

1. In the FreePBX Admin panel, go to Applications, then Extensions, and open the extension you want to configure.
2. On that extension's Voicemail tab, enable voicemail and enter the destination address in the Email Address field. Menu paths shift between FreePBX releases, so check current Sangoma documentation if your build differs.
3. Set the voicemail PIN and greeting.
4. Under Attach, set to Yes to include the audio file. Under Delete Voicemail, set based on your retention policy.
5. In Voicemail Admin, which holds the system-wide voicemail defaults, set the From address to a legitimate business email address that your relay account has permission to send as.
6. Save and test by dialling the extension and leaving a message.

For additional FreePBX configuration guidance including SIP trunk setup and security hardening, see our FreePBX setup guide for Australian businesses.

Troubleshooting Voicemail to Email Delivery

Common failure points to check include the following:

1. Spam filtering

Check the spam or junk folder first, every time. Voicemail emails sent from a phone system's own server domain (not your business domain) are frequently flagged by modern spam filters. If emails consistently land in spam, inspect their authentication results and follow the actual sending service's SPF, DKIM and DMARC instructions. Changing relay helps only when the new path is correctly authenticated and aligned. Add a safe sender rule for the voicemail sender address as an interim measure.

2. SPF and DKIM failures

SMTP authentication, SPF and DKIM are separate mechanisms. If your phone system authenticates to an external relay (Microsoft 365, Google Workspace, SendGrid or another service) to send voicemail emails, the recipient generally sees mail delivered by that relay's own outbound infrastructure, not directly from your PBX's public IP. SPF must authorise the actual sending infrastructure for your domain, which for most cloud phone system platforms and relays means following that provider's documented SPF/DKIM setup instructions, not simply adding your PBX's own IP address. DKIM must also be enabled by whichever service actually signs and sends the outbound message. Authenticating successfully to the relay does not, by itself, guarantee an SPF or DKIM pass. Your cloud phone system company's or relay provider's documentation will specify what needs to be added to your domain's SPF record and how to enable DKIM.

3. Wrong email address configured

Verify the exact email address configured in the voicemail settings matches the actual inbox you are checking. A typo in the extension or domain is one of the most common causes of voicemail delivery failures, and the phone system will not report a delivery error visibly. Test by sending a test voicemail and immediately logging in to the exact inbox configured to check.

4. Audio attachment blocked by email security

Some corporate email security systems block incoming emails with audio attachments (WAV, MP3) as a security measure. If voicemail emails arrive but with no audio attachment, check whether your email provider or IT security configuration is filtering audio file types. The workaround is to configure the phone system to send voicemail emails with the audio as a link rather than an attachment, if the platform supports it, or to whitelist the specific audio file extensions at the email security layer.

5. SMTP authentication failure

For FreePBX and self-hosted 3CX deployments, SMTP authentication failures prevent any email from sending. On FreePBX 17/Debian, check the Postfix logs normally found under /var/log/mail.log and related mail.* files. On 3CX, use the Admin Console Activity Log and generated support logs. Common causes: the SMTP password changed (especially if the relay account uses a multi-factor authentication app password that was rotated), the relay account was locked for suspected abuse, or SMTP AUTH is not enabled on the account.

Best Practices for Voicemail to Email

Use a dedicated shared voicemail address. Send voicemails to a shared address like [email protected] rather than to an individual's personal inbox. This ensures messages are accessible to the whole team, survivable if a staff member leaves, and easier to monitor with a shared response SLA.

Keep the voicemail greeting short and include a callback timeframe. Tell callers their message will be returned, and within what timeframe. A greeting that says "Please leave your name and number and we will return your call within one business day" sets a clear expectation and reduces follow-up calls from people who are unsure whether their message was received.

Set a retention policy. Decide whether voicemails are deleted from the phone system after the email is sent. Compliance-sensitive businesses should determine applicable retention, access, security and deletion requirements with appropriate professional advice; keeping both a PBX copy and an emailed copy does not by itself create independent or compliant recordkeeping. For general businesses, deleting after email delivery prevents the voicemail inbox from filling up.

Test delivery monthly. Voicemail to email delivery can break silently: SMTP credentials expire, SPF records change, or spam filter policies update. A monthly test call that leaves a message and confirms email delivery takes 2 minutes and prevents the silent accumulation of unread voicemails.

Connecting Voicemail to the Rest of Your Call Flow

Voicemail to email works best when the rest of your call flow is configured correctly:

• Your after-hours routing should direct calls to voicemail when the office is closed, not just let calls ring out. A caller who reaches an unanswered ringing line hangs up. A caller who reaches a voicemail greeting leaves a message.
• Your ring group or hunt group should have a final overflow destination of voicemail after a set number of ring cycles, so calls that nobody answers eventually reach voicemail rather than timing out.
• If your business uses an auto-attendant, confirm that the voicemail option in the menu routes to a voicemail box that has email delivery configured. An unconfigured voicemail box on a menu option that callers regularly select is a common source of unrecovered messages.

What Most Businesses Get Wrong

Configuring voicemail to email but not testing the full chain. The configuration portal says email delivery is enabled, so the business assumes it is working. The voicemail emails go to spam, or the SMTP relay fails silently, and messages accumulate unread while staff assume nobody is leaving messages. Test from a caller leaving a message through to an email arriving in the target inbox before declaring the feature working.

Routing voicemail to a single person's inbox. If the staff member who receives voicemail emails is sick, on leave, or leaves the business, messages stop being actioned. Use a shared inbox that two or more team members monitor, with a clear ownership protocol for following up.

Not setting up voicemail on the main business number at all. Many businesses configure desk phone extensions but leave the ring group or main number voicemail unconfigured. Callers who cannot reach anyone get silence or a confusing error instead of an opportunity to leave a message. At minimum, configure a ring group voicemail with a basic greeting that tells callers their message will be returned.

Your Next Steps

Configure voicemail to email in this order:

1. Create a shared voicemail inbox address (e.g., [email protected]) if you do not have one.
2. Where the platform supports a custom SMTP relay, configure it using the mail provider's current authentication and domain-alignment requirements; otherwise follow the phone-system provider's delivery guidance.
3. Enable voicemail to email delivery on each extension and on any ring group or queue voicemail boxes.
4. Record a professional greeting for each voicemail box, including a return call timeframe.
5. Add the voicemail sender address as a safe sender in your email system.
6. Test by calling each voicemail box from an external phone, leaving a message, and verifying delivery.
7. Set a monthly calendar reminder to run a delivery test and check SMTP credentials are still valid.

Voicemail-to-email is one component of a fully configured cloud phone system setup. Our guide to setting up business phones on the NBN in Australia covers the full configuration sequence , from NBN connection quality checks through to ring group setup, after-hours routing, and voicemail configuration , with AU-specific guidance for each step.

Voicemail-to-email availability and pricing vary across Australian cloud phone providers and plan tiers. Our guide to the best phone system for small business Australia identifies which providers include it in their base plan, which charge as an add-on, and which have the most reliable email delivery for voicemail notifications.

What Does Voicemail to Email Cost?

Some providers include voicemail to email and transcription in the base plan, while others may charge separately, this varies by provider and plan tier rather than following one universal price. Check the specific provider's current plan inclusions rather than assuming a flat industry-wide add-on price.

If your business is on a provider not covered in this guide, or if you're getting errors when testing voicemail to email delivery, tell us your provider and what you're seeing. We'll give you the specific steps for your setup. We reply personally, usually within one business day.