To DM someone on Twitter/X, open Chat or Messages, start a new message, choose the correct handle and select Send. If sending is unavailable, check the recipient's contact settings and your conversation's Chat setup. A public profile or Message button does not guarantee that a new request will be accepted.
Start with the inbox your account actually shows
X's current help documents Chat alongside older Direct Message instructions. The names, setup prompts and controls can differ between clients or accounts. Do not treat a screenshot from an older DM tutorial as proof that an option has disappeared from your account.
Before starting, confirm the recipient's handle and why you need to contact them. A short message about an existing discussion is easier to evaluate than a vague greeting followed by an unexpected link. Never send a password, login code or financial credential merely because an account looks like support.
Legacy DMs and current Chat are different
X describes Chat as its encrypted messaging feature. Registration and the conversation's current state matter: requests may be unencrypted until accepted, and a recipient not registered for Chat can receive an unencrypted message. Read the lock/unlock indicator and setup notice rather than assuming every message is encrypted.
X's service notice also distinguishes legacy messages from upgraded Chat conversations. Old messages do not become a separately verified secure archive because the inbox now has a new name.
Use the privacy information for the conversation you are actually opening. Your public-post protection setting is not a universal encryption switch for messaging.
Send a message from x.com
- Sign in and open Chat or Messages in the navigation.
- Use the new-message/compose control and search for the recipient's exact name or handle.
- Check the selected profile before writing. If prompted, complete Chat setup and keep its PIN private.
- Write a brief message, inspect the conversation's privacy indicator, then select Send.
- Check the conversation for your sent message or a displayed error. A message request is not proof that the recipient has accepted or read it.
The legacy DM help uses Messages → New message → recipient → Next. If your account instead opens Chat, follow the current controls and notices there.
Send a message on iPhone or Android
Open the Chat or Messages tab, select the compose control, choose the recipient and write your message. The recipient's profile may also offer a message button. If you do not recognize the profile, open it and confirm the handle before sending.
A visible Message button does not guarantee delivery permission. Current Chat help says the conversation can still require eligibility or an X Number. An X Number is a private contact code, not the recipient's phone number; do not repeatedly guess it or ask someone else to bypass a closed inbox.
If a message fails only in one app, update it and compare with the website. Retain the error text so you can distinguish a client fault from a recipient restriction.
A request is a separate stage of the conversation
When messaging a new contact, your message may land in requests rather than their main inbox. Give the person enough context to decide whether to accept. Do not keep resending the same request because you have not received a reply.
For incoming requests, inspect the sender before accepting a conversation or opening attachments. Check the additional request folders or filters your client offers when expecting a legitimate message. A missing notification alone does not prove the message was never sent.
Chat request limits vary by subscription and can change. Follow the limit or waiting period displayed in your account instead of relying on a single number copied from an older tutorial.
Choose who can contact you
Open the settings available inside Chat or under Settings and privacy → Privacy and safety → Direct Messages. Review who can send requests and any filters. Use the options actually offered in your client; the older DM settings and new Chat interface need not be identical.
For an established legacy DM conversation, closing new requests does not necessarily stop messages from that contact. X's DM guidance directs users to blocking/reporting controls where appropriate. Read what a setting changes before using it as a complete solution.
If an X Number has been shared beyond the people you intended, current Chat help provides controls to turn it off or refresh it. Keep account passwords, login codes and the Chat PIN separate from any contact code.
Check group members before discussing private details
Create a group using the recipient selector or the group control provided by your inbox. Review the participant list and group name before sending. Do not assume everyone knows who else has been added or which earlier messages are visible to a newcomer.
Ask before adding someone to an existing sensitive discussion. If the subject changes or a new participant needs only part of the context, starting a separate conversation can be clearer than bringing them into the whole group.
Group size, history behavior and available controls should be checked in the active client. This guide does not apply a legacy DM group limit to every current Chat conversation.
Check attachments and encryption indicators
Use the photo, file, GIF or other attachment controls shown by your client. Preview the intended attachment and remove unnecessary personal details before sending. A document can contain information beyond what its first page shows.
Current Chat help says conversation content can be encrypted, but associated metadata is not encrypted, and Grok participation changes the content privacy described in that help. Review those notices before involving an assistant in a sensitive conversation. This is a statement of X's documentation, not an independent security audit.
If an attachment fails, try a smaller non-sensitive test file or share an approved link through an agreed channel. Do not upload private conversations to an unknown “DM repair” tool.
Write a message the recipient can act on
A useful first message identifies the context, makes one request and gives an easy way to decline. For example: “Hi, we spoke in the archive-search discussion. May I cite your public example in our guide? I can send the proposed passage first.” This is an example, not a message sent during this review.
Wait for consent before adding someone to a group or sending large files. If they do not reply, use an agreed public contact method if one exists. Buying a subscription does not create an entitlement to another person's attention or a way around their contact preferences.
Why you cannot send the DM or Chat message
- No recipient or no send option: check the exact account and whether it accepts contact from you.
- Chat PIN requested: follow the official setup or recovery prompt. Do not share the PIN with a tool or another account.
- X Number requested: the inbox may be closed to you. Contact the person through a channel they provide; a message button alone is not permission.
- Request limit shown: stop repeated attempts and follow the current limit or waiting notice.
- Media fails but text works: check the attachment and file support rather than assuming the whole inbox is broken.
- Only one client fails: update/reopen it and compare with x.com before changing unrelated account settings.
A failed message does not prove you were blocked, and a sent request does not prove it was read. Keep the exact error and avoid drawing conclusions the interface does not support.
Deletion, recovery and privacy questions
Does deleting a message remove it for everyone?
Legacy DM deletion removes it from your account only, according to X's DM help. Current Chat has separate deletion controls. Read the action's scope in the conversation rather than applying the old rule universally or promising total erasure.
Can I recover any deleted conversation?
No method in this guide guarantees recovery. A personal account export and a current encrypted Chat are different systems. Do not give a recovery service your password, cookies or PIN.
Are all X messages end-to-end encrypted?
No blanket assurance is appropriate. Check whether the particular conversation is Chat, whether the request has been accepted, and the current privacy indicator.
Verify the recipient and the conversation state
Use the inbox your client offers, make one clear request and check the sending result. Respect contact restrictions and keep a separate, appropriate record of important agreements. A personal account backup is useful planning, but not a promise that encrypted or deleted messages can be reconstructed.