Zoomtopia is here. Unlock the transformative power of generative AI, helping you connect, collaborate, and Work Happy with AI Companion.
Register nowEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Learn moreKeep your Zoom app up to date to access the latest features.
Download Center Download the Zoom appDownload hi-res images and animations to elevate your next Zoom meeting.
Browse Backgrounds Zoom Virtual BackgroundsEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Zoom AI CompanionUser groups are unique spaces where community members can collaborate, network, and exchange knowledge on similar interests and expertise.
Help & Resources is your place to discover helpful Zoom support resources, browse Zoom Community how-to documentation, and stay updated on community announcements.
The Events page is your destination for upcoming webinars, platform training sessions, targeted user events, and more. Stay updated on opportunities to enhance your skills and connect with fellow Zoom users.
The Zoom Community is nominated for the 2025 CMX Community Industry Awards in the Customer Support Community category!
Vote now2023-11-20 10:49 AM - edited 2023-11-20 10:52 AM
We have a Voicemailbox for compliance, and we can't capture any data that could be tied to an employee. Is there a way to have a VM box not capture the who called #.. or anyway to mask it only for the one number?
Thanks!
2023-11-20 01:17 PM
Hello @RickCH
I haven't seen that feature in Zoom Phone; I know something exist on Zoom Meetings where you can mask the phone number of the callers but that won't help you here.
In any case, if the Caller ID is present when making the call, there will be always somehow/somewhere a way to check or trace the number (Call Logs, etc.) if the don't hide it from directly from their phone (the source) so I recommend always the user (for these situations) to hide their Caller ID directly from the Mobile Phones before making the call.
Maybe somebody else in the community might have a better answer to propose.
Vinnie.
2023-11-28 07:18 AM
Thanks for the Reply Vinnie, Does not seem like the community knows. Ill open a ticket with Zoom and see if there is any options.
Thanks!
2025-03-26 09:37 PM
Did you ever get an answer to this?
2025-03-27 06:34 AM
I ended up sending the call to a Contact Center flow. Then sending it right back to a Zoom Phone queue, but on the "Route to" box in the flow, the default option for caller ID is "Flow Entry point Number"... so the person answering the call or the VM will have the number of the queue, not the caller's #.
I did not see any way to do it inside of Zoom Phone unfortunately. Just using the flow options in contact center does not have any effect on licensing. So works out.
2025-03-27 07:09 AM
My use case is similar, it is a contact center line that is a anonymous hotline, as such the customer does not want the caller's ANI (caller ID) to be tied to any records.
In my testing I have done the following:
INBOUND to QUEUE > Route to outbound number (Zoom Phone User we defined as ANON) > Set Forwarding on ANON Zoom Phone to Destination Queue. The log files for calls coming into the queue number now read:
From. To
ANON. XXX-XXX-XXXX (Entry Point Number of Queue)
The log file is ideal, but the customer journey is not. I am digging deeper and will keep you posted.
2025-03-27 07:27 AM
Yeah, I guess the logs would have the orig callerid... we just kinda agree not to look it up as Zoom admins. The people who deal with the calls and interact with the calls and VM have no idea who it is. If you find a way to totally anonymize it, that would be even better!
Yes update this if you find anything! THanks!!
2025-03-27 08:21 AM
To add to my use case, its due to a 'request for public records' act.