> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dispoiq.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Phone number management

> Search, purchase, manage and request release of sending numbers.

Last updated: October 8, 2026.

Choose a sending number your team can keep track of, confirm its costs before buying, and check the result before buying another. Pausing a sender or removing it from the sending pool is different from giving up a rented number.

This guide is for authorized administrators of US business workspaces with eligible messaging access. Messaging destinations are limited to the US and Canada through routes actually enabled for your workspace. Where number search is available, it offers **US local numbers**; that does not offer Canadian numbers or guarantee a particular area code, route or feature.

## 1. Check access and registration first

Open **Settings → Messaging → Numbers** if your account has the required access. Purchasing can be blocked by your plan, subscription status, messaging setup, registration status, unavailable funding or a disabled purchase control. A displayed result or enabled button does not override the checks made when you submit a purchase.

Where available, the number-purchase workflow requires an approved business brand registration. Buying a number does not establish that its campaign is approved or that it is ready for every sending route. Check messaging onboarding and the restrictions shown for your workspace before sending.

Registration and a sending number do not supply recipient permission. For customer-initiated SMS/MMS messages, follow the prior express written permission requirement under your accepted messaging terms, including its narrow same-conversation rule for a recipient-initiated text. Keep permission records, honor opt-outs and confirm that permission covers your sender and intended messages. Changing numbers does not erase an opt-out or let you evade a restriction.

## 2. Search, check costs and confirm a purchase

Where number purchasing is available:

1. Choose **Add number**.
2. Search by **Area code**, or choose **City** and enter the city and its two-letter state.
3. Review the returned numbers and select the ones you need. A search result is a listing, not a reservation; a number can become unavailable before purchase.
4. Confirm the flat USD \$5 rental: the first charge applies only after successful number activation and covers one month; USD \$5 renewals fall on that number's monthly anniversary. Review how activation and monthly billing dates will be determined under the offer you accept. Registration and messaging charges are separate. If the offer shows a different or unexplained number charge, or those details are missing, ask support before purchasing.
5. Review the selected numbers and the recurring-rental confirmation, then confirm the purchase only if you are authorized to incur those charges for the business.
6. Read the result for **each** selected number. A batch can have different outcomes; do not assume all numbers were bought because one succeeded.

The number-rental policy in this guide is a **flat USD \$5 per number per month**, with **no volume tiers and no separate number activation fee**. Registration, messaging usage and subscription charges remain separate under their accepted schedules. The first USD \$5 rental charge applies only after successful activation and covers one month; subsequent USD \$5 renewals fall on each number's monthly anniversary. This policy does not confirm that recurring collection is currently enabled. A blank or unknown displayed price is not a free number. Capability labels describe the number; an SMS, MMS or Voice label does not by itself make that feature available in DispoIQ or approve its use.

For a rental or purchase-charge question, contact **[support@dispoiq.app](mailto:support@dispoiq.app)** with the number, workspace and purchase reference. Support will compare the offer you accepted, the activation and rental-period information, and any hold or final charge, then coordinate a correction where required by your accepted terms or applicable law. If the offer and charge cannot be reconciled before purchase, wait for clarification before authorizing it. This review does not turn an unknown amount into an accepted fee.

## 3. Check what the result means

| Result | Next step |
| - | - |
| Purchased and added to the pool | Confirm the number appears in your workspace and review its sending status before use |
| Purchased, but configuration or pool setup is incomplete | The number can already be rented even though it cannot yet send as expected; ask for setup review rather than buying a replacement to solve the same issue |
| Purchase in progress or outcome uncertain | Keep the reference and contact support; do not submit a fresh purchase simply because the browser timed out or the number is missing from the pool |
| Unavailable or definitively refused | Read the specific result; only choose another number once the previous attempt is understood |

A funding hold is not a second charge. An uncertain purchase can leave a hold open while its outcome is checked. Once number activation has succeeded, the monthly rental charge can apply even if later configuration fails. Your accepted Terms and the [Subscription, cancellation and refund policy](/policies/billing-refunds), when incorporated, govern charging, authorization, billing corrections and refunds. No rate or refund change is created by this guide.

If a number is missing, its setup is incomplete or a purchase outcome is unclear, contact **[support@dispoiq.app](mailto:support@dispoiq.app)** with the number, workspace and existing attempt reference. Support will check the relevant access, registration and funding status, the purchase outcome, and the number inventory separately from the sending pool, coordinating with authorized technical staff as needed. Use the confirmed result to decide the next step; do not treat a missing pool entry or a browser error as proof that no number was acquired.

## 4. Organize and maintain your sending pool

The Numbers list can show a label, team assignment, sending status and capacity information. Expand a row to edit **Label**, **Assigned to**, **Cap / hour** or **Cap / day** where available. Use the label and assignment to make responsibility clear within your team; assigning a number does not transfer ownership of it or establish exclusive access for that person.

**Warming**, **Active**, **Paused** and **Quarantined** describe sending-pool states. These controls do not establish a guaranteed throughput, delivery rate or permission to send. Before relying on a setting, check its effect on the route and queued work you use; do not assume a pool control stops every communication channel.

From the row menu, **Pause sending** or **Quarantine** can stop that number from participating in the pool's sending rotation. **Pause all** applies to selected rows. **Remove from pool** removes the sender-list entry. These are different from releasing the rented number: they do not themselves confirm release or stop its rental obligations. If a rented number disappears from this list, ask support to check the number inventory rather than assuming it was given up.

Check errors after an edit and verify the displayed result. Keep your authorized business contact and messaging registration details current. If sending is restricted, resolve the stated cause; buying more numbers, increasing caps or changing assignments is not a substitute for that review.

## 5. Request release carefully

Contact **[support@dispoiq.app](mailto:support@dispoiq.app)** to confirm the available release process for the exact number and your workspace. Do not use **Remove from pool** as a release request. Identify your authority, the full number, and any existing purchase or release reference. Do not send passwords, payment-card details or access tokens.

Before authorizing release, stop planning new sends from that number and review any queued communications, public contact details and conversations that depend on it. Ask how those dependencies will be handled. Release is different from a pause or transfer: treat it as giving up the number, without an expectation that it can be recovered. A later holder could receive messages addressed to the old number; do not depend on continued reply access after release.

If you voluntarily release a number before its paid rental month ends, there is no ordinary prorated refund for the unused rental time. Billing-error corrections, refunds required by applicable law and any refund DispoIQ expressly owes remain preserved. This rule does not reduce separate remedies for DispoIQ-caused suspension, breach or early termination.

A request, timeout or failed release is not proof that the number was released. Obtain confirmation of the result and the applicable billing treatment. If the outcome is uncertain, ask support to resolve that attempt before making another destructive request. Release does not itself promise deletion of message history or other records; applicable retention, export and privacy arrangements are separate.

## 6. Cancellation, suspension and transferring a number

Our end-of-access policy is to **release rented phone numbers when paid subscription access ends, unless you separately agree to paid retention**. Canceling renewal does not release a number immediately: paid access normally continues to the end of the paid period. Before an end-of-access release, DispoIQ will warn you about losing the number and explain any transfer process actually available for that number. Ask support before the end of paid access if you want to discuss retention or a possible transfer; neither is established merely by asking.

Paid retention requires a separate agreement identifying the retained numbers and the charges and terms you accept. This guide creates no free grace period, indefinite retention, unlimited continuing charge or automatic card-funding authorization. The data-export window does not extend number retention or messaging access, or expand your rights to licensed information. A release result still needs confirmation; this policy does not establish an automated release workflow or mean that a canceled renewal proves a number has been released.

A messaging suspension or pool pause while paid subscription access continues is different from paid access ending. It does not itself release a number. Confirm the applicable resource-charge terms and available release route rather than assuming the number is free, released or reserved for future recovery.

Support accepts number-retention, release and transfer questions even after ordinary paid workspace access ends or is restricted. It will record the request, verify authority for the workspace and number, check any existing purchase or release attempt and separately agreed retention terms, and coordinate handling through an available authorized route. Support will explain the confirmed result and applicable billing treatment; an unresolved or blocked request is not confirmation of release. Any offered transfer needs its own eligibility, steps, charges and timing disclosed and agreed before you rely on it. This process sets no response or completion deadline and does not establish that a transfer is available.

If you want to move a number into or out of the service, ask support whether that transfer is available for the specific number **before** releasing it or canceling a dependency. This guide offers no self-service porting, transfer deadline, permanent ownership, exclusivity or recovery guarantee. Wait for an agreed process and confirmation before relying on a change.

Valid charges for already-authorized usage and the selected wallet-funding rules remain subject to the accepted schedule and Terms, including all billing-error corrections, applicable-law rights and expressly owed refunds. Saving a card does not itself enable automatic top-ups. Contact support about funding questions or sending restrictions. This guide is an explanatory reference, not a separately accepted policy or a promise of enabled features.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.