Block spam calls and delete the hundreds of conversations they start.
under review
J
Joe Rubin
Once you publish your AI receptionist phone number to your listings, you start getting hundreds of the same spam calls a week. They leave an automated message, then a conversation is created. If the follow up text goes out, then the spam responds and they go back and forth endlessly. This is wasting a ton of minutes and texts. We need to be able to block these and then have the conversations automatically deleted so our conversation modules aren't jammed up.
Photo Viewer
View photos in a modal
Log In
S
Scott Rutherford
Any update on this? Thanks in advance.
Jehan Zouak
Merged in a post:
AI Voice needs spam controls (block numbers + mark as spam + screening rules)
D
Dave Hooper
Problem:
AI Voice still lets junk/repeat callers through. Deleting conversations doesn’t stop repeat calls, so users end up constantly cleaning spam. Repeat spam can also drain calling minutes (and cause overages when minutes are capped).
Request- Add basic spam/call management tools:
- Block number (blacklist) from call log/conversation (one click)
- Mark as spam (optionally auto-block + move to Spam folder)
- Rules for unknown/suspected spam, e.g.:
--unknown → voicemail / silent inbox
-- suspected spam → require “Press 1 to continue”
-- repeat caller rate limit (cooldown / auto-block after N calls)
Why it matters:
Less inbox cleanup, fewer disruptions, prevents spam from burning minutes.
Success criteria:
Blocked numbers never reach AI Voice (no minutes used), and spam can be flagged/hidden in <5 seconds from the call log.
S
Scott Rutherford
I've interacted with the Vendasta helpdesk team and their solution is to issue a new number. I don't think this is the solution for a host of reasons (e.g. marketing material, online directories). This has to be solved as we are pitching to SMBs an AI Receptionist as a cornerstone for their operations. It's got to be solid.
Architectural Framing: Spam Call Mitigation
Spam calls reaching the AI receptionist should be treated as a voice infrastructure and systems integration problem, not just an AI problem. The AI layer is downstream and is inheriting deficiencies from upstream controls.
Effective mitigation requires evaluating the entire inbound call architecture, with clear ownership and responsibility at each layer.
- Telephony Provider (Voice Network)
The underlying carrier or VoIP/SIP provider responsible for call origination and delivery. This layer governs call authentication, reputation scoring, signaling metadata, and the earliest opportunities for blocking or degrading spam traffic.
- Call Filtering / Spam Detection Layer
The pre-answer filtering controls applied before calls reach application logic. This may exist at the carrier level, as an integrated third-party service, or as a Vendasta-controlled layer. Its role is to absorb and neutralize spam so downstream systems are not forced to compensate.
- AI Receptionist / Call Handling Layer
The AI receptionist is a call handling and routing system, not a primary defense mechanism. It should operate on calls that have already passed baseline trust and validation thresholds.
Core Assertion
When spam reaches the AI receptionist, it is a signal of upstream architectural gaps. Sustainable spam mitigation must be enforced before AI engagement, at the voice network and filtering layers.
S
Scott Rutherford
Just checking it to see if any update.
S
Scott Rutherford
With all due respect, I think this needs to become a priority as its really impacting operations. Not only impacting business operations but also costing us in wasted minutes, which translates to wasted money. Not good.
Is there a way to use the HangUp capability with some instructions?
Rylan Morris - Vendasta
marked this post as
under review
Thanks everyone for sharing this. I know how frustrating it is to deal with nonstop spam calls and the extra conversations and costs they create. It makes sense that this would clutter up your workflow and take away from real customer interactions.
We really appreciate you taking the time to spell out the impact. We’re reviewing all of the related feedback around spam filtering, call blocking, and conversation cleanup, and we’ll do our best to factor this in. We need to balance this with other priorities, but your examples help us understand how important this is.
Thanks again for raising it!
T
Tom Lombardi
Rylan Morris - Vendasta - We get 10-15 spam calls daily, spam chats, and it's a waste of money and time not to mention how it screws up the stats and clutters the dashboards with junk. This should be a priority mainly for the money being spent on spam
Jehan Zouak
Merged in a post:
Mark a Conversation as Spam/Call Block
B
Brian McGuire
Ability to mark a conversation as spam and block that phone number in the future.
Jehan Zouak
Merged in a post:
AI Receptionist to gate keep sales calls
J
Jonathan Cummins
We request development for the AI receptionist to be able to gatekeep sales calls. The agent would ask for the caller's details (name, email) and then search the web/LinkedIn to identify whether the person has a sales title. The agent would then soft terminate the call. This avoids the caller eating lots of credits on our 800 number and filling our schedules with appointments that are not revenue producing for the agency.
Jehan Zouak
Merged in a post:
Voice AI – Spam Lead Notifications & Filtering Options
A
Arjun Raman
Currently seeing a high volume of spam leads during Voice AI testing, which are being forwarded to users through email notifications and negatively affecting their experience. Suggest adding a separate section or filter for Voice AI leads, along with a basic spam detection system. This would help reduce noise, enhance lead quality, and build greater trust in the feature.