22 ways a lead hand-off quietly breaks, and how to check each
A lead hand-off breaks quietly when records stop arriving, arrive wrong or sit with no owner while every tool still looks healthy. This catalogue lists 22 such breaks in the order a lead travels (capture, match, owner, follow-up, replies, reporting), with the usual cause, a way to check each one and who usually fixes it.
Each entry cites a public source where we found one. Entries with no source are marked as our reading. The checks are generic: read them against your own tools.
Capture: Form, webinar or ad to the CRM
A field or list value was changed, so a step now writes into nothing
Someone renames, retypes or recreates a field, or renames a list value, in one tool. The connection between your marketing tool and the CRM keeps pointing at the old definition, so new answers land in a dead field or are dropped, while records still look like they arrive. Which changes break what differs by tool: a label-only rename often breaks nothing, while a type change, a deleted-and-recreated field or a renamed list value is the usual culprit (our reading).
Why it happens. A connection records a field's name and type once, at first sync, and does not always follow later changes.
Usually fixed by: Marketing operations (the mapping) with the CRM admin (change control).
Sources: Vendor documentation
The CRM refuses a lead because of one answer
A form answer does not fit a CRM rule: a required field is empty, a list value is not allowed, a validation rule fires. The record can be refused, so the person never appears in the CRM although the form said thank you.
Why it happens. The form was edited, or an admin tightened a rule, and nobody re-tested the path between them.
Usually fixed by: CRM admin (the rules) with marketing operations (the form options).
Sources: Integration vendor guide · Vendor staff reply in a forum
The connection hits a daily cap and the rest of the leads are delayed or refused
A busy day (a webinar, an ad burst, an import) uses up a daily limit on form posts or on calls between tools. What comes after the limit can be delayed or refused, and the gap shows up as a hole in the CRM.
Why it happens. Daily limits are built into the tools, and the connection does not warn anyone before it hits them.
Usually fixed by: Marketing operations with the CRM admin (limits and batching).
Sources: Vendor documentation · Vendor documentation
Lead volume falls quietly and nobody is alerted
New leads fall sharply. A broken form, a removed tracking script, a consent change or a browser change cuts the count, and the weekly report just shows a slow week.
Why it happens. Counts are looked at when they are reported, not compared with traffic and spend as they happen.
Usually fixed by: Web or marketing operations, with whoever changed the site that week.
Sources: Vendor documentation
The connection runs on one person's login
The integration signs in as a named person. When that person leaves, changes role or their password expires, the connection stops or loses permissions, and nothing new moves.
Why it happens. Connections are often set up under whoever built them, and nobody lists them in the leaver checklist.
Usually fixed by: CRM admin and marketing operations.
No public source found: our reading.
Match: Is this person already here?
The same person becomes two (or five) records
One person fills two forms, or attends a webinar with a different email, and the CRM creates a second record. Two reps may call them, or neither does because each thinks the other owns it.
Why it happens. Automated writes and file imports may skip the duplicate warning a person typing in the CRM would see, and matching on exact email misses typos and second addresses.
Usually fixed by: CRM admin (matching rules) with marketing operations (what the connection may create).
Sources: Data-quality report
One person exists as a lead and as a customer contact, owned by different people
After a conversion or an import, the same person can exist twice: an early-stage record and an account record, or a second record in the other tool. Each has its own owner, its own history and its own emails.
Why it happens. The conversion or the sync creates a new record instead of linking to the existing one, usually when the owner or queue setup is unusual.
Usually fixed by: CRM admin, with sales operations (who wins ownership).
Sources: Community thread
Two systems keep undoing each other's changes
A value flips back and forth (a checkbox, a status, an owner) because each system's change triggers the other's update. History gets noisy and rules that fire on "changed" fire again and again.
Why it happens. Two-way sync that cannot tell a person's edit from the connection's own edit.
Usually fixed by: CRM admin and marketing operations together.
Sources: Integration vendor guide · Community thread
A lead from an existing customer is routed as a stranger
A new lead from a company you already sell to goes round-robin to whoever is next, not to the account's owner. The customer gets a second rep, or a cold sequence.
Why it happens. Routing looks at the lead's own fields and does not look the company up first.
Usually fixed by: Sales operations (routing rules).
No public source found: our reading.
Owner: Who gets the lead
New leads sit with no real owner
The lead exists but belongs to a shared queue, a catch-all user, or nobody. No rep sees it in their list, so the response-time clock runs with no one watching.
Why it happens. The assignment rule has no branch for this lead (a new country, a new product, a blank field), so it falls to a default.
Usually fixed by: Sales or revenue operations (routing rules).
No public source found: our reading.
The owner has left or been switched off
A lead or account is owned by someone who is deactivated. Updates to it can be refused, and no one is following up.
Why it happens. When people leave, their records are not reassigned and the routing still names them.
Usually fixed by: CRM admin and sales operations (an offboarding checklist).
Sources: Vendor documentation
Leads from imports and integrations skip your assignment rules
Rules assign owners to leads created one way (a form, a person typing), but leads created by an import or an integration arrive with the default owner, or none.
Why it happens. In some tools, assignment rules run only when each import or call asks for them.
Usually fixed by: Sales operations and the CRM admin.
No public source found: our reading.
Follow-up: Sales starts working it
The lead reaches sales and nothing happens
The lead is in the CRM with an owner, but no call, email or task follows within the agreed time. It cools while reports show it as handed off.
Why it happens. Nothing links "lead created" to "first action due", so it depends on the rep's habit.
Usually fixed by: The sales leader (the agreed time) with sales operations (alerts, automatic follow-up).
Sources: Research article (2011)
Leads that sales rejects or stops working never go back to marketing
A lead sales declines or abandons stays with the rep or is closed, and never returns to nurture. It drops out of both teams' view.
Why it happens. Nobody owns the step from "sales said no" to "marketing keeps nurturing".
Usually fixed by: Revenue operations (the status and the recycle rule).
No public source found: our reading.
The sales tool refuses to enrol the person
A rep tries to enrol a lead and is blocked: the address bounced before, the person unsubscribed, or they are already in another sequence. When enrolment is automatic, the failure is silent.
Why it happens. In some tools, safety rules (bounce, spam, opt-out, one sequence per person) are enforced by the sales tool, but the lead was routed without checking them.
Usually fixed by: Sales operations (rules) with marketing operations (suppression data).
Sources: Vendor documentation
The person is enrolled, but no step is going out
The enrolment shows active, yet the next step never fires. The lead looks worked in reports and is not being worked.
Why it happens. The rep's inbox lost its connection, a send limit was reached, or a send failed, and nobody checks the error list.
Usually fixed by: Sales operations, with the rep.
Sources: Vendor documentation
The sequence is tied to a record that was merged, converted or deleted
A person was enrolled, then the CRM record was merged, converted or deleted. The sales tool keeps pointing at the old one and activity cannot be written back.
Why it happens. Record changes in the CRM are not always carried into the sales tool.
Usually fixed by: CRM admin and sales operations.
Sources: Vendor documentation
Replies: Back to marketing
Replies and meetings do not come back to marketing
A prospect replies or books a meeting, but the CRM shows no activity. Marketing sees a lead that never engaged, sales sees a hot reply in their inbox, and campaign results undercount.
Why it happens. In many tools, activity is logged only when the reply's address matches a person in both systems, so a second email address, a missing record or an auto-reply breaks the link.
Usually fixed by: Sales operations (activity capture) and the CRM admin (email fields).
Sources: Vendor documentation
Someone opted out or bounced in one tool, and the other keeps emailing
An unsubscribe or a bounce is recorded where it happened but not in the other system. The next campaign or sequence mails the person anyway, which hurts deliverability and ignores their choice.
Why it happens. Opt-out may be mapped one way only, a re-subscribe does not always travel back, and nothing syncs before a person's first sync.
Usually fixed by: Marketing operations (consent) with whoever owns privacy.
Sources: Vendor documentation
Reporting: Stage, source, dates
The two systems disagree on stage or source
The same person is a lead in one tool and qualified in the other, or has a different lead source. Reports from each tool tell a different story, and a rule that depends on the value never fires.
Why it happens. Stage and source lists were changed in one tool only, or the sync rules are one-way and never move a value backwards.
Usually fixed by: Revenue operations.
Sources: Vendor documentation · Vendor documentation
The campaign that created the lead is lost
The lead is credited to "direct", "unknown" or a later touch. Campaign reports undercount, and budget goes to the wrong channel.
Why it happens. The source is read from a browser identifier. If a visitor refuses it, switches device or returns after it expires, the form cannot be tied to the earlier visit.
Usually fixed by: Marketing operations and web analytics.
Sources: Vendor documentation
Dates and times land on the wrong day
A lead created late in the evening is counted on the next day, or a weekly report is a day off from the other tool. Response times and "created this week" counts differ between tools.
Why it happens. Some fields store only a date, some a date and time, and tools show them in different time zones.
Usually fixed by: Revenue operations (report definitions).
Sources: Vendor documentation
Navceed is being built to watch hand-offs like this continuously: follow each record through every step, notice when one breaks, show the cause in plain words and prepare the fix for the data owner to approve. Today it works on an example company; connecting your own tools is coming next.