Who owns the relationship once somebody is actually buying. This is not about who wins the deal; it is about who answers the phone in eighteen months.
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 |
|---|---|
| City / State | A territory account manager. |
| Industry | Where knowing the trade matters. |
| GSTIN | Registered vs unregistered, if you treat them differently. |
| Payment terms | Long-credit accounts to somebody senior. |
A worked example
A distributor with 400 customers splits them by state. Four rules, one per region, each handing to that region’s account manager. New customers created by anybody in the business land with the right person automatically, and nobody has to remember the map.
Caps and overflow
| Setting | Worth it here? |
|---|---|
| A cap per person | Rarely. A customer is a long relationship, not a daily workload, so a per-day cap makes little sense. Use it only if you are deliberately levelling a book of accounts. |
| An overflow owner | Rarely needed, for the same reason. |
Nothing stops you setting either — they are offered on every module. It is simply that a daily limit answers a question this module rarely asks.
Where to go next
Something missing or wrong here? Tell us. A question that needed asking usually means a page that needed writing.