# Add inbound call rules to handle SPAM

**URL:** <https://devforum.zoom.us/t/add-inbound-call-rules-to-handle-spam/132232>\
**Category:** Phone\
**Tags:** phone\
**Created:** [May 1, 2025, 7:13pm UTC](https://devforum.zoom.us/t/add-inbound-call-rules-to-handle-spam/132232 "2025-05-01T19:13:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![webjive](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/webjive/32/40737_2.png) [@webjive](https://devforum.zoom.us/u/webjive)\
**Post date:** [May 1, 2025, 7:13pm UTC](https://devforum.zoom.us/t/add-inbound-call-rules-to-handle-spam/132232/1 "2025-05-01T19:13:46Z")

</div>

We get dozens of SPAM calls a week and one way we could mitigate these is to have an ability to setup an inbound call rule to either forward these to another line, voicemail, etc. The way I could see it working is you already show caller ID and right now 100% of our spam calls are labled “CITY, ST” meaning you have something like SUGARLAND, TX as the CID.

Having a rule where we could take the city, st level calls and have them be dropped or sent straight to voicemail would solve 100% of random SPAM calls.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [May 12, 2025, 6:28pm UTC](https://devforum.zoom.us/t/add-inbound-call-rules-to-handle-spam/132232/2 "2025-05-12T18:28:39Z")

</div>

Hey @webjive  
Thanks for reaching out to us!  
Have you looked into the Inbound Blocked List endpoints:

> **[Phone APIs](https://developers.zoom.us/docs/api/phone/#tag/inbound-blocked-list)**
>
> API reference for: Phone
