Integrations & CRM

Yes. Our lead-post webhook is the primary integration method: when a new lead is generated for your account, we make an HTTP POST to your specified endpoint within 1–3 seconds of form submission. The payload is either form-encoded or JSON (your choice at setup), contains all standard and vertical-specific fields, and is signed with an HMAC-SHA256 header so your endpoint can verify authenticity. We retry failed posts up to 5 times with exponential backoff (30s, 2m, 10m, 1h, 6h). For pulling data in the other direction — return submissions, wallet balance, delivery stats — we expose a read-only REST API with a per-account bearer token. Full developer documentation, payload schemas, and sample code in Node, Python, and PHP are at /developers on our site.

Yes. We support Zapier (native app, listed in the Zapier marketplace), Make (formerly Integromat), n8n, Pabbly Connect, and any other iPaaS tool that can receive a webhook. For Zapier users, our trigger is "New Lead" and it fires on every delivered lead with all standard fields mapped. A common stack: InsureLeads → Zapier → Google Sheets (backup) + Slack (team notification) + your dialer (instant call). This setup takes 10 minutes and is free on Zapier's starter plan if you stay under 750 tasks/month. For high-volume buyers we recommend direct webhook to your CRM instead of routing through Zapier because direct webhooks add zero latency whereas Zapier polling can add 1–5 minutes, and in lead response those minutes matter.

We push leads directly into most predictive, progressive, and preview dialers: Convoso, Readymode (formerly XenCall), Five9, Vici dial, T-Max, PhoneBurner, CallTools, Kixie, Orum, JustCall, Aircall, and Ringba (for ping-post and inbound). For live transfers, we terminate calls into any SIP endpoint, Twilio phone number, or plain 10-digit DID — no special carrier setup required. For buyers using a CRM with a built-in dialer (HubSpot Sales Hub, GoHighLevel, Close, Salesforce Sales Engagement), the lead arrives in the CRM and your dialer picks it up from there; no separate integration needed. If your dialer is not on our list, send us a field-mapping document and we can usually stand up the integration in 1–2 business days at no charge.

Yes, in two ways. (1) Direct email/SMS delivery of the lead to you: a formatted notification is sent to the email or phone number on your account within seconds of capture — useful if you want a human to triage before it hits the CRM. (2) Automated outreach to the consumer: we do not send outreach on your behalf (you must contact the consumer under your own agent identity for TCPA and CMS reasons), but we push the lead into your automation platform of choice — Twilio, SendGrid, Mailgun, ActiveCampaign, Klaviyo, GoHighLevel, or HubSpot Sequences — so your pre-built nurture sequence fires immediately. Best practice: a 5-minute SMS, a 60-minute email, and a phone call attempt within 5 minutes. That three-channel approach lifts contact rate from ~30% (phone only) to 55–65%.

Yes. During integration setup we give you a configurable field-mapping template: every standard field (first_name, phone, email, etc.) can be renamed, reordered, or split into separate fields to match your CRM's schema. You can also request custom tags on each lead — for example, utm_source=insureleads, lead_type=real_time_exclusive, vertical=medicare — which is helpful for attribution reporting in your CRM. For agencies running multiple producers under one master account, we can route-by-rule: leads in TX go to one webhook, leads in FL go to another, Medicare goes to a third. All customization is free. Changes to mapping take effect within 15 minutes. Documentation and a sandbox endpoint (so you can test the exact payload you will receive) are in the developer portal at /developers.

We retry up to 5 times with exponential backoff: 30 seconds, 2 minutes, 10 minutes, 1 hour, and 6 hours. Each retry attempts the same endpoint; if your CRM comes back online within 6 hours the lead lands normally and you receive an in-dashboard notification that the delivery required retries. If all 5 retries fail, the lead is queued in the dashboard for manual download as a CSV and we send an operational email to your account contacts. Lost leads are rare — our 30-day success rate on first-attempt webhook delivery is 99.4% — but the safety net matters. As a redundancy, we recommend configuring a secondary delivery channel (email or a secondary webhook) during onboarding so you have belt-and-suspenders coverage without any extra work.