← Desk
dealers · 2026-09-02 · 1m30s

09-02 CRM Automation vs. Sales Workflow: Creating an Exception Status to Prevent Auto-Lost Leads

id b40aa1f0e20d74619f6913092c4d3d46inferred

Core Synopsis

A systemic conflict exists between a sales user's workflow and the CRM's automated data hygiene rules. The user, Speaker 1, requires a way to keep leads in an "open" state indefinitely, as their process involves long-term nurturing. However, the system is configured to automatically mark idle leads as "Lost" to prevent data clutter for the broader team. This tension reveals a classic design trade-off: a one-size-fits-all automation that benefits the system's overall health is actively undermining the productivity of a high-performing individual. The immediate need is to find a system-compliant exception or a specific status that exempts designated leads from the automated "Lost" rule.

The Problem: System Rules vs. User Workflow

The Pain Point

Speaker 1 is losing visibility on active, long-term leads because the CRM system automatically marks them as "Lost" after a period of inactivity. This automated action directly interferes with their daily task-based follow-up process, forcing them to combat the system instead of using it. The core request is for a state where a lead is never marked "Lost" unless they manually trigger that action.

The System's Rationale

The automated "Lost" rule is not an error but a deliberate design choice. As explained by Lance, it exists to maintain data hygiene across the entire user base. Without it, the CRM would accumulate thousands of unmanaged, "dead garbage" leads, as most users do not proactively clean their pipelines. The rule serves the collective by preventing data bloat at the expense of individual edge cases.

The Proposed Workaround

Lance identifies a potential solution within the existing system. There should be a specific lead status, such as "On Order," that is exempt from the automatic "Lost" rule. Placing a lead in this status would allow it to remain in the system indefinitely, effectively creating the exception Speaker 1 needs without requiring a fundamental change to the system-wide rule.

Next Move

@Lance

  • [ ] Call the vendor (Gage) to confirm which lead status exempts a lead from being automatically marked "Lost" - [TBD]
No device highlights on this take.
0:00
So I make, make a task every day.
0:02
Yeah. So now what you're talking about is there's probably a rule. So you're saying, even if you haven't marked hot, it disappears after a while. Yeah. So there's a rule in there, and I know what the rule is. I just need to probably call my Vendor.
0:15
Yeah. If I could just turn it off so that it never marks my leads lost unless I mark it lost, that would be.
0:20
Well, but so yeah, there's a rule where things do get marked lost after a while. Yeah. But there should be a. There should be a mode you can put it in, a status you can put it in where it never gets marked lost.
0:30
Correct. That's what I would like.
0:31
Um, like on order or like on order is one. You know that if you put something in on order, it'll just stay there for like almost indefinitely.
0:37
So I should do that then.
0:39
No, just hang on. Let me let me call Gage.
0:41
There's no need for them to mark anything lost unless it's lost. I will mark it lost if it gets lost.
0:46
Things have to. The reason those rules exist though is because you'll have, you know, a bunch of garbage, like let's say just random. Leads that come in, not ones you're actually talking to. Yeah. No contact, no nothing. It's just dead garbage. And if you don't have it marked to go automatically lost, you'll just end up with thousands and thousands of open and fucking yeah, all marked lost because people don't mark them lost. I do. You're different.
1:11
Can I turn it off for me, and you can leave it on for everybody else?
1:15
I don't know. That might be a question too. Yeah. I mean, no, it's fine. It's fine. Trying to do what now? Log in or log in?