← Help center

Getting leads in

Two ways to load leads — a live feed from your sources, or a CSV — and one rule that applies to both: no consent evidence, no dialing.

Connect a live lead source

Go to Settings → Integrations & API and scroll to Connect a lead source. You get your account's intake address plus copy-paste recipes for three situations:

Each recipe needs an API key. Create one in the API keys section just above (Admin only), tick Send & change data, and paste the key where the recipe shows YOUR_API_KEY. You only see the key once, so copy it then.

Which campaign calls the lead? If the incoming lead names a campaign, that campaign gets it. If not, we use the campaign you attached to the API key. If neither is set, the lead is saved but never called — a common first-day surprise.

Only the phone number is strictly required, but send everything you have: name and state make the conversation better, and state is what keeps calls inside legal calling hours. The exact field list, response shapes, and error codes are in the developer quickstart.

The requirements sheet for a lead source

Under the recipes there's a Lead source requirements sheet: fill in your company's legal name and contact email and it produces a printable one-pager you hand a vendor before they send you anything. It spells out the consent language their form must show — naming your company, because the calls go out on your accounts — and the exact fields to send.

CSV import

Import in the sidebar walks you through a column-mapping wizard and gives you a row-by-row report of what was created, skipped, or rejected. Duplicates of a number you already have from the last 30 days are skipped automatically.

Facebook Lead Ads

Direct Facebook Lead Ads sync is not connectable yet. Until it is, route Facebook leads through Zapier or your CRM into the intake address above.

Consent — the rule that matters

Regulators treat an AI voice as an artificial or prerecorded voice, which requires prior express written consent for marketing calls. Every lead must arrive with its consent evidence: when the person agreed, and which version of the language they saw. A lead without it is stored and visible, but marked ineligible and never enters the dial queue. This is deliberate and cannot be switched off. Open any lead and you'll see a green "Consent on file" box listing the proof, or a red one explaining that it will never be dialed. More on the rules in Compliance.

What happens after a lead lands

It's normalized (phone number formatted, state turned into a time zone), checked against your do-not-call list and, if you've connected a scrubbing provider, scrubbed there too — then queued for its campaign.

Statuses you'll see on the Leads page: new → queued → dialing → contacted (a person answered) → qualified → transferred. Others: ineligible (with the reason shown — usually missing consent or a DNC hit), suppressed (they opted out), and dead (out of attempts).

One person's data, on request

Open a lead and, at the bottom of the drawer, an Admin can export everything held about that person as a file, or delete it permanently — the lead record, call history and transcripts, transfers, callbacks, and texts. That's how you answer a consumer's data request. Deletion can't be undone.

Can't find what you need? Use the contact form and we'll help directly.