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

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 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).
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 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.

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 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).
Kind of break, one of six: Arrival: did it show up in the next tool in time?
Sources: Vendor documentation · Vendor documentation

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

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

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).
Kind of break, one of six: Arrival: did it show up in the next tool in time?
Sources: Vendor documentation