How to Find Message Requests on Facebook and Messenger

If someone contacts you through Messenger and the conversation is absent from your usual Chats list, check Message requests before deciding it has vanished. Messenger can direct some first contacts to requests instead of the main inbox. It also offers controls over who reaches your chats, your requests, or neither. A request is an invitation to decide whether to talk; it is not a message you are required to answer.

Start in the Messenger app under the account that received the message. From the Chats screen, look for a menu, your profile picture, or a Message requests entry. Open requests and check each category the app displays, including a suspected-spam section if one appears. On a computer, use the Messages area of Facebook or Messenger on the web and look for the same request label. Menu locations vary, so the name of the destination is more useful than a screenshot of one version of the app.

This guide is for a personal Messenger inbox linked to a Facebook account. A Facebook Page inbox, Marketplace conversation, Instagram direct message, or Messenger Kids account can have different controls. If you manage more than one profile or Page, confirm which identity is active before searching.

Find requests in the Messenger mobile app

1. Open the Messenger app and confirm you are signed in to the account where you expected the message. If you switch between accounts, inspect the account name or profile picture before continuing.
2. From Chats, open the available menu or profile area. Look for Message requests. The menu may be shown with a profile image, a row of lines, or a different control as the app changes. Do not rely on a particular icon color or position.
3. Open Message requests and scan the request list. If Messenger shows separate tabs such as You may know and Spam, check both. A message placed in a spam section is not proof the sender is malicious; it means Messenger treated it as potentially unwanted.
4. Open a request only if you want to inspect it. Read the sender name and the message before choosing any action. If you do not recognize the sender, pause before following a link, sharing a code, or moving the conversation into Chats.
5. When you know what the message is, use the controls actually shown on that conversation. Those may include accepting or replying, deleting, blocking, or reporting. The choices can depend on the device and account.

If the app opens straight into an existing conversation, you may have found a chat rather than an unaccepted request. Go back to Chats and search for the sender there. Messenger's request folder is only one possible location for a missing conversation.

Find requests on Facebook or Messenger in a browser

On a computer, open Facebook's messages or Messenger in a browser while signed in to the intended account. Inspect the navigation around the chat list for Message requests. If Facebook first shows a small Messenger panel, use its option to open the full inbox and look again. Then check any separate spam or filtered view the interface offers.

Use the web address you normally use for Facebook or Messenger; do not enter your password into an unfamiliar site that promises to reveal “hidden” messages. A browser may have fewer or differently placed controls than the phone app. If you cannot see the same action on web, inspect the request in the official app before assuming it is unavailable on your account.

The Facebook Help Center distinguishes messages on Facebook from support for the Messenger app and Messenger website. That distinction matters when searching Help: choose the instructions for the surface you are actually using. A Facebook Page administrator should use Page inbox guidance instead of treating the Page's requests as a personal Messenger folder.

What the request categories mean

The main request list and any spam or filtered list are places to review messages that have not entered your ordinary Chats inbox. Meta has shown You may know and Spam as Messenger request categories in its safety documentation. It also describes delivery controls that let people decide whether certain senders reach their chats, requests, or neither. The exact labels and routing can change, so treat the categories as navigation aids rather than a guarantee about who the sender is.

An expected contact might be filtered, and an unfamiliar account can appear in a less restricted list. Look at the message itself, the sender's profile details that Messenger makes available, and whether you were expecting contact. A familiar name or profile photo alone does not verify identity. If the request claims to be from a bank, workplace, courier, or Meta support and asks for a code, payment, or login, verify through the organization's official channel before responding.

Some accounts have different contact settings. Meta has announced stricter messaging defaults for teens in certain age groups and regions, so a missing request does not always mean an invitation was sent and then hidden. Delivery can also depend on the sender's account and your current settings. This guide cannot see or change those account-specific decisions.

Decide whether to accept, ignore, delete, block, or report

If you want to speak with the sender, read the request and choose the Accept or reply action shown in your version of Messenger. Before doing that, understand that replying establishes a conversation rather than merely previewing an invitation. The request may then appear among regular chats, subject to the current app behavior and your message settings.

If you are undecided, you can leave the request unanswered while you verify who sent it. There is no need to accept a request merely to prove that you checked the folder. Meta's Messenger safety material says a person is not notified simply because you opened a message request. The current article's stronger claim that a sender will never know you read a declined message should be removed: read indicators and later actions can vary, and that absolute promise has not been freshly verified for every Messenger surface.

If the request is unwanted, use Delete if your interface offers it. Read any confirmation screen before proceeding because deleting a request may remove your access to that conversation. If the person is bothering you, inspect Block. Blocking messages from a profile is a different action from deleting one request, and the available scope of a block should be read in the confirmation screen. If the content appears abusive, fraudulent, or threatening, use the conversation's Report control where available. Facebook's Help Center identifies blocking and reporting as options for uncomfortable or spamlike messages.

Do not send a password, one-time security code, recovery link, or payment detail to a request sender. A message saying your account will be disabled unless you act immediately is a reason to verify through Facebook's own settings or Help, not a reason to click the message's link. If you are personally at risk, preserve any evidence you need before deleting a conversation and use appropriate local support channels.

If a request is missing

Check the active account first. Messenger can support account switching, and a request addressed to one account will not be in another account's inbox. Next check every request category your interface shows, including spam. Then search Chats for the sender in case the conversation was already accepted or was routed directly to the inbox.

If the person says they sent a message, ask them to confirm that they contacted the correct profile through their own account. Do this outside the suspicious thread when possible. A delivery setting, age-related restriction, sender restriction, or technical issue may prevent the message from appearing as a request. This guide cannot determine which one applies without access to the account's current controls.

If you recently deleted the request, do not assume a copy remains in the request folder. Check existing Chats and any archive the app makes available, but avoid relying on an “undelete” service that requests your Facebook password. If the app appears stale or a menu is absent, update the official Messenger app when an update is available, reopen it, and compare with the official web inbox. These are troubleshooting checks, not a promise that a missing message will be restored.

Review who can reach your Messenger inbox

You can adjust Messenger contact and delivery settings from the account's own privacy controls. Look for wording about message delivery, who can reach you, or privacy and safety, and read the choices for each sender group. Meta describes options that can route contacts to chats, route them to requests, or prevent contact. The exact groups and choices available to you may depend on age, region, profile type, and product changes.

Before tightening a setting, consider whether you want people outside your current friends or contacts to reach you for legitimate reasons. Before opening it, consider whether you are prepared to review more requests. The setting controls future contact routes; it is not a way to retroactively validate an existing sender or recover a deleted request. Recheck it in the official app if you see unexpected routing.

Frequently asked questions

Does opening a message request tell the sender I read it?

Meta's Messenger safety material says opening a request alone does not notify the sender. Do not extend that statement into a guarantee about what happens after accepting, replying, or changing the conversation. If you need to avoid contact, inspect the request and its controls before responding.

Where is the spam folder in Messenger?

Open Message requests and look for a Spam, filtered, or equivalent category. Meta has shown a Spam tab in Messenger request examples. If your app presents a different layout, check its current Help and privacy controls instead of looking for a fixed tab position.

Why is a Facebook message request absent from my main inbox?

Messenger can route some contacts to requests under its delivery controls. The person may also have contacted a different profile, or the conversation may already be in Chats. Check the active identity, request categories, and Chats before drawing a conclusion.

Is a Page message request in the same place?

Not necessarily. This guide covers a personal Messenger inbox. If you manage a Facebook Page, switch to its own messaging tools and follow the Page inbox controls available to your role.

Should I accept a request to stop seeing it?

No. Accepting or replying is for a conversation you want. For unwanted contact, inspect the offered delete, block, or report actions. Read each confirmation so you understand the effect before selecting it.