The one everybody starts with. A lead is an enquiry that has not been qualified yet, and the cost of it sitting unowned for a day is the whole reason assignment exists.
Leads are the only module that can also cap untouched work — how many a person is sitting on that nobody has rung. That is usually the more useful of the two limits.
What you would route on
Any field on the module can be used, including ones you have added yourself. These are the ones businesses reach for:
| Field | Why you would route on it |
|---|---|
| Source | IndiaMART, Google Ads, website form, walk-in, exhibition. The commonest thing to route on. |
| City / State | A regional desk. South India to one person, North to another. |
| Expected value | Send the large enquiries to somebody senior. |
| Industry | Where your team has specialists. |
| Rating | Hot enquiries to whoever is free now. |
A worked example
A fabrication business runs Google Ads. Ads leads land overnight and go cold by morning. One rule: Source is one of Google Ads, Facebook → the two people on the digital desk, in turn. A second rule underneath: every record → the whole sales team, in turn. The first rule catches ad enquiries; the second catches everything else so nothing is left ownerless.
Caps and overflow
| Setting | Worth it here? |
|---|---|
| A cap per person | Yes, and this is the module caps were built for. Ten or twelve a day is a realistic figure for somebody who also has to ring them. |
| An overflow owner | Strongly. Leads arriving overnight when everybody is at their cap is exactly the case the tray exists for. |
Where to go next
- Writing the rule
- When it runs — on create, on edit, or both
- Capping how much each person gets
- Where the overflow goes
Something missing or wrong here? Tell us. A question that needed asking usually means a page that needed writing.