A AtomicX Chat
Help Sign in

Updated November 20, 2026

CRM lead intake

Overview

An e-lead is a lead that arrives electronically: a lead from a lead provider or marketplace, a Facebook Lead Ads form, a website form, or an email in your lead inbox. The CRM turns each one into a contact and a lead marked E-lead, picks the Source from your match rules, and drops duplicates.

Steps

Give providers your lead address

  1. Go to CRM → Locations and click Edit on the location.
  2. Copy the Inbound lead URL for providers and forms that post leads (JSON, ADF/XML or plain text all work), or the Lead inbox address for providers that email leads. Forward your existing lead inbox to that address.
  3. For Facebook Lead Ads, connect the form through Zapier (or any automation tool) and post the lead fields as JSON to the Inbound lead URL.

A lead posted to the Inbound lead URL is saved before the provider gets its reply, then turned into a lead in the background, usually within 15 seconds. If the CRM can't save the lead, the provider gets an error (503) and can send it again. Sending the exact same lead twice imports it only once.

Leads from your website chat

When a visitor in your website chat leaves an email or phone number, the CRM creates an e-lead from it automatically, once per conversation. This works wherever the chat asks for contact details:

  • an Email Input or Phone Input node, or a Form Group with Email or Phone fields, in the chat's workflow,
  • a workflow the AI assistant offers during the chat (for example a quote request form), and
  • the contact form the AI assistant shows, for example for a demo.

If the visitor left an email or phone but no lead was created yet, the CRM creates it when the conversation completes.

The lead gets the source Website - Request Information, goes to your first active location, and has a note with everything the chat collected plus the visitor's last chat messages. Nothing needs to be set up beyond having a location.

Match leads to sources

  1. Go to CRM → Sources and click Edit on a source, for example one named after a lead provider.
  2. Under Match rules, enter one vendor name or sender domain per line, for example acmeleads and leads.acmeleads.com.
  3. Click Save. Leads whose vendor name or sender domain contain a rule get that source. A lead whose vendor name is exactly a source's name also gets that source; everything else goes to Unknown.

What happens to a lead

  • The contact is matched by phone first, then email, and created when new.
  • A new lead is created with the stage New, temperature Fresh, the item of interest from the e-lead, and the e-lead's comments as a note. When the e-lead says what the customer offers in exchange, that is added as a note too.
  • When Start the assistant automatically for e-leads is on and the lead has an email address, the AI sales assistant answers the lead's message by email right away (no greeting, no waiting for business hours). The message shows in Communications as the customer's first email. Website chat leads are not emailed, because the chat already answered them.
  • The lead is assigned by the lead assignment rules (fixed assignee of the source or location, then round robin), and the team member is told. See CRM lead assignment.
  • When Start the assistant automatically for e-leads is on in CRM settings, the AI sales assistant takes the lead in the default mode.

Duplicates

A lead is dropped as a duplicate when:

  • the provider sends the same lead id twice, or
  • the contact already has an active lead worked in the last 30 days. A note "Duplicate e-lead from …" is added to that lead instead.

A lead with no phone and no email is kept as failed with the reason "No contact details in lead".

Tips

  • Send a test lead with curl -X POST <Inbound lead URL> -H "Content-Type: application/json" -d '{"name":"Test Lead","phone":"4165550199","item":"Blue sofa"}' and watch it appear under Leads → Fresh a few seconds later.
  • Website forms can post the same JSON directly; the keys first_name, last_name (or name), phone, email, item, comments/message and source are recognised.
An unhandled error has occurred. Reload ×