What Happens To A Lead At 6pm On Friday | Zoho CRM Assignment Rules And Routing

A lead fills in the form on your website at ten past six on a Friday evening. They've just compared three vendors and yours is the one they filled in.

What happens next is entirely decided by configuration. And in a lot of businesses what happens next is: nothing, until Monday, by which point they've had a call back from somebody else.

Everything on screen is a mock demo of Zoho CRM with sample data.

So let's look at where that decision actually lives.

Here's the list. The column that matters is Lead Owner — and notice it isn't in this view at all, which is the first thing to fix.

Every lead has one, and it was set by something. Either a person picked it up, or a rule assigned it, or it defaulted to whoever owns the integration that created the record — which is how leads end up owned by an administrator nobody told.

That column is the shortest possible summary of your routing. If several rows say the same name and it isn't a salesperson's, you've found the problem without opening Setup.

And one fact to hold onto, because it is the single most common reason somebody tells us their assignment rule is broken. Assignment rules never fire on a record a person creates by hand. They run on import, on web forms, and on the API — and that's all. Our six-ten Friday lead is a web form, so it's squarely in scope. But if you test your rule by typing in a lead yourself, nothing will happen, and the rule is fine.

Setup, Automation, Assignment. An assignment rule is a list of conditions checked in order. First match wins, and then it stops. That ordering is the part people get wrong — a broad rule sitting above a specific one means the specific one never runs, and nothing warns you, because both rules are valid.

Round-robin lives here too, and it's the option everyone picks because it sounds fair. It hands leads out in turn.

Now, Zoho did think about the empty chair. A rule entry can require that the user is online, or on shift, or both — and anything that doesn't match, or matches somebody unavailable, falls to a default user you nominate. So the capability is there.

Two caveats that matter in practice. Online status lags by up to five minutes, so a rep who just closed their laptop can still be handed a lead. And all of this only works if somebody configured it. Left alone, round-robin keeps dealing cards to an empty chair — not because Zoho can't tell, but because nobody told it to care.

One more thing about that ordering, because it's the failure people spend longest debugging. Rules are evaluated top to bottom and stop at the first match. A new rule goes to the bottom by default — which means the rule you were most recently thinking about is the one least likely to ever fire. Nothing in the interface warns you. Both rules are valid, both show as active, and the newer one simply never gets reached. So if a rule you built last week appears to do nothing at all, check its position in the list before you check its conditions.

And you can have several rules on one module, with nothing in the product to de-conflict them. Each rule entry takes up to twenty-five criteria, so the temptation is to keep adding rules rather than thinking the order through. Resist it — order is the thing nobody documents and everybody debugs.

Except Zoho did think about that, and put the answer one tab across. Thresholds.

Read what it offers. Set a limit on how many records get assigned to a user. And on overflow, reallocate them back automatically once the intended users become free.

So the empty chair is a solved problem. There is a capacity control, it ships in the product, and it will hand work back when somebody returns.

And here is the list. Empty. No thresholds. Which is the same story as every other screen in this video — the mechanism exists, nobody switched it on, and the default quietly makes the decision instead.

Assignment decides who. It doesn't decide what happens if nobody does anything.

That's a workflow rule, one menu up. A rule that watches for a lead created outside working hours, or a lead untouched after some number of minutes, and then does something — notifies a duty rep, escalates, sends an acknowledgement so the person at least knows they were received.

These two mechanisms are the whole apparatus, and they're usually configured to different levels of care. Assignment gets set up on day one because leads have to go somewhere. The after-hours rule gets written after a deal is lost, if at all.

Five questions to answer about your own Friday evening. Who owns a lead that arrives at six ten on a Friday. How long can it sit unopened before something happens automatically. What happens when the assigned rep is on leave — is there a threshold, and does the work come back when they return. Does the person who filled in the form get any acknowledgement at all before Monday. And who is the default owner on the form itself, because if nobody set one, it is whoever built the form, and that is rarely a salesperson.

If any of those has no answer, that's not a gap in your CRM. It's a decision that hasn't been made, and the system is making it for you by default.

It's worth being plain about why any of this matters, without inflating it. The person who filled in your form at ten past six is, at that moment, comparing you to two or three other companies. They are not going to remember which one replied fastest. They are going to talk to whoever replied first.

That's the whole mechanism. Not a statistic about response times — just the observation that a form submitted on Friday evening is a decision being made over the weekend, and your CRM is either participating in it or not.

The configuration that decides which costs about an hour.

The reason this is worth an hour of somebody's attention is that it's the cheapest configuration in the whole system relative to what it protects. You already paid for the lead.

We build routing as part of an implementation, and we'll write the after-hours path with you rather than leaving it as a default. We scope it before we start.

CodeStringers. Zoho authorized consulting partner, Santa Cruz.