Work somebody has to do. Routing a task decides whose list it appears on, which makes it one of the more immediately useful modules to automate.
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 |
|---|---|
| Priority | Urgent work to whoever is on duty. |
| Due date | Same-day tasks to the person with capacity. |
| Related module | Tasks about invoices to accounts, about leads to sales. |
A worked example
A service business auto-creates a follow-up task whenever a lead is assigned. A rule on Tasks routes anything marked High priority to the duty coordinator, so urgent work never waits for somebody to notice it.
Caps and overflow
| Setting | Worth it here? |
|---|---|
| A cap per person | Yes. Tasks are a real daily workload and a cap keeps one person from being handed everybody’s follow-ups. |
| 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.