The leads we couldn't see
A CRM's worst failure isn't a lead it scores wrong. It's a lead it never shows you. Blake forwards leads in by email, and a guard meant to ignore your own internal mail was quietly eating the ones reps forwarded from their own inboxes. No error, no bounce, no row in the UI. Here is the bug, why silent drops are the most dangerous kind, and how we made sure a forwarded lead can never vanish again.
The worst thing a CRM can do is not score a lead wrong. It's lose one you never knew arrived.
That happened in Blake last week. No alarm went off, because the entire point of the bug was that nothing went off.
How leads get in
Blake ingests leads by email. You forward a thread to your workspace address, Blake reads it, enriches the company, scores it against your ICP, and drops an opportunity in your pipeline. The forward is the whole interface. No data entry, no copy-paste, no "log this in the system later."
That design has one sharp edge: Blake has to decide what counts as a lead and what doesn't. Your own outbound, internal threads, the "lunch?" message from your colleague, none of that should become an opportunity. So there's a guard. If a message comes from your own domain, ignore it.
Reasonable rule. Wrong question.
The wrong question
The guard asked "did this come from our domain?" when it should have asked "did we write this, or did we forward it?"
Picture a rep at Rapid Logistics. A prospect emails them directly. The rep forwards it to Blake to get it scored. Now look at what Blake sees: the forwarding envelope is from the rep, at the rapidlogistics.nl domain. Same domain as the workspace. The guard fires. The lead is dropped.
Not flagged. Not queued. Not parked in a review list. The pipeline marked the message processed, set the opportunity to nothing, and moved on. From the rep's side, they forwarded a hot lead into a black hole and went back to selling, assuming it landed.
We found four real ones sitting in that hole. Powerblock. A logistics prospect. A hardware vendor. A signal company. Real buyers, forwarded in good faith, gone.
Why silent is the dangerous part
A loud failure is a gift. A bounce, a red banner, a "we couldn't read this" reply, any of those and the rep just forwards it again or pastes it manually. The lead survives because the human knows it didn't land.
Silent failure removes the human's last chance to compensate. The rep trusts the tool. The tool ate the lead. Both of them think the job is done. You don't find out until a quarter later when someone asks why that deal never showed up, and by then the trail is cold and the prospect has signed with someone who answered.
For a CRM this is close to original sin. The promise is "forward it and forget it." The second half of that promise only holds if forgetting is safe.
The fix
Two parts.
First, the guard now distinguishes authored from forwarded. A message you wrote from your domain is still ignored. A message you forwarded that contains someone else's thread gets read, because the lead inside it isn't you, it's them. Blake parses the forwarded original and scores the real counterparty.
Second, no more silent drops. Anything the pipeline decides not to turn into an opportunity is recoverable instead of vanishing. If a guard ever fires again, the dropped mail can be found and reprocessed, not lost. A diagnostic now lists inbound that landed without an opportunity, so "where did it go" has an answer.
The four lost leads are getting reprocessed. They'll land in the pipeline they should have landed in, scored, with the company enriched, as if the guard had never gotten in the way.
The lesson we're keeping
Every safety rule in an ingest pipeline is a small bet about what your users will do. Get the bet wrong and the rule doesn't just fail, it fails invisibly, which is worse than not having the rule at all.
So the standard for Blake going forward is simple. A guard can decline to act. It is not allowed to disappear the evidence. If Blake chooses not to make something a lead, you can still see that it tried.
Always be closing only works if you can see what there is to close.