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. A customer who leaves a message and doesn't hear back within a few hours often calls a competitor before you even know they called. 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.

If you're concerned about audio files filling your email inbox, most phone systems let you delete the voicemail from the system once the email is sent, keeping storage manageable. 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. Most providers include this feature at no extra cost in their standard plans.

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? Most platforms offer an option to delete the voicemail from the phone system after sending the email. 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? Using the provider's server is simpler but can cause emails to land in spam because the sender domain does not match your business domain. Using your own SMTP relay (Microsoft 365, Google Workspace, or a dedicated transactional email service) means the email arrives from your domain and is far less likely to be filtered.

Setup on Maxotel cloud phone system

Maxotel's cloud phone system includes voicemail to email as a standard feature. Configuration is per extension and does not require any SMTP relay setup for basic delivery.

Per-extension voicemail setup

In the Maxotel portal:

1. Navigate to Extensions and select the extension to configure.
2. Open the Voicemail tab or section.
3. Enable voicemail and set a PIN (used to retrieve voicemail by phone if needed).
4. Enter the email address to deliver voicemails to. This can be an individual email address or a shared inbox.
5. Set the voicemail greeting: upload an audio file or use the platform's default. The greeting is what callers hear before leaving a message.
6. Under email delivery options, choose whether to delete the voicemail from the system after the email is sent, or retain it.
7. Save and test: call the extension, let it ring through to voicemail, leave a test message, and verify delivery to the nominated email address.

If the email does not arrive within 2 minutes, check the spam folder first. 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), configure a dedicated voicemail extension in Maxotel that the ring group overflows to when all members are unavailable or after a set ring time. That voicemail extension'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 handles voicemail to email delivery through its system-wide email configuration. Before individual voicemail to email settings will work, the 3CX Management Console must have a working outbound email (SMTP) configuration.

System-level SMTP configuration

In the 3CX Management Console:

1. Go to Settings, then Email.
2. Enter your SMTP server details. For Microsoft 365, the SMTP host is smtp.office365.com, port 587, with TLS enabled. For Google Workspace, the SMTP host is smtp.gmail.com, port 587, with TLS enabled.
3. Enter the SMTP credentials: the email account username and password (or an app password if your account uses multi-factor authentication).
4. Set the From address to your business email address (e.g., voicemail@yourbusiness.com.au).
5. Send a test email from the console to confirm the SMTP configuration is working before configuring individual extensions.

Using your own SMTP credentials means voicemail emails arrive from your own domain, pass your email provider's SPF and DKIM checks, and are dramatically less likely to end up in spam than emails sent from the 3CX system's own server.

Per-user voicemail in 3CX

Once SMTP is configured at the system level:

1. In the Management Console, go to Users and select the user to configure.
2. On the Voicemail tab, enable voicemail and enter the user's email address for delivery.
3. Set the voicemail PIN and greeting.
4. Optionally enable voicemail transcription if your 3CX licence includes it.
5. Save and test by calling the user's extension and leaving a message.

For ring group or queue overflow voicemail in 3CX, configure a voicemail extension that the group falls back to, and set the delivery email on that extension to a shared team address.

Setup on FreePBX

FreePBX voicemail to email relies on the Asterisk voicemail module and a working outbound email path from the server. FreePBX self-hosted on a Linux server requires a working mail relay to be configured at the operating system level before voicemail to email will function. This is the most common point of failure for FreePBX voicemail delivery.

Configure the SMTP relay on the FreePBX server

FreePBX uses the system's mail transfer agent (Postfix or Sendmail) to send voicemail emails. The default configuration attempts to send directly from the server, which is almost universally blocked or filtered to spam by receiving mail servers. The solution is to configure Postfix to relay outbound mail through an authenticated SMTP relay.

For a server relaying through Google Workspace:

1. Install the Postfix SASL authentication libraries if not already installed: yum install cyrus-sasl-plain on CentOS/RHEL/FreePBX Distro.
2. Edit /etc/postfix/main.cf and add relay configuration pointing to smtp.gmail.com:587 with TLS and authentication enabled.
3. Create /etc/postfix/sasl_passwd with your Google Workspace SMTP credentials and run postmap /etc/postfix/sasl_passwd to compile it.
4. Reload Postfix: systemctl reload postfix.
5. Test with a direct send: echo "Test" | mail -s "FreePBX mail test" youraddress@yourdomain.com.au.

For Microsoft 365, use smtp.office365.com:587 as the relay host. Ensure SMTP AUTH is enabled on the Microsoft 365 account in the Microsoft 365 admin centre, as it is disabled by default on some tenant configurations.

Configure voicemail per extension in FreePBX

Once the SMTP relay is confirmed working:

1. In the FreePBX Admin panel, go to Applications, then Voicemail Admin.
2. Select the extension to configure and enter the email address in the Email Address field.
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 General Settings, 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

When voicemail emails do not arrive, the failure is almost always in one of five places:

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 the emails consistently land in spam, the fix is to configure the phone system to relay through your own business email SMTP server, which has SPF and DKIM records that your email provider trusts. Add a safe sender rule for the voicemail sender address as an interim measure.

2. SPF and DKIM failures

If you are using your own SMTP relay but emails still land in spam or are rejected, check the SPF record for your sending domain. The SPF record must include the IP address or server your phone system uses to send. For cloud phone system platforms sending on your behalf, the provider's sending infrastructure must be included in your domain's SPF record, or the emails will fail SPF checks and be marked as spam or rejected entirely. Your cloud phone system company's documentation will specify what needs to be added to your SPF record.

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. Check the Postfix mail logs at /var/log/maillog on the server for authentication errors. 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 voicemail@yourbusiness.com.au 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. For compliance-sensitive businesses (financial services, medical practices, legal firms), retaining the voicemail in the system alongside the email copy creates two independent records of the message. 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., voicemail@yourbusiness.com.au) if you do not have one.
2. Configure SMTP relay on your phone system to send from your own domain rather than the provider's server.
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 is a standard feature across most Australian cloud phone system plans. 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?

Voicemail-to-email is included in most standard cloud phone plans at no extra charge. Some providers include it in all tiers. Others include it from the standard tier upward, not the entry-level tier. Where it is a paid add-on, expect $5-10 per user per month. The cloud phone plan itself runs $20-35 per user per month (inc. GST). Professional voicemail transcription (text of the message delivered to email, not just the audio file) is sometimes available as a higher-tier add-on at $5-15 per user per month.

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.