Add a lead by hand
Enter a single lead, or paste a small batch, straight into a pipeline from the dashboard.
Open your pipeline, click the Intake node, then add a lead manually. You get a form built from that pipeline's fields, with required ones marked. Fill it in, click Add lead, and it's ingested like any other lead.
Use it for leads that arrive off-channel: a phone call, an email, a spreadsheet row a supplier sent you late, or a lead you had to correct and want to re-send.
Bulk paste
The Bulk paste tab takes tab- or comma-separated rows pasted straight from a spreadsheet. The first row is the header — its names are matched to your fields. Preview shows what LeadMove parsed before anything is created. 100 rows maximum; for anything bigger use a CSV import.
What happens next
Exactly what happens to a lead posted to your webhook: validation against your fields, deduplication, spam filtering, scoring, then distribution to your buyers. Manual review, if it's on for the pipeline, holds the lead for approval just the same.
Two things to know:
- A duplicate is recorded, not sent. You'll see "Recorded as duplicate (not routed)" — the lead is kept for the trail, never delivered, never billed.
- "Distribute immediately after ingestion" is on by default. Uncheck it and the lead lands in Held for review with no countdown, whatever the pipeline's manual review setting: approve it, send it to a buyer of your choice, or reject it from the leads list, exactly like a held lead. See Manual review.
Assigning a lead to a buyer by hand
Lead page → Manual Lead Assignment. Pick a buyer, optionally a specific delivery method, and send. It creates a real delivery: billed, counted against the buyer's caps, and visible in its portal.
You can assign a lead that is pending, routed (a second buyer on the same lead), unrouted or failed. A lead still awaiting a decision — held for review, spam, invalid, rejected — is not assigned from this form: its review card is where you decide, and Send to a buyer instead… on that card approves it and delivers it to the buyer you pick in one step.
A routed lead that another buyer already has (a live delivery: queued, waiting for its hours, or delivered) asks you to confirm before a second buyer gets it, in an exclusive pipeline. In a shared pipeline every matching buyer gets the lead by design, so nothing is asked.
Three refusals you can override, all with Send anyway: the buyer is at its cap with no compensation credit, it already received this same person inside its duplicate window, or another buyer already has the lead. Overriding is deliberate and shows up in the buyer's usage.
Don't use manual entry to test
A manually added lead is a real lead: it counts against your monthly quota, and it will be delivered to a real buyer and billed. To try a payload or check which buyer would win it, use the test console on the pipeline — it previews routing and can email you a sample delivery without ever contacting a buyer.
Common questions
Can I add a lead to a paused pipeline? No. Only active pipelines accept leads, whatever the method. Reactivate the pipeline first.
A required field is empty and I don't have the value. Can I still save it? Not from the form — required fields are enforced before submission. Either fill in a placeholder you'll correct later, or make the field optional in the pipeline's Intake settings.
Where does the lead show up? In the pipeline's lead list, immediately, with the same statuses as every other lead. See lead statuses.