About

We didn't set out to build a phone verification API.

We just got really, really tired of chasing numbers that were never going to pick up.

The pattern we kept running into

Between the businesses we've run, we've sat on the other side of this problem more times than we can count. Leads would come in. Inside sales would call. Customer experience would follow up. Sales would push the funnel forward.

And a chunk of those “leads” — every single time, across every business — were never reachable. Wrong number. Disconnected number. A number typed in wrong at the exact moment someone was deciding whether to buy from us.

Nobody flags this on day one. It shows up slowly: a callback that doesn't land, then another, then a pattern. Eventually the CRM has a workflow for it — exponential backoff, three attempts, mark as lost — because that's the only way to survive the volume. The junk gets a process. The process doesn't fix the junk.

What that junk actually costs you

Once you've watched this happen across enough businesses, you stop seeing it as an annoyance and start seeing it as a tax:

  • Junk in, junk out. Every downstream decision — forecasting, campaign ROI, sales capacity planning — inherits the noise sitting in your CRM.
  • A false sense that campaigns are working. A dashboard full of “leads generated” looks healthy right up until someone tries to call them.
  • Real money spent chasing unreachable people. Ad spend on the click. Agent time on the callback. WhatsApp/SMS credits on the follow-up. All spent on a number that was never going to answer.
  • Operational drag and decision paralysis. When nobody's sure how much of the funnel is even real, every planning conversation turns into a debate about the data instead of a decision about the business.

The fix that wasn't easy to find

We went looking for a better way to catch this — not another CRM workflow to manage the junk, but something that could tell us, before any of that money got spent, whether a number was even real.

That's when we found phone number verification based on live telecom network data — not a format check, not a regex, an actual read on whether the number exists and is active right now. It worked. It also wasn't easy to get to: fragmented providers, inconsistent signals, nothing built for a business that just wanted a straight answer without becoming a telecom integration project.

So we decided to build the thing we'd been looking for.

Why we built FILTER

We believe businesses should spend their money and their people's effort where it does two things: grows revenue, and plugs the leaks quietly draining it. Chasing a number that was never going to answer does neither. That's the whole premise FILTER is built on — filter the junk out before it costs you anything, so every rupee and every follow-up goes toward a customer who was actually there.