How to automate WhatsApp validation for leads entering your CRM

Most teams clean their contact list on a schedule: monthly, quarterly, before a big campaign. That catches the numbers already sitting in the CRM. It does nothing for the leads that came in yesterday, or the ones coming in an hour from now. A periodic cleanup is always chasing a list that's still growing between cleanups.

The fix isn't a faster cleanup cycle. It's validating at the point a lead enters the system, so nothing invalid gets in to begin with.

Why periodic cleanup always falls behind

A quarterly re-check assumes the list is static between checks. It isn't. New leads flow in daily from forms, imports, integrations, and manual entry, and each one carries the same risk as the numbers already in the CRM: never registered on WhatsApp, mistyped, or attached to a country code nobody validated.

The scale of the underlying decay makes this worse than it looks. B2B contact data decays 22.5% to 70.3% a year depending on data type and measurement method, and roughly 42.9% of phone numbers become invalid within 12 months, according to Landbase's review of contact-accuracy research. A list validated in January is already stale by the numbers alone, before you even count the leads added since. See how many WhatsApp numbers are fake for how that decay compounds specifically for WhatsApp reachability, on top of general contact aging.

There's also a speed cost that has nothing to do with data quality. Response time is one of the strongest predictors of whether a lead converts at all: conversion rates run 8 times higher when first contact happens within 5 minutes versus 6 minutes or longer, and companies responding within an hour still report losing leads to faster competitors 81.2% of the time, per the Blazeo 2026 Speed-to-Lead Benchmark Report. If a lead sits in a queue for a quarterly bulk validation before anyone reaches out, the number being valid won't matter, the lead will already be gone.

Point-of-entry validation

The alternative is checking each lead's number the moment it's created, not on a schedule. In practice this means a webhook: your CRM fires an event when a lead is created (or a phone field is updated), that event calls the validation API, and the result gets written back before the lead reaches an outreach sequence.

This isn't a replacement for bulk cleanup, it's what keeps a cleaned list from rotting again. See CSV upload vs API for the full breakdown of when each method fits: bulk validation clears out what's already in the CRM, point-of-entry validation stops the same problem from coming back one lead at a time.

Batch vs. real-time: the actual trade-off

These aren't competing approaches, they solve different problems:

A CRM with a genuinely dirty backlog needs the batch pass first: there's no point validating new leads carefully into a list that's already half dead weight. Once that backlog is cleared, the webhook is what keeps it clean, since every lead afterward is a fresh chance for the same problem to reappear. wavalid's use case for list cleaning covers the batch side in more depth; this post is about the ongoing part.

What to do with an invalid lead

Validating a lead only helps if something happens with the result. Three patterns, in order of how much friction they add to your pipeline:

• Block. The lead never enters the active outreach segment. Useful when WhatsApp is your only outreach channel and an unreachable number has no other value yet.
• Flag. The lead stays in the CRM with a status field (e.g. whatsapp_status: invalid) so reps and automations can see it, but it's excluded from any WhatsApp-based sequence by default.
• Route to a review queue. Instead of blocking or silently flagging, the lead goes to a queue someone checks manually, useful for high-value leads where a wrong number might just mean a typo worth fixing rather than a dead end.

Flagging is usually the safest default: it keeps the data (a number invalid today might belong to a real contact who mistyped a digit or switched numbers since) while stopping it from wasting a send. Deleting outright throws away information you might need to fix the lead later. See how to clean a contact list before a campaign for the same segment-don't-delete logic applied to a full list rather than one lead at a time.

A practical integration outline

The mechanics are the same regardless of which CRM you're on:

1. Trigger. The CRM fires a webhook on lead creation (HubSpot Workflows, Salesforce Flow with an outbound message, Pipedrive webhooks) carrying the lead's phone number and ID.
2. Validate. Your endpoint receives the webhook and calls the validation API with the number:

curl https://wavalid.rizon.agency/api/v1/validate \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"phoneNumber": "+14155551234"}'

3. Write back. The response (valid or invalid) gets written to a custom field on the lead record, along with a timestamp.
4. Route. A CRM workflow rule reads that field: valid leads continue into the WhatsApp sequence, invalid ones get flagged or moved to a review list.

If your CRM's own automation tooling can call a webhook directly, an MCP server is a natural fit for teams building this as part of a larger AI-driven workflow, since the same validation call can be triggered by an agent step rather than custom integration code. For a straightforward webhook-to-field setup, the REST API is the simpler entry point, and it's the same underlying check either way: sub-100ms, across 195+ countries, and every validated number is stored on your account so you're never re-checking a lead you already have an answer for.

The close

Cleaning a CRM in bulk fixes the past. It doesn't stop tomorrow's leads from bringing the same problem back in. Wiring wavalid's API or MCP server into your lead-created webhook validates every number at the one moment it actually matters, before a rep or a sequence ever tries to reach it, so the list stays clean instead of needing to be re-cleaned every quarter.