> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://myoperator.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How do I safely delete (remove) a DID in MyOperator, and what should I check first?

| Tip
Quick answer: Admins can delete a DID from Manage → DIDs → ⋮ → Delete.

Before deleting, confirm the number is not used in any live call-flow, caller-ID policy, campaign, or porting request. Once you click Delete and confirm, the DID vanishes in under a minute and can no longer be used for routing or outbound CLI.

## When should I use this guide?

Use it when a phone number is permanently retiring or being replaced, and you must ensure calls, caller-ID, billing, and compliance stay intact.

---

## Prerequisites & safety checklist

* IVR/Call-flow — the DID is not an entry number or queue target
* Caller-ID policy — the DID is not the default CLI anywhere
* Campaigns / Auto-dialers — the number is not referenced
* Public listings updated (website, ads, email signatures, etc.)
* The number is not in a port-in / port-out state

## When will deletion NOT work?

If the DID is still mapped as above or is locked for porting.

---

## 5-step deletion workflow

1. Dashboard → Manage → DIDs
2. Locate the number → click ⋮
3. Click Delete
4. Confirm the prompt (type `DELETE` if asked)
5. Wait for the toast “DID deleted”

---

## 2-minute verification test

* Inbound — call another published DID; IVR should answer correctly
* Outbound — place a test call; the correct CLI should show
* Logs — new call entries should not reference the deleted DID

---

## Alternatives to deletion (comparison)

| Action | Keeps number? | Free rental cost? | Best use-case |
| --- | --- | --- | --- |
| Delete | ❌ | ✅ | Permanent retirement |
| Unassign (reserve) | ✅ | ❌ | Transition period |
| Replace CLI, then delete | Partial | ✅ | Number swap/rebranding |
| Disable campaigns referencing | ✅ | ❌ | Short maintenance window |

---

## Important notes & edge cases

* Permissions: only Admin/Owner can delete DIDs.
* Irreversible: recovery is not guaranteed; the number may be reissued.
* Billing: past rentals aren’t refunded; future charges stop per your plan.
* Compliance: regulated routing must use a compliant replacement DID.
* Porting locks: numbers mid-port cannot be deleted until the port completes.
* Caller-ID fallback: outbound calls fail if no other valid CLI is configured.

---

## Troubleshooting table

| Symptom | Likely cause | Quick fix |
| --- | --- | --- |
| Delete button greyed | DID is still mapped in IVR/CLI | Unassign from all flows/policies |
| “Number locked” error | Port-in / port-out in progress | Contact Support |
| Calls still arrive at the old number | External touchpoints not updated | Update website, ads, etc. |
| Agents see “Unknown/Other” CLI | Caller-ID policy is now blank | Assign a valid replacement DID |

---

Keywords: delete DID, remove phone number, caller-ID policy, MyOperator