Getting leads in

Three ways to load leads, and one rule that applies to all of them: no consent evidence, no dialing.

HTTP posting (webforms and lead vendors)

Create an API key under Settings → API keys and give your form or vendor the posting URL. Only the phone number is strictly required, but send everything you have — name and state make the AI conversation better, and state keeps calls inside legal calling hours. Full field reference in the developer quickstart.

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 within the last 30 days are skipped automatically.

Facebook Lead Ads

Direct Facebook Lead Ads sync is coming — it isn't connectable yet. Until then, route Facebook leads through Zapier/your CRM to the HTTP posting URL above.

Consent — the rule that matters

Regulators treat AI voice as an artificial/prerecorded voice, which requires prior express written consent for marketing calls. Every lead must carry its consent evidence (when they agreed, and the version of the language they saw). A lead that arrives without it is stored and visible, but marked ineligible and never enters the dial queue. This is deliberate and cannot be switched off.

What happens after a lead lands

It's scrubbed against your suppression list and (if connected) your DNC provider, then queued for its campaign. Statuses you'll see: new → queued → dialing → qualified / transferred, or ineligible with the reason shown.