A registered warranty and any claim against it. The owner is whoever handles the claim when the customer rings.
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 |
|---|---|
| Item | Product specialists. |
| Customer | Keep it with their account manager. |
| Serial number | If serials encode a batch or plant. |
| End date | Expiring soon to whoever chases renewals. |
A worked example
An appliance distributor routes warranties by product category so the person who knows that product handles the claim. Expiry notices then reach somebody who can act on them.
Caps and overflow
| Setting | Worth it here? |
|---|---|
| A cap per person | Yes, if claims are a real daily workload. |
| 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.