Where Marketplace Buyer Messages Actually Go
Check Message requests. Marketplace conversations from people you aren't connected to land in a separate folder in Messenger, not your main inbox, and Facebook shows the enquiry count on the listing whether or not you ever opened the message. A rep seeing "3 interested" and no messages is almost always looking at the wrong folder, not at a bug.
Everything ranking for this is written for somebody selling a bookshelf. Restart the app, check your internet, clear the cache. That advice never mentions the folder the messages are actually in, and it never accounts for what happens when thirty listings are live at once instead of one.
This one costs real money. A buyer who messaged and got nothing back does not message twice.
Where the messages actually are
Messenger separates conversations by whether the sender is connected to you. Somebody who is not your friend, and who has never messaged you before, does not land in your main chat list. They land in Message requests, which is a separate tab you have to open on purpose.
For a private seller, that is a minor annoyance a couple of times a year. For a rep with thirty units live, every single buyer is a stranger, which means every single one of your Marketplace conversations starts life in a folder you are not looking at.
There is a second layer underneath it. Messenger also filters some requests further into a spam or filtered bucket, and messages there generate no notification at all. That is where the ones you never even saw a badge for have been sitting.
The check, in order
- Open Messenger and go to Message requests. Read the whole list, not the first three.
- Inside requests, look for the filtered or spam section and open that too. It is easy to miss because it is usually a small link rather than a tab.
- Go to your Marketplace selling page and open each listing with an enquiry count. The conversation is attached to the listing whether or not it reached your inbox.
- Only after all three, consider that something is actually broken.
Do steps one and two before you conclude anything. In our experience most "Marketplace is not delivering my messages" reports end at step one.
Why "3 interested" doesn't mean three messages
This is the other half of the confusion, and it is not a folder problem.
Facebook shows activity counts on your listings — views, and how many people it counts as interested. How Marketplace decides what to show and to whom is described in Meta's own explanation of Marketplace ranking. Those counts include people who tapped through or saved the listing without ever sending you anything. So a listing showing interest and carrying zero conversations is not necessarily a delivery failure. It can simply mean people looked and nobody wrote.
Two different situations, one identical-looking symptom:
| What you see | What it usually means | What to do |
|---|---|---|
| Interest count rising, no messages anywhere including requests | People are looking and not writing | A listing problem, not a message problem. Photos, price, or the title |
| Interest count rising, messages sitting in requests | The normal state of a Marketplace seller account | Work the requests folder daily |
| Buyer says they messaged and you have nothing anywhere | Check the filtered bucket inside requests | Reply from the listing thread directly |
| Views flat at zero across every unit | Distribution, not messaging | See listing problems |
The first row is the one people misdiagnose most often, because "nobody is messaging me" feels like a platform fault and is usually a listing fault. If views are healthy and messages are zero, the listing is being seen and rejected, which is a price or photo conversation rather than a Messenger one.
Why this gets worse at volume
Three things compound once you are posting real inventory.
Every buyer is a stranger. A private seller occasionally gets a message from a friend of a friend that lands normally. You never do. One hundred percent of your Marketplace traffic goes through the requests path.
Notifications thin out. The more conversations arrive, the less any individual one announces itself, and filtered requests announce nothing at all. Relying on a badge to tell you a buyer arrived stops working somewhere around the point the channel starts producing sales.
Threads age out of sight. A request from Tuesday sits below the ones from Thursday. On a busy board, a buyer you never replied to is invisible within about a day, and the enquiry that was going to be a deal quietly stops existing.
The fix is a routine, not a setting. Open requests at fixed times, clear the whole list rather than the top of it, and treat the filtered bucket as part of the job. Roughly forty minutes a day is the real cost of working this channel — what that time actually contains is in lowballers, no-shows and time wasters.
The routine that stops it happening
Three passes a day, at fixed times, and each one covers the requests folder rather than the main list.
| When | What to open | Why then |
|---|---|---|
| Before the floor gets busy | Requests, including the filtered section | Overnight arrivals, and you have time to write properly |
| Early afternoon | Requests | Catches the lunch-hour browsers |
| Evening | Requests, plus listings with new activity | Marketplace traffic is heaviest here and reps skip it |
The evening pass is the one that matters and the one that gets dropped. Somebody browsing vehicles at nine at night is doing it deliberately, and a reply that lands while they are still looking is worth several that arrive the next morning.
Clear the whole list each pass rather than the top of it. Requests sort by recency, so yesterday's buyer is already below today's, and on a busy board a thread you skipped twice is effectively gone.
Digging out of a backlog
If you have just discovered the folder and it has two hundred threads in it, do not start at the top and work down.
Sort by what they said instead. Anything with a specific question about a unit gets answered first, however old — those are people who read the listing. Anything naming a number gets answered second. The bare "is this available" threads older than about a week can be left; the person has bought something else by now, and working through them costs you the hours you should be spending on live ones.
Then set the routine above, so it does not accumulate again. The backlog is a one-off; the folder is permanent.
What about the buyer who says they messaged and you never got it?
Take them at their word and go to the listing rather than the inbox. The conversation is attached to the listing, so opening it from your selling page gets you the thread even when it never surfaced in a chat list.
Reply there and it becomes a normal conversation from that point.
If the thread genuinely is not there, the likeliest explanations are that they messaged a different listing than they think, or that the account they used has since been restricted, which removes their messages. Neither is something you can fix. Move on rather than spending twenty minutes on it.
Does anything actually break?
Occasionally. Messenger has outages like everything else, and a listing that was removed takes its conversation thread with it.
The one worth separating from all of this is account restriction. If your Marketplace access has been limited, listings and their conversations can disappear together, and the symptom looks like a messaging failure from the inside. That is a different problem with a different diagnosis, covered in why Facebook took away your Marketplace access.
Everything short of that — missing messages, interest counts with nothing behind them, a buyer swearing they wrote — resolves in the requests folder far more often than in a support ticket.
Where autobook.io fits, and where it doesn't
This article is about the part of the job we deliberately do not touch, so it is worth being blunt about it.
autobook.io has no inbox. It does not read your Facebook messages, does not reply to anyone, does not sync conversations, and sends no notifications. Nothing in the product would have told you a message was sitting in requests. Every routine described above is manual, done by you, inside Messenger, on your own account.
If you want a tool that answers buyers, other vendors in this market sell exactly that and say so on their pricing pages. We are not one of them.
What we do is upstream: importing inventory off the dealership website, writing an editable description per unit, posting through your own Chrome session, and renewing listings that go stale. The argument for that division is simple enough — the listing work is repetitive and worth automating, and the conversation is the part that actually sells the car.
Frequently asked questions
Why can't I see my Facebook Marketplace messages?
They are almost certainly in Message requests. Conversations from people you are not connected to do not appear in your main Messenger list, and some are filtered further into a spam bucket that generates no notification.
Where is the Message requests folder?
Inside Messenger, as a separate section from your normal chat list. Open it, then look inside it for the filtered or spam sub-section, which is the part most people never find.
My listing says people are interested but nobody messaged. Is it broken?
Usually not. Interest counts include people who viewed or saved without writing. Check requests first; if the messages genuinely are not there, the listing is being seen and passed over, which is a photo or price problem rather than a messaging one.
A buyer says they messaged me and I have nothing. What now?
Open the listing from your Marketplace selling page. The thread attaches to the listing even when it never surfaced in your chat list.
Do I get notified for every Marketplace message?
No. Filtered requests generate no notification, and at volume notifications are not a reliable signal anyway. Check the folder on a schedule instead.
Does autobook.io alert me when a buyer messages?
No. There is no inbox, no notifications and no message reading of any kind. That side of the channel stays entirely manual.