Summary

  • Twilio continues charging monthly for numbers held by a suspended subaccount. Closing the subaccount releases all its numbers, and the account cannot be reopened.
  • Recently released numbers have a ten-day restoration route. Retaining numbers through a customer exit requires transfer before closure, with separate requirements for their destination's configuration and registrations.

Twilio's instructions offer a straightforward response to a customer who has stopped paying: suspend the subaccount until payment arrives. The service stops; the number rent stays. The provider's subaccount guide explicitly keeps monthly charges on the phone numbers the suspended account holds.

Suspension prevents the account from making or receiving calls and sending or receiving SMS. It can subsequently be reactivated. Calls already in progress do not end merely because the account is suspended. This is a holding position with defined service effects and a continuing cost, useful precisely because the relationship can resume.

Closing the subaccount has a different reach. Twilio releases every assigned phone number and shuts the account down permanently. It cannot be reopened. An offboarding rule that translates “the customer has left” straight into account closure is therefore making a decision about the whole telephone inventory as well.

Ten days belongs to the number

Twilio's unused-resources guide identifies the action that stops a number's recurring charge immediately: release it. The number leaves the account. The same guide allows recently released numbers to be restored in the current or legacy Console within ten days.

That window concerns number restoration. The closed subaccount still cannot reopen. An exit plan promising ten days to undo the entire customer environment would combine two rules governing different objects. The distinction matters before somebody relies on the supposed return journey.

The immediate billing stop also has a defined object: the recurring charge. Any refund of a period already billed or paid would need its own basis. A company-specific calculation needs its number tariffs, inventory, dependent uses, transfer work and actual traffic. The documents already let it distinguish the choices before assigning their prices.

The current Console asks the operator to type the number to confirm release. The instructions also address numbers with an associated emergency address, requiring prior handling of that address. Even a small inventory cleanup touches configured communications resources. A low-activity row calls for an investigation of its purpose before a disposal decision.

Move what must survive, then close

Twilio recommends transferring numbers to the main account before closing a subaccount if they are to be kept. Numbers can move between subaccounts and between the main account and its own subaccounts under common control. They leave the source inventory and become available in the recipient's list.

The transfer requires the main account's authority. Subaccounts separate each customer's activity and resources, while this decisive exit action returns to a common administrator. The person ending a customer contract and the person able to move its numbers need to meet in the workflow before permanent closure.

This is an internal account transfer, a separate route from porting a number to another telecommunications carrier. The immediate decision needs a specific destination and purpose for each number worth keeping. Only then can account closure accurately execute the chosen disposal of the customer's remaining environment.

A transfer does not promise a fully configured application at the other end. Number settings may need reconfiguration. Toll-Free verifications, A2P registrations and Trust Hub enrolments need resubmission and reconfiguration. Where a number has address requirements, a compliant address must be prepared in the receiving subaccount before the move.

A connected WhatsApp Sender has an especially clear instruction. It does not move with the phone number to the gaining account. The guide calls for a support ticket to move the Sender before moving the number. The digits occupying one inventory cell can have several operational objects attached, each with its own handling.

A number appearing in the recipient's list is consequently an intermediate result. Applicable registrations, necessary settings and a test of the intended use complete the acceptance work. Doing that before closing the old subaccount gives the business a defined future for the numbers it elected to retain.

Paying for an empty shelf has conditions

Keeping everything and continuing to pay may look like the least demanding way to postpone the choice. Twilio's number-use guidance adds a condition: the provider says it may reclaim inactive numbers to comply with local telecommunications requirements. It reclaims numbers in trial and suspended accounts before those in paid accounts.

Its general activity examples are specific: at least three calls made or received in the last month, each lasting twelve seconds or longer and carrying a completed status; or three text messages sent or received in that month. The guide also says no hard rule works identically everywhere. These are general examples for examining use, rather than a worldwide guarantee that a number can be retained indefinitely.

Twilio recommends reviewing activity monthly and keeping inventory close to near-term plans. The unused-resources guide separates the Console's active-configuration column from its traffic-status column. Having voice or messaging configured and having traffic answer different questions. A future commercial use is another decision again.

Retained inventory needs a purpose, an owner and an end condition. Otherwise the next monthly charge is the only appointment firmly in the diary. Subaccount usage is billed to the main account and draws on its common balance, so small leftovers from separate customers eventually meet at the same payer.

An orderly exit first identifies what should remain. It assigns a recipient, prepares the relevant registrations and settings, and then closes the customer account that can safely disappear. Suspend, release, transfer and close each select a different combination of cost and reversibility. The business should choose that combination before its cleanup automation chooses it for every number at once.

Sources