Adding buyers
Create a buyer with a name, finish its setup section by section on its page, then set it live.
Buyers → New buyer. Type a name and create: the buyer exists straight away. Everything else — contact, price, caps, delivery — is filled in afterwards on the buyer's own page, one section at a time, each saved as you go. Stop halfway or close the tab and nothing is lost.
A buyer is a company you sell leads to. You create it once for your whole account, then add it to as many pipelines as you want — quotas, hours, price and duplicate window follow the buyer everywhere.
| Field | What it's for |
|---|---|
| Start from | Blank buyer, or an existing buyer to copy — see Creating from an existing buyer. |
| Buyer name | How the buyer appears everywhere in the app. The only required field. |
| Contact email | Optional. Who to reach at this buyer. Not the delivery address — that comes with the delivery method. |
Finishing the setup
A new buyer starts paused, and its page opens on a setup checklist. Each line opens the panel that saves it, and ticks itself once done.
| Step | Where | Required to go live |
|---|---|---|
| Contact details | Settings → Contact person | No |
| Pricing | Settings → Pricing & billing — see Lead pricing | No |
| Caps & schedule | Settings → Caps & windows — see Quotas and caps | No. Unlimited and 24-7 unless you set them |
| Delivery method | Settings → Delivery methods — see Delivery methods | Yes |
| Go live | The checklist itself | — |
Migrating a buyer that has already received leads this month elsewhere? Declare them in the same panel — see moving a buyer in mid-cycle — instead of lowering its cap by hand.
Go live sets the buyer to active. It stays disabled until at least one delivery method is turned on: an active buyer with nowhere to send is still picked by distribution, and every lead it takes goes nowhere.
Know what you're doing? Dismiss setup guide hides the checklist without activating the buyer. Until a buyer goes live or the guide is dismissed, the buyers list flags it with a Setup incomplete badge, so an abandoned setup is easy to find again.
Finding a buyer in the list
The Buyers page shows how many buyers you have next to the title, and a toolbar to narrow the list: search by name or email, filter by status or by tag, and sort by newest, name, leads received, or price per lead. Search and filters live in the URL, so a filtered view can be bookmarked or shared.
Two views
The toggle at the end of the toolbar switches how the list is drawn.
| View | For |
|---|---|
| Cards | Reading performance — leads, revenue, credits and cap bars, one wide card per buyer. |
| Table | Administering — twenty buyers on a screen, with price, caps, leads, revenue and prepaid balance in columns. |
In the table, click a column header to sort by it (buyer, price per lead, leads); clicking the active one goes back to newest first. The sort control in the toolbar and the column headers are the same setting, so they always agree. Revenue isn't sortable.
Your choice is remembered for next time. Once you've used the toggle it also sits in the address bar, so a link copied from there opens on the view you were looking at, whatever the recipient's own habit is. On a phone the list is always cards — an eight-column table isn't usable at that width.
Tags
A tag is a word you put on a buyer to say what kind of buyer it is — a niche, a tier, a region. Two pools of buyers for two kinds of leads is one tag each, and the list filters down to either.
Set them in Settings → Profile. Type to reuse a tag you already use somewhere else, or type a new word and create it. Tagged buyers show their tags under their name in the list, always the same colour for the same word.
Tags are shared across the whole account — buyers and pipelines draw on the same vocabulary, so a word typed on one is offered on the other and segments both lists at once. They are free text, up to 20 per buyer. There is nothing to manage: a tag exists as long as something wears it, and disappears from the filter when the last one drops it.
Public details
A buyer has two identities: the name you file it under, and the name a lead should read. Settings → Profile → Public details holds the second one — display name, website and booking link.
They're optional. Lead auto-reply uses them today, where a message can name the buyer that just received the lead. Leave the display name empty and messages use the internal name instead, which is fine when the two are the same and wrong when your internal label is "TRC Business Leads".
Set them once per buyer: every pipeline that names that buyer picks them up.
What the buyer says is elsewhere: its intro line — a sentence in its own words — and its own whole message both live in Settings → Lead auto-reply, the card that also decides whether its deliveries message the lead at all. See per-buyer messages.
Where the configuration lives
A buyer's page has two tabs. Overview is what it is doing — leads, revenue, the pipelines feeding it, recent deliveries. Settings is everything you can change, grouped by how often you need it: delivery methods first (with the sender domain they send from), then pricing and billing, caps and windows, operating hours and disputes, then the profile, contact, lead auto-reply, portal access and compensation credits.
Each Settings card shows the current values and an Edit button that opens a panel beside the page. A panel saves its own section and nothing else, so two people editing different sections never overwrite each other. Nothing is saved until you press Save; leaving a panel with changes asks first.
Delivery methods are the exception to the one-panel-per-section rule: the Settings tab lists them in full, and each one opens its own page — a webhook body template, a field mapping and a delivery schema need the room. Adding one starts in a panel (type and name) and lands on that page.
The address bar follows along — ?tab=settings&panel=pricing — so a section can be bookmarked or shared directly.
Buyers created from a pipeline canvas
Add a buyer on a canvas creates the buyer, its email delivery method and the rule in one pass, and sets the buyer live right away — it has somewhere to deliver by construction, so there's no setup left to do. Only if the delivery method can't be created does the buyer stay paused, with its checklist to finish the job.
Creating from an existing buyer
Set Start from to an existing buyer, or use Duplicate on any buyer's page. Type the new client's name (and contact email if you have it) and you get a second buyer set up like the first, without retyping anything.
What is copied: price per lead and conditional prices, currency, billing mode, caps and their cycles, operating hours and timezone, duplicate window, dispute window and allowance, tags, priority and notes — plus every delivery method, with its field mapping, template and transforms.
What is not: contact details, portal access, and wallet balance (it starts at 0). Routing rules aren't copied either — a rule belongs to one pipeline, so add the new buyer where you want it, or use Duplicate to another buyer on an existing rule (Routing rules).
The copy never inherits how many leads the original already received in the current windows — that's the original's history. If the new client arrives mid-cycle with figures of its own, set them on the copy under Caps & windows (carried-over leads).
On the copy's checklist, everything that came from the source is marked inherited rather than done — a reminder to check it against this client's deal instead of trusting it.
Check the destinations before going live
Delivery methods are copied as-is, destination included — the copy's webhook URL, recipient emails or spreadsheet still point at the buyer you copied from. That's why the copy starts paused and every copied method starts inactive. Open each one, set the right destination, turn it on, then go live.
The buyer's duplicate window
During distribution, a buyer is skipped when it already received a lead with the same email or phone inside its window, even if the lead is brand new to your pipeline. 0 disables the check.
This is separate from the pipeline's own deduplication: one protects your inventory, this one protects the buyer's.
Disputes
The Settings → Disputes card carries two settings.
Dispute window — how long this buyer has to contest a delivered lead. By default it gets your account's window; turn off Use account default to give it its own deadline, in hours, when it negotiated different terms.
Dispute allowance — how often it may dispute at all, as a percentage of the leads it received over the last 30 days. Off by default (unlimited). Set it on a buyer that disputes reflexively; the card then shows how many attempts were blocked. Full flow: How disputes work.
Status
The control next to the buyer's name shows whether it's in play, and changes it.
| Status | What it means |
|---|---|
| Active | Normal. The only status distribution considers. |
| Paused | Temporarily out. No pipeline can route to it. |
| Disabled | Out for good — what a deleted buyer becomes. Its leads and history are kept. |
| Archived | Out, kept for the record. |
It reads Active once the buyer is live, and Go live while it is out — the same menu either way. Active stays out of reach until at least one delivery method is turned on. While the setup checklist is still up, its own Go live does the job.
To stop one pipeline, not the buyer
Use Pause in this pipeline on the pipeline canvas. It keeps the buyer live everywhere else, and keeps its conditions, price and mapping intact — see Routing rules.
Temporarily closing a buyer
A buyer that's away for a holiday, a long weekend or a week off doesn't need a status change. Open the same status control and pick Temporarily close…, then a preset — For 1 hour, Rest of today, Until next Monday — or an exact date and time. The buyer stops receiving leads until then and starts again on its own: nothing to remember, nothing to undo.
The dialog then asks what to do with leads that arrive meanwhile, because the answer depends on how long you're closing — it is not inherited from the buyer's operating hours setting, which answers for a night:
| Choice | What happens |
|---|---|
| Send them to other buyers (default) | Nothing piles up. The buyer comes back to fresh leads only. |
| Hold them for this buyer | Everything queues and is delivered in one batch at reopening. |
Hold with care over a long closure: held leads count against the buyer's caps and are billed to a prepaid balance as soon as they're assigned, and a week's worth lands days old. Skip is the right answer for a holiday; hold is for a few hours.
The status control then reads Closed until Aug 25, 9:00 AM, in the buyer's own timezone, and the buyer wears a Closed until badge in the list and on the pipeline canvas. To bring it back early, pick Reopen now — any held leads go out straight away.
Dates are read on the buyer's clock, and reopening respects their operating hours: a closure ending at midnight delivers at the next open window, not at 3 AM.
Buyers can do this themselves
If you leave Self-serve pause on (Settings → Buyer portal, on by default), your buyers can pause their own deliveries from their dashboard for up to 30 days, and resume early — see pausing your deliveries for what they see. They choose the same skip-or-hold question you do.
You keep the last word:
- you're emailed when a buyer pauses or resumes, with the end date and what's happening to their leads meanwhile;
- their pause shows everywhere yours does, marked · set by buyer — the status control, the buyers list, the pipeline canvas — and it's in the activity log;
- you can change or lift it like any closure. Doing so makes the closure yours, and the buyer can no longer lift it.
The reverse doesn't hold: a closure you set is read-only in their portal. They see that deliveries are paused and until when, and are told to contact you — a buyer you cut off can't reopen itself.
From your own systems
You can pause and resume a buyer without opening LeadMove — from your billing tool the moment a charge fails, for instance. Create a key in Settings → Developers, then call POST /api/v1/buyers/{id}/pause; see the buyers API.
A pause posted that way is the same pause as the button here, and says so everywhere: the status control reads Paused · via API, its menu names the key and the reason you sent, the buyers list carries the same · via API suffix, and the activity log records the key as the actor.
One rule worth knowing before you wire it up: resume only lifts what the API itself paused. A buyer you paused by hand stays paused when your billing system calls resume — it answers changed: false and tells you who paused it. Your side of the account and ours never fight over the same switch.
The Automate section at the bottom of the status control copies the exact request for this buyer, ready to paste your key into.
Common questions
Do I need one buyer per pipeline? No. Create it once and add it to each pipeline. Tier, weight, conditions and price overrides are set per pipeline; quotas, hours and duplicate window are set once on the buyer.
Why can't the buyer resume this from the portal? Because you set it, not them — whether you clicked it here or your own system called the API. The portal only lets a buyer lift a pause the buyer set. Anything that came from your side reads as Paused by your lead provider and is read-only for them.
Closed or paused — which one do I want? Closed, whenever the buyer comes back on a known date: it reopens by itself, and you can say when. Paused when you don't know — it stays out until you set it back to active. Both stop deliveries; only one has an end.
Do paused or archived buyers count toward my plan's buyer limit? Yes. Every buyer you've created counts, whatever its status — see Plans and quotas.
Where do I set what the buyer actually receives? On the buyer's delivery methods: the channel, the destination and the field mapping. See Delivery methods.
Does changing the duplicate window affect leads already sent? No. The window is applied at distribution time, so a change only affects the next leads.