Recurring revenue. The owner is whoever answers for the renewal — and every invoice the subscription raises is owned by the same person.
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 |
|---|---|
| Plan | Enterprise plans to an account director. |
| Customer | Keep it with their account manager. |
| Renewal date | Renewals due this quarter to whoever is chasing them. |
| Value | Large contracts to somebody senior. |
A worked example
A SaaS reseller routes subscriptions by plan: enterprise to the two account directors, standard across the support team. The renewal reminder then reaches a person, not a shared inbox.
Caps and overflow
| Setting | Worth it here? |
|---|---|
| A cap per person | Rarely. A subscription is a relationship, not a daily arrival. |
| An overflow owner | Rarely. |
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.