Sean, your voicemail-into-client-record vision is the right pattern to stop missed-call leaks. The hard part is the phone-number match, since a lot of voicemail mailers send the from as the voicemail system's own number.
A setup that worked for me without needing a request-only upload:
1) Transcribe at the voicemail source. Point the business line's voicemail so every message is emailed as an attachment and pipe that inbox into a transcription service so you get plain text. That text is what lands in Jobber - skip storing raw audio unless it's disputed work.
2) Match on a stable field, not the inbound number. Put the Jobber client's phone in a custom field or on the address line so a lookup finds them even when the voicemail from number differs. If the number has no match, park the message in a shared "New Inbound" container - unmatched voicemails are the ones that disappear.
3) Callback fast and leave a trace. The same automation that drops the transcription into the client record can, as a side effect, schedule the callback the same day the caller dialed. Even a "left voicemail, will call back at 2pm" note beats a blank timeline.
4) Filter junk before it clogs the record. Adrianx already flagged this - expired warranties, ad resellers and website-company voicemails. A quick keyword or duration rule at the transcription step stops noise from filling the timeline.
A couple of things to watch: ring the business line through a single phone system so every voicemail email comes from the same sender. If an answering service handles after-hours, make sure their callback-forward also ties to the Jobber number. For the after-hours window in particular, forward overflow to a backup line that rings 3-4 times and drops a voicemail in your own system so you control the transcription.