To be clear,
@Alejandro_3CX's proposed solution of sending voicemails as attachments to email is 100% valid. But, it can be a little more challenging to setup than you might expect,
especially if you do not control the mail server... and there are other disadvantages to consider.
The risk with depending on email for voicemails is... what happens if something goes wrong with the sending of the email? This is especially problematic if the email address is outside the company's normal domain.
If you are using your own mail server, it seems like 9 times out of 10 the mail server won't relay outside the domain. Sure, if you know what you are doing, you typically can configure your mail server to relay emails outside your domain, but I have had COUNTLESS arguments (hundreds) with customers over the years who swear they have configured their relay settings correctly, but they have not, and some emails never arrive. If the email does not arrive as expected, the voicemail is gone forever.
The other challenge, for me personally, is that I get a lot more emails than I do voicemails. Unfortunately, I tend to tune-out / ignore all the beeps and dings generated by so many applications. Further, because I get so many emails every day, it would not be hard for an important voicemail to get buried in a mountain of emails. The MWI on my phone is valuable to me.
Surprisingly, for some organizations (public schools in California for example) voicemails are part of the public record and can NEVER be deleted -- ever. In that case, having the ability to archive voicemails, in a similar way to Recordings, would help manage disk space on the 3CX server. We can do that with our tools.
One of these days I should add another report to our
3CX Voicemail Manager that shows the disk space utilization by user. Right now, we only show the number of voicemails.
