Call Screening & IVR for Spam Filtering

Overview

When ad campaigns — particularly display or broad-match campaigns — generate high call volumes, a significant portion of those calls may be bot-generated or low-quality spam. A lightweight IVR (Interactive Voice Response) layer inserted in front of the client's real phone number can filter out bot calls with minimal friction for legitimate callers.

This approach is distinct from ^[1] (which filters ad clicks before they reach the site) and ^[2] (which filters form submissions). Call screening addresses the phone channel specifically.

The Problem

Ad campaigns — especially Microsoft Ads display campaigns — can generate calls at very low cost per call (e.g., $2/call) but with a high proportion of spam or bot-initiated calls. Without a screening layer, these calls hit the client's main phone line directly, overwhelming staff and making it difficult to identify genuine leads.

Example: A Microsoft Ads display campaign generated ~150 calls for ~$300 ($2/call). The majority were spam, causing the client to pause the campaign entirely rather than optimize it.

The Solution: CallRail + IVR Forwarding

Architecture

The core pattern is a forwarding number with screening inserted between the ad and the client's real phone:

Ad / Website → CallRail Number → IVR Prompt → Client's Real Phone
                                      ↓
                               Bot/No-Input → Call Dropped

The client's real phone number is never exposed directly in ad campaigns. Instead, a CallRail tracking number is used. All calls hit CallRail first, where screening logic runs before forwarding.

IVR Prompt Design

A simple single-level IVR is sufficient to block most bots:

"Thank you for calling [Company]. Press 1 for sales, press 2 for support."

Bots cannot navigate DTMF prompts, so calls that receive no input are dropped automatically. This creates minimal friction for real callers — a single keypress — while being highly effective against automated dialers.

A slightly higher-friction variant asks callers to state their name and company before being connected. This screens out more marginal calls but adds more friction for legitimate prospects.

Tradeoffs

The simple "press 1" IVR is the default recommendation for clients experiencing bot call spam from ad campaigns.

Implementation Notes

• Tool: ^[3] handles both the tracking number and the IVR/forwarding configuration.
• Number placement: The CallRail number replaces the client's real number in ad campaigns and on the website pages those ads drive to. The real number remains on other channels (e.g., Google Business Profile, directories) unless call tracking there is also desired.
• ClickCease relationship: IVR screening and ^[4] are complementary. ClickCease blocks fraudulent ad clicks before they reach the site; IVR screens calls that do come through. For Microsoft Ads specifically, ClickCease protection should be configured first, as it reduces the volume of bot traffic reaching the phone number at all.
• Zoom Phone alternative: For internal/agency use, Zoom Phone includes built-in spam identification that flags suspected spam calls before answering — a lower-effort option when CallRail is not already in place.

When to Recommend This

Propose call screening when:

• A client launches a new ad campaign (especially display or broad-match) and reports a sudden spike in call volume with low lead quality.
• Microsoft Ads or other networks without existing ClickCease coverage are active.
• The client is considering pausing a campaign due to spam calls rather than optimizing it — screening may rescue the campaign's ROI.
• The client does not have a dedicated receptionist or answering service and is being overwhelmed by volume.

Related

• ^[5]
• ^[6]
• ^[7]
• ^[8]