Email notifications

Which emails LeadMove sends you, how to turn each one off, and where the alerts that never email you show up.

Settings → Notifications controls the emails LeadMove sends you: one master switch, three notification types, and a button to test what an alert looks like. Preferences are per user — each teammate sets their own.

Setting	What it sends	Default
Enable email notifications	Master switch. Off silences every notification below.	On
Delivery Failed Alerts	An email as soon as a lead fails to reach a buyer after its retries.	On
Pipeline Went Quiet	An email when a pipeline that normally receives leads has had none for 24 hours.	On
Weekly Summary	A Monday recap of the week that just ended.	On

Changes only apply once you hit Save Preferences.

Send Test Email delivers a sample "delivery failed" alert to your own address — the fastest way to check it isn't landing in spam before a real failure happens.

Delivery Failed Alerts

When a delivery to a buyer fails, LeadMove retries it. Once every retry is exhausted the lead stops moving, and this alert goes out — one email per failure, not one per attempt. It names the buyer, the lead, the delivery method and the exact error the buyer's endpoint returned, with links to open the lead (retry it, or route it elsewhere) and to check the buyer's delivery settings.

If the error mentions authentication or a bad URL, every lead routed to that buyer will fail the same way until the settings are fixed.

Pipeline Went Quiet

The only alert about something not happening — and the one nothing else can tell you. A source that breaks at your client's end produces no leads and no errors: without this email you find out hours or days later, by opening the dashboard.

It fires on a simple rule, checked every hour:

the pipeline is active, and
it received at least 3 real leads a day on average over the last 7 days, and
nothing has arrived for 24 hours.

The volume condition is what keeps it credible: a pipeline that receives a couple of leads a week has quiet days for perfectly normal reasons, and would cry wolf every Tuesday.

The email gives the pipeline, when its last lead arrived, its usual daily pace, and what to check — the break is almost always upstream, in the source that posts to you. You get one email per quiet spell, not one an hour. If leads come back and stop again later, that is a new spell and you are told again.

Leads from Test distribution never count as activity here, and the onboarding example pipeline is never watched.

Weekly Summary

Sent every Monday at 13:00 UTC (9am ET) and covering the previous complete week, Monday to Sunday:

Leads received, with the change versus the week before. Spam-filtered leads and leads from the example pipeline are not counted.
Routed — how many found a buyer — and delivered — how many actually reached one.
Buyer revenue for the week, with the change versus the week before, and your top buyer (revenue and lead count). Revenue follows the same billable definition as the dashboard: delivered leads, minus compensation deliveries and accepted disputes.
Disputes opened during the week, when there are any.

Two cases get no email at all: a week with no leads and no deliveries (nothing to recap), and an account that has never captured a real lead or whose subscription is canceled. Trials do receive it.

Who receives what

Delivery-failure alerts go to the owners and admins of the account who have both the master switch and Delivery Failed Alerts on.
Pipeline-quiet alerts follow the same rule, with the Pipeline Went Quiet toggle. If nobody in the account has it on, nothing is sent — and nothing is marked as reported either, so the day someone turns it back on the silence is still news.
The weekly summary goes to every owner and admin with both the master switch and Weekly Summary on — each teammate independently, so one can keep it while another opts out.
A buyer opening a dispute emails owners and admins who have the master switch on. See how disputes work.
Quota warnings (at 80% of your monthly lead limit) and low prepaid balance warnings go to the account owner regardless of these toggles, because both decide whether leads keep flowing. Quotas: plans & quotas.

Alerts that live in the app, not your inbox

The bell in the top bar collects health signals that don't email anyone. It refreshes on its own, and alerts can be marked read one by one or all at once:

Alert	Raised when
High failure rate	A buyer's deliveries are failing at an abnormal rate over the last hour.
Buyer inactive	A buyer received no leads in 24 hours despite active routing rules.
Dead Letter Queue threshold	Too many deliveries have failed all retries and are sitting unresolved.
Cap near	A buyer passed 80% of its daily, weekly or monthly cap.
Unrouted accumulation	Leads are stacking up unrouted, or deliveries have been pending over an hour.
Dispute spike	A buyer's dispute rate over the last 7 days is unusually high.
Sender domain failure	A verified sender domain stopped verifying — deliveries fall back to leadmove.io until it's fixed.
Balance low	A prepaid buyer is running out of funds, or has been paused for it. This one also emails the owner.

Common questions

I turned the master switch off and still got an email. The switch covers notifications. Account-critical warnings — monthly quota at 80%, a prepaid buyer out of funds — still reach the owner, as do billing emails from the payment provider.

The test email never arrived. It goes to the address you sign in with. Check spam, then confirm the address on your profile.

Can two teammates get different alerts? Yes. Each user has their own preferences, and only owners and admins are in the audience for delivery failures and disputes in the first place.

Do these settings affect what buyers receive? No. Buyer-facing emails are the lead deliveries themselves, configured per buyer — see delivery methods.