The 15-minute morning Sales QA pass for social DMs
A morning Sales QA pass is a 15-minute daily review of the social conversations that arrived overnight, ordered by which buyer is still waiting rather than by what is unread. It is not inbox triage. An inbox is finished when it is empty, which is a different goal from the one that makes you money.
The question a morning pass answers is narrower: which lead went cold while nobody was watching, and which conversation stalled one message short of a booking. For the longer definition, see what Sales QA for social conversations means. This is its daily version.
Why should the morning check be Sales QA instead of inbox triage?
Because unread is a poor proxy for unanswered. The conversations most likely to be lost overnight already have a response attached, so they never look neglected in a message list.
Two of the six lost-lead patterns Reploom tracks collide in that window. After-hours leads cool down covers leads that arrive outside working hours and wait too long for a real reply. Auto-reply only, no human follow-up covers a high-intent lead who gets a generic acknowledgment and never hears from a person. Overnight, one conversation usually hits both.
In the example report on our homepage, 31% of leads arrived after 20:00, and average DM reply time outside the working schedule was 11 hours 30 minutes against 42 minutes inside it. Those are sample numbers for one account, not a benchmark, but the shape holds: the messages that wait longest are the ones nobody sees until morning.
What does an auto-reply-only lead actually look like?
It looks like a thread that already has a reply in it. Two conversations from the sample report show it, and both leads chased the business themselves.
Nolan Price wrote on WhatsApp: "I work nights and am looking for a consultation right after your studio opens." He got back "Northstar is closed for the evening. A team member will respond after 7 AM", messaged again later, and waited about eight hours for a person. Lead score 78, availability intent.
Zoe Harris wrote on Instagram, ready to start strength coaching before a work trip. She got a generic auto-reply, then chased it herself: "Checking once more in case there is an opening this week." Lead score 93, booking intent, 4 hours 45 minutes of waiting.
Neither thread was unread. Both were unanswered. A morning routine built on unread counts finds neither one.
What is the right order for a daily social sales check?
Work in descending order of what a delay costs you, not in the order messages arrived. Highest lead scores first, then anyone who received only an auto-reply, then anyone who got an answer with no next step, then everything else.
| Check | Time box | What you are looking for | Action |
|---|---|---|---|
| 1. Highest lead scores | 5 minutes | High score plus clear buying intent, still waiting for a human | Reply, or assign a named owner with a deadline |
| 2. Auto-reply only | 4 minutes | Threads where the only overnight response was automated | Answer as a human, referencing what they asked |
| 3. Answered, no next step | 3 minutes | An answer went out, but no booking question, slot, or call followed | Add the missing next step in one short message |
| 4. Everything else | 3 minutes | Comments, mentions, and lower-score questions | Route by intent, handle in a batch later |
The order is what makes fifteen minutes enough; a message list spends them on whoever wrote last.
How does a 15-minute run play out minute by minute?
Minutes 1 to 5 go to the highest-scoring conversations from the last twelve hours. Read the one-line reason and decide whether it is yours or someone else's. A lead in the nineties with pricing or booking intent gets a reply now, or an owner and a time.
Minutes 6 to 9 go to threads whose only overnight response was automated. Nothing in a message list separates a bot reply from a human one, so this block rarely exists anywhere else. Reply as a person, name what they asked about, offer one concrete option.
Minutes 10 to 12 go to conversations that got a real answer and then stopped. Someone heard a price or a schedule and nobody asked for the booking. One message closes it: a slot, a call, or a direct question.
Minutes 13 to 15 go to the remainder. Comments and mentions belong here, and they move faster if you already route them by intent.
What does Reploom do here, and what do you still do?
Reploom surfaces. A person decides and replies. Reploom is not a chatbot and does not send, draft, or queue messages on your behalf.
It contributes the sorting that used to eat the first ten minutes: every Instagram, Facebook, and WhatsApp conversation carries a 0 to 100 lead score, a buying-intent type, and a one-line reason, while unanswered leads and overdue follow-ups sit in a live queue measured against your reply target. Non-leads stay visible, so nothing is hidden.
The judgment stays human. Whether a warm lead needs a price, a call, or a nudge is sales work; the score only points you at the right five conversations first.
How do you know the morning pass is working?
It is working when the same names stop appearing two mornings in a row, and when leads that arrived at 21:00 have a human reply before 10:00, not at lunchtime.
The second signal is slower and more valuable. If the same leak appears every morning for a week, it is a process problem, and a daily pass will patch it forever without fixing it. That is the job of the weekly Sales QA report: repeated leaks grouped into patterns with source conversations attached, and the biggest one becomes a tracked seven-day playbook.
The morning check saves the buyer who is still waiting today. The weekly report changes the reason they were waiting at all. Speed is the lever in both, and we covered why reply speed is a growth lever rather than a service metric.
If your team handles hundreds of social conversations a month, the leads waiting each morning were already paid for once, through ads or content. Reploom runs Sales QA for social conversations against those threads and surfaces the ones still waiting, so the morning pass is a list rather than a search. Book a Demo to see the live queue and the weekly report run against your own conversations.