Where your lead hand-off from marketing to sales typically breaks

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).
Kind of break, one of six: Return path: does what the next tool did get back to the first? Condition: does a rule that should always hold, hold?
No public source found for this one: it is our reading of how these hand-offs usually work.

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).
Kind of break, one of six: Condition: does a rule that should always hold, hold?
No public source found for this one: it is our reading of how these hand-offs usually work.

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.
Kind of break, one of six: Condition: does a rule that should always hold, hold?
Sources: Vendor documentation

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).
Kind of break, one of six: Field landed: did each field arrive with a value, in the right place?
Sources: Vendor documentation

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).
Kind of break, one of six: Arrival: did it show up in the next tool in time?
Sources: Integration vendor guide · Vendor staff reply in a forum

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.
Kind of break, one of six: Field landed: did each field arrive with a value, in the right place?
Sources: Integration vendor guide · Community thread

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.
Kind of break, one of six: Freshness: is the step still running, and on time?
Sources: Vendor documentation

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).
Kind of break, one of six: Return path: does what the next tool did get back to the first?
Sources: Vendor documentation