Skip to main content
API Integration·Baton Leads

Caller-ID Name Lookup System

A Make webhook that takes a phone number, runs a Twilio Name Lookup, and returns the lead's first and last name in under a second. Reusable from any tool that can hit a URL.

Caller-ID Name Lookup System

Sub-second response

One webhook call returns firstName + lastName

Reusable across CRMs and dialers

The Problem

Teams running inbound calls capture phone numbers but rarely capture names on the first ring. Pulling caller names manually slows the team down. Paying per-tool for name lookup adds cost everywhere it's needed and produces inconsistent results across tools.

The Build

I built a Make scenario that exposes a webhook endpoint. Any tool sends a phone number to the URL. The scenario parses the number, calls the Twilio Name Lookup API for the registered name on file, splits the returned name into firstName and lastName, and responds with clean JSON in under a second. Baton Leads wired it into its Zapier flows so every inbound call gets enriched the moment the contact lands in the CRM.

Screens

Before and after for Baton Leads' caller ID lookup: names looked up manually, now returned by a Make and Twilio webhook in under a second.

The Outcome

Baton Leads stopped paying per-tool for name lookups and stopped formatting the result differently in every place it ran. One webhook call enriches every new contact with first and last name in real time. The same endpoint is reusable from any tool that can hit a URL.

Stack

MakeZapierTwilio