Warm Transfer (Pre-Call Data)

A warm transfer (also called a live transfer) is when your source pre-qualifies a caller and then bridges the live call to your tracking number, instead of the caller dialing in cold. This guide shows how to send that caller's details a moment before the transfer, so Lead Distro AI can attach them to the call. For the basics of a call campaign first, see Call Tracking Setup.

When to use it

• Your buyer pays per qualified or passed call, not per lead, so each call needs to be tied to who the caller was.
• You want the caller's details (name, state, case type, TrustedForm, your own lead id) on the call record for reporting, reconciliation, and dispute review.
• Your source runs a warm or live transfer through a dialer that can send a quick web request before it bridges the call.

How it works

• Your source sends the caller's details to the call enrichment endpoint (a quick GET or POST) right before the transfer.
• Your source bridges the live call to your campaign's tracking number.
• Lead Distro AI matches the two by the caller's phone number and shows the details on the call record.

Step 1: Turn on Pre-call Data and choose your fields

Open your call campaign, go to Settings, and turn on Pre-call Data. A Fields tab appears where you choose which parameters to accept: add whatever your vertical needs (first name, state, case type, ZIP, your own lead id, anything). There is no fixed list. We always keep the caller's name, phone, and email; the Fields tab is for the extra fields you want stored and shown on the call.

Step 2: Send the caller details

Send the fields to the enrichment endpoint using the same API key your source already uses. You can send them as a POST with a JSON body, or as a GET with query values, whichever your dialer supports. The callerid is the consumer's phone in E.164 format (like +13105551234) and is required, since it's the key we match on.

curl -X POST https://app.leaddistro.ai/api/v1/calls/enrich \
  -H "x-api-key: YOUR_SUPPLIER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "flo_campaign_id": "YOUR_CAMPAIGN_ID",
    "flo_supplier_id": "YOUR_SUPPLIER_ID",
    "callerid": "+13105551234",
    "first_name": "Maria",
    "state": "TX",
    "case_type": "MVA",
    "trustedform_url": "https://cert.trustedform.com/...",
    "lead_id": "YOUR-LEAD-ID"
  }'

Prefer a simple GET? Send the same values as query parameters (send the x-api-key as a header, and URL-encode the + in callerid as %2B):

https://app.leaddistro.ai/api/v1/calls/enrich?flo_campaign_id=YOUR_CAMPAIGN_ID&flo_supplier_id=YOUR_SUPPLIER_ID&callerid=%2B13105551234&first_name=Maria&state=TX&case_type=MVA&lead_id=YOUR-LEAD-ID

On success you get back a confirmation of exactly what we stored and will match on:

{
  "success": true,
  "mode": "call_enrichment",
  "stored": true,
  "caller_phone": "+13105551234",
  "fields_stored": ["first_name", "state", "case_type", "trustedform_url"],
  "external_lead_id": "YOUR-LEAD-ID",
  "expires_at": "...",
  "match_window_hours": 48
}

Step 3: Bridge the live call

Send the live call to your campaign's tracking number, passing the consumer's phone number as the caller ID. When the call lands, we match it to the details you sent and attach them.

Step 4: Set the destination to bill on connect

Because your buyer pays for a passed transfer rather than talk time, set the destination to bill when the call connects. Open the destination in Edit Target, set billing to bill on connect with a 1 second minimum, and save. If a transfer doesn't qualify, refund that call from the call's page and it shows as Returned. See Wallet & Top-Ups.

Step 5: Send the details on to your destination (optional)

The details are on your call record either way. If your destination wants them too — in their CRM, or in an inbox while the call is still live — you have two options, and you can use both.

• Data Delivery (per destination). Open the destination in Edit Target, turn on Data Delivery, and fill in the endpoint URL, method, any custom headers, and the body template. The moment that destination answers, we post the caller's phone and location plus every pre-call field to their endpoint. It fires only to the destination that actually took the call. Send Test fires a sample so you can validate their endpoint before a real call rings.
• A Call Connected automation (campaign-wide). On the campaign's Overview tab, go to Triggers & Automations, add an automation with the Call Connected trigger, and choose the Email, Webhook, Slack, or Google Sheet action. The Fields picker includes a Pre-Call Data group, so you can drop the caller's fields straight into an email to your client.

Where the data shows up

Open the call from the Calls page. The Pre-call data card shows your lead id and every field you sent, tied to that exact call, ready for reporting, reconciliation, or a dispute.

Limits to know

• Matching needs the consumer's caller ID. If the transfer shows the dialer's own number instead, we can't match on the phone. Ask support about a dedicated number per lead.
• You have 48 hours from sending the details to bridge the call, then the saved details expire.
• The destination only gets the fields if you send them. The details always land on your call record. To pass them into the destination's own system, turn on Data Delivery or a Call Connected automation (see the step below).

FAQ