The 60-second answer
Voicemail-to-email delivers messages as email with the audio attached, making them searchable, forwardable and reachable from anywhere. The trap is retention: if your PBX purges at 30 days but your mailbox keeps everything, your actual retention period is forever, and PIPEDA governs the longest one in the chain.
The message-waiting light was a 1980s solution
The blinking lamp assumed something that stopped being true: that the person the message was for would be sitting at that desk, in that building, within a useful timeframe. It also assumed the message would be listened to on that handset, retrieved with a PIN, and written down on paper by someone holding a pen.
Every one of those assumptions has failed. Staff are in vehicles, at sites, working from home, or covering for someone. The desk with the light on it may be empty for a week. Meanwhile the caller who left the message has already phoned a competitor, because they had no way of knowing their message was sitting in a building nobody was in.
What changes when messages become email
| Message-waiting light | Voicemail-to-email | |
|---|---|---|
| Where you can retrieve it | That handset, or via a PIN | Anywhere you have mail |
| Finding an old message | Sequential playback | Search by number, date, or text |
| Passing it to a colleague | Write it down and retell it | Forward the original audio |
| Proof of what was said | Your recollection | The recording itself |
| Coverage when someone is away | Nobody knows a message exists | Shared mailbox, seen by whoever is in |
| Response time | Whenever they return to the desk | Minutes |
The fourth row is quietly the most valuable one in a trades or service business. A dispute about what a customer authorised, what address they gave, or what date they agreed to is settled by a recording rather than by two recollections. That is worth more than the convenience, and it is why the feature earns its place even in businesses that receive few messages.
A voicemail nobody hears for four days is functionally a missed call with extra steps. The value of voicemail-to-email is not convenience, it is latency.
The size question, briefly
Businesses sometimes worry about mail storage. The arithmetic settles it. Telephone-quality audio is encoded at eight bits per sample, transmitted as 8-bit samples, at the standard 8,000 Hz clock rate [5] — that is 64,000 bits, or roughly 8 kilobytes, per second of speech. A one-minute message is under half a megabyte before any compression, and typically far less after it.
A business receiving thirty messages a day at a minute each accumulates roughly 4 GB a year at worst. Voicemail is not what fills a mailbox. Attachments from suppliers are.
The trap: your retention period is the longest one in the chain
Here is the part that is genuinely worth stopping for.
PIPEDA requires that personal information be retained only as long as necessary for the purpose it was collected, and asks organizations to develop retention guidelines including minimum and maximum retention periods [1]. Voicemail is personal information in almost every case — callers state their names, their numbers, and their circumstances [2].
Now consider what voicemail-to-email actually does. It takes audio governed by your phone system's retention setting and copies it into a mail system governed by an entirely different one. If the PBX purges at 30 days and the mail system keeps everything forever, then your organisation retains that audio forever. The 30-day setting is not a retention policy; it is a setting on one of the two places the audio lives.
Worse, the audio has now been distributed. It sits in a mailbox, likely in a mail archive, probably in a backup, possibly on a phone that syncs mail, and potentially in whatever the recipient forwarded it to. If any of that is later the subject of a breach, the assessment covers all of it [3].
Configuring it properly, in five decisions
- Copy or move? Decide whether the PBX keeps the original after delivery. Keeping both is defensible; doing it by accident is not.
- Set the mail-side retention to match. This is the step that closes the trap. A retention rule on the voicemail folder, matching the PBX period, makes the configured policy the real one.
- Choose the destination type. Department lines to a shared mailbox that survives absence; personal extensions to individuals. Customer-facing lines should never land only in one person's inbox.
- Control access. Once messages are in email, they inherit your email access controls, which is precisely why account security, credential hygiene and access review matter here — the federal baseline controls for small and medium organizations are the right checklist [4].
- Know where it goes. If the mail system or the voicemail platform sits outside the province or the country, information crossing those borders in commercial activity remains subject to PIPEDA regardless of where you are based [6]. Know the answer before someone asks.
Transcription, and why to treat it as a draft
Many systems now attach a text transcript alongside the audio. It is genuinely useful — it makes messages skimmable and searchable by content rather than only by number and date, and it lets someone triage twenty messages in the time it takes to listen to three.
Two cautions are worth stating plainly. First, transcription accuracy degrades badly on exactly the things small businesses need most: proper names, street addresses, postal codes, part numbers and phone numbers spoken quickly. Never act on a transcribed address or callback number without checking it against the audio. The transcript is an index, not a record.
Second, a transcript is a second copy of the same personal information, in a different format, in the same mailbox — and text is far easier to search, copy and accidentally forward than audio is. Everything said above about retention applies to it identically, and the retention rule you set on the mail side needs to cover both.
The departure checklist nobody has
When someone leaves, three things need doing and usually only one gets done. The extension is reassigned. The voicemail box is frequently left in place, and the email delivery address is almost never revisited. The result is customer messages continuing to arrive in a mailbox nobody reads, sometimes for months, until a customer complains that they left three messages.
The fix is a four-line checklist: redirect the extension, close or reassign the voicemail box, change the delivery address, and test by leaving a message. It takes ten minutes and it is exactly the kind of task that goes undone because it is nobody's specific job. The 30 to 60 minutes of administrative changes included in a MapleReceptionist band exists to absorb precisely this sort of housekeeping.
What it costs
Voicemail-to-email is included in every band, with Canadian-hosted voicemail and retention set to your period rather than a default: $99 CAD per month up to 10 extensions, $219 up to 25, $399 up to 50, $699 up to 100, plus HST. Also included: an extension per person, auto-attendant and IVR call-flow design, business-hours and after-hours routing, SIP trunk or analogue FXO integration, and provisioning for handsets you already own. Where voicemail and call records physically live is covered in our guide to data residency and PIPEDA for hosted PBX.
Bottom line
Voicemail-to-email is one of the few phone-system features that changes behaviour rather than merely adding an option: messages get answered in minutes instead of days, and what was said is recoverable instead of remembered. Turn it on. Then spend ten minutes setting a matching retention rule on the mail side, because otherwise the retention policy you think you have is a setting on one of two systems [1], and the one that governs is the other one.