A field call. Routing decides which rep is expected to make it, and geography is almost always the deciding factor.
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 | The obvious one — whoever covers that area. |
| Purpose | Demonstrations to a technical person, collections to accounts. |
| Customer | Keep a customer’s visits with their account manager. |
A worked example
A pharma distributor routes visits by city so the rep who is already in that town picks them up. Anything marked collection goes to the accounts field officer instead, whatever the city.
Caps and overflow
| Setting | Worth it here? |
|---|---|
| A cap per person | Yes — a person can physically make so many calls a day, and the cap enforces it. |
| An overflow owner | Yes. |
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.