Should You Turn On Your X Number for DMs?
An X Number lets people who do not follow you open a Chat with you. The real question is how much unfiltered inbox a creator can carry.
Turn your X Number on if you take work through DMs, and leave it off if your inbox is already more than you can read in a day. That one line covers most of the X Number DM question, though the details decide whether you regret the switch a week later. X announced the feature on 22 September 2026, and the prompt started appearing for people trying to message accounts with a closed inbox.
The number itself is a numeric access code that lives inside Chat, and someone who does not follow you types it to land in your inbox. It is not your phone number, and nothing about it touches your carrier. The chat safety number is something else entirely, built so two people in an encrypted conversation can confirm who they are talking to.
What follows is a decision piece rather than a setup walkthrough. The tables sort when an open door pays for itself, where sharing the code costs you later, and what switching it off does not stop. Rollout is gradual, so the screen may not look the same on every account yet.
What Is an X Number and What Is It Not?
An X Number is a numeric access code inside Chat that lets people who do not follow you reach your inbox. According to X's help page, having one is optional, and you start using it by switching Enabled on. Nobody can look the code up from your profile or your username.
Confusion starts with the word number. A phone number, a customer service line and the chat safety number all carry the same word, and none of them is this feature. Safety numbers verify identity inside an encrypted conversation. An X Number is a door. X's help page does not publish how long the code is, so treat any article quoting a length as guesswork.
| The X Number is | The X Number is not |
|---|---|
| A numeric access code inside Chat | Your phone number or anything a carrier issues |
| Optional, switched on with Enabled | On by default for every account |
| A way for a non-follower to open a direct message | A verification tool like the chat safety number |
| Replaceable at any time with Refresh | Permanent, or published on your profile |
Anyone trying to message an account with a closed inbox meets a prompt along the lines of "Enter X number to contact them". X's help page is explicit that the prompt appears whether or not the other person has created one, and that X does not reveal who has one. So the prompt is not evidence that a number sits behind it. Chat itself carries end-to-end encryption, though X's help page notes that message requests are not encrypted until you accept them.
Who Can See Your Number Once You Share It?
Anyone you have already exchanged messages with in a direct conversation can see your X Number, and from there you lose control of where it goes. X's help page says plainly that those people may share it with others. Whoever holds the current number can message or call you while it is enabled, even without following you.
Hide from others narrows only the first half of that. Switching it on stops the code from showing inside conversations you already have, so an old contact cannot scroll back and copy it. The number itself keeps working. Somebody who wrote it down last month can still use it, because hiding controls visibility, not access.
Treat the code as semi public from the moment it leaves your hands. A client pastes it into a group thread. A screenshot of your pinned post outlives the post. Refresh exists because X expects exactly this pattern, and a creator who shares the number widely should expect to use it more than once.
Should a Creator Keep the Number On All the Time?
Most creators should run the number in seasons rather than leaving it on permanently. An open door pays only when somebody wants to walk through it. While you are chasing inbound work, the noise that arrives with the code is the price of the briefs you win. In a quiet month it is only noise.
Be honest about triage time before you switch Enabled on. Every message that arrives through the code is one you have to read, sort and either answer or drop. If nobody has that half hour each day, the number becomes a slow leak of guilt rather than a growth channel. The table takes a side on each situation.
| Situation | Keep it on | Turn it off |
|---|---|---|
| Open pitching season | Yes, the inbound is the whole point | Only when the replies stop happening |
| Launch week | Yes, if someone watches the inbox hourly | If nobody can answer within a day |
| Support inbox with a team on it | Yes, it beats sending people to a form | While the team is away |
| Small personal account | Rarely worth the noise | Off by default |
| The number has leaked | Refresh rather than close the door | If refreshing does not calm it down |
| No time to triage this month | Not this month | Off until the time exists |
The leaked row deserves a note. Refresh replaces the code, which is cheaper than shutting the door on everyone with a real reason to write. Switching Enabled off is the heavier move, and it belongs after a refresh that failed rather than instead of one.
Where Should You Share an X Number and Where Should You Not?
The right places are the ones you can take the code back from, and the wrong ones archive it forever. A pinned post and a profile bio are publication rather than sharing. Screenshots, caches and reposts mean you cannot withdraw the code by deleting the post, so a bio share stays public for as long as anyone kept a copy.
Time boxed places behave better. A conference badge, an event chat, a workshop slide or a cohort group each reaches people who need you this week and stops mattering afterwards. Email to a client or a prospect works best of all, because you know exactly who received it and the code sits in a thread you can search later.
| Where you share it | How long it lives | Verdict |
|---|---|---|
| Pinned post or profile bio | Forever, copies included | Avoid unless you want a public inbox |
| Conference badge or event chat | The length of the event | Good, refresh afterwards |
| Client or prospect email | As long as the thread | Best, it stays traceable |
| Reply under a public post | Forever, readable by anyone | Avoid |
Refresh is the reset button for all of it. According to X's help page, tapping it replaces your number with a new one. People who only have the old number cannot use it "to reach you as a new contact", which is the official wording and worth reading literally. You can also see when somebody has reached you through the code. That gives you a trigger, because an arrival you cannot explain is a reason to refresh the same day.
Does the Number Bring Calls Too?
Calls ride along with the code, though only inside whatever your call settings already allow. X's help page says a person holding your number can also call you, "subject to your call settings". The qualifier matters, because it means the feature does not overrule decisions you have already made about who may ring you.
X's own calls page adds the part most summaries skip. Starting a call needs Premium, while any account can receive calls. That same page still carries an older rule: you can only call someone who has sent you a Direct Message first. The rule sits awkwardly beside a feature built for strangers, and X has not reconciled the two pages. Read the call side as unsettled.
A creator who does not want voice or video contact should open the call settings before touching the number. Switching the X Number off to dodge calls pulls the wrong lever.
What Does Turning It Off Actually Stop?
Switching the number off stops one thing, and it is narrower than most people expect. According to X's help page, turning off or refreshing your X Number does not remove the X Number prompt other people may see. Someone trying to message you is still asked for a code. What changes is whether typing one actually reaches your inbox.
The real cost sits elsewhere anyway. A conversation opened with your code lands in the main inbox rather than in message requests. Nothing sits between a stranger and your unread count. Accounts that buy Twitter followers to widen their reach should plan for the inbox that comes with a bigger audience, because reach and messages grow together. Block and report stay the tools of last resort, for when one person becomes the problem.
| What you do | What it stops | What it does not stop |
|---|---|---|
| Switch Enabled off | A typed code reaching your inbox | The prompt other people see |
| Tap Refresh | The old code working for new contacts | Conversations already open |
| Turn on Hide from others | Old contacts seeing the code | The code working for whoever kept it |
| Block an account | That account messaging or calling you | Anyone else holding the number |
Read the table as a ladder. Hide from others is the lightest move, Refresh is the everyday reset, switching Enabled off closes the door, and blocking deals with one person. None of them hides the fact that a prompt exists, because X does not reveal whether any given account has a number.
Is the Number Worth It for Your Account?
The number earns its place only when a message from a stranger can turn into money, a collaboration or a story. If that never happens, the code is an inbox tax. When it happens sometimes, the question becomes how cheaply you can keep the door open. The X Number DM decision is a capacity question wearing a privacy costume.
- Solo creator. On during pitching and launch seasons, shared by email and at events, refreshed afterwards.
- Small agency. On, with one person named as the reader, because an unowned inbox is worse than a closed one.
- Shop taking customer questions. On, shared wherever you publish support hours, refreshed when spam arrives in batches.
- Personal account. Off. The people who matter can already reach you.
The separate XChat app arrived in April 2026 and was pulled from the App Store and Google Play on 14 September 2026, with no official explanation. That removal changes nothing about the decision here, because Chat inside X keeps working.
The rule fits on three lines.
- Turn it on when you want inbound work and somebody is genuinely reading the inbox.
- Refresh the moment a message arrives from a source you cannot explain, and again after every public event.
- Turn it off when the triage time disappears, and remember that the prompt other people see stays either way.
This article was last updated on 25 September 2026 friday. Today, 40 visitors read this article.
