"How many numbers should I keep" usually gets decided by eye: grab a few extra, sort it out later. In practice the right count has nothing to do with how many tasks are queued today — it is set by the number of isolated circuits you run in parallel. Below: how to calculate that count, why a spare number costs more than it looks, and when the portfolio needs trimming rather than topping up.
The number count follows circuits, not task volume
A single number can handle ten tasks a day or one a quarter — workload does not set the count. What sets it is the count of isolated circuits: separate accounts, projects or clients, each needing its own entry point. One active account with daily tasks and one long-lived profile that gets a code once a quarter are two circuits and two numbers, not one heavily loaded number plus a spare. Count circuits, not requests.
The rule: one circuit, one number
Saving on the number count looks reasonable at first: two accounts, one shared number, fewer lines on the invoice. In practice it undoes the exact reason numbers are kept separate. A shared number physically links accounts together: the platform sees the same phone under two profiles and reads it as a sign they are connected, even when both belong to the same person. The isolation that separate numbers exist for disappears the moment one number serves two circuits at once. There is no exception: one number per circuit, and the portfolio holds exactly as many numbers as there are independent circuits to run at once.
How to calculate the actual need
The calculation starts with a list, not a guess. Write down every circuit you run: work accounts, personal ones, test accounts, two-factor bindings, backup recovery channels. Mark each with one of two statuses. First, a circuit needing a standing number: it is used regularly, a code can arrive at an unpredictable time, or the platform expects the same number on every repeat login or recovery. Second, a circuit that a one-off activation covers: the contact is a single or rare event, and holding a slot year-round makes no sense — paying for a code exactly when needed, through the one-off activation section, is cheaper. The count of the first type is the number count your portfolio needs; the second type does not enter the count at all.
Why spare numbers cost more than they look
A spare number in the portfolio is not a one-time cost — it is a standing one. Owning an offline slot costs 0.6 of the price of regular rental for the same term, already a saving over an always-online number, but an idle slot still gets charged that price every paid period regardless of whether a single task lands on it. The free hour of airtime, available up to twice a day, is credited to each slot separately and never pools across the portfolio — a spare number doesn't save someone else's limit, it just adds a line to the invoice with no task behind it. The second cost is operational: offline ownership has no auto-renewal, and every spare number is one more expiry date to track. Three numbers barely register as a mental load; fifteen already need a tracking system.
Reviewing the portfolio and when to trim it
The number of circuits you need is not fixed: projects close, accounts get abandoned, some tasks move to one-off activations. A review every one to two months, timed to the next ownership-term purchase, is when renew-or-release gets decided on current facts rather than habit. The sign that the portfolio needs trimming is simple: two cycles in a row with no task landing on a number, and the circuit it was held for is either closed or no longer needs a standing binding. Releasing it is cheaper than paying for unused ownership, and when the need resurfaces, a one-off activation or a fresh slot costs less than months of idle standby.
Frequently Asked Questions
Can one number serve several accounts at once to save money?
Technically yes, but it links the accounts together in the platform's eyes — a shared number reads as one owner behind several profiles. The rule is one circuit, one number, no exceptions for savings.
How do I know a circuit needs a standing number rather than a one-off activation?
A standing number is needed wherever the platform expects the same phone on repeat logins, recovery, or as a second factor. If the contact is a single event, a one-off activation is cheaper.
How often should the size of a number portfolio be reviewed?
Every one to two months, tied to the ownership renewal cycle: that way each number gets a decision based on fresh task data, not habit.
Build a portfolio of offline slots sized to your circuit count, and compare ownership terms and remaining free airtime per number, in the offline SMS section. The economics of a multi-number portfolio are covered in offline rental for an account portfolio. Why offline ownership has no auto-renewal and how to avoid losing a number at expiry — in auto-renewal of slot ownership.