The Exact Moment 'Slow to Reply' Becomes 'Ghosted,' According to a New Study

Photo: Natali Hordiiuk, via Unsplash

The three-minute wait that feels like a verdict

You send a message. It gets read. Then nothing. At what point do you decide you've been ghosted, two minutes, two hours, two days?

A 2025 study in Computers in Human Behavior by researchers Christiane M. Büttner and Sarah Lutz tried to actually measure that moment instead of just describing it. They call it "response delay tolerance", the amount of time someone will wait before a silence stops feeling like a pause and starts feeling like rejection. And the answer isn't a fixed number. It's something each of us calculates on the fly, badly, using clues we don't even notice we're using.

How they measured it

The design was unusually careful for a topic normally left to advice columns. First, the researchers pretested 36 different chat scenarios on 98 participants, varying three things: how close the two people were, how urgent the message was, and how responsive the other person had been up to that point. Then, in the main study, 339 participants worked through those calibrated scenarios and reported the exact point at which they'd start to feel ignored.

Two factors turned out to predict a shorter fuse: how urgent the message was, and how responsive the other person had already been. Closeness, oddly, barely mattered. Once someone had feelings of being ignored, that feeling predicted what they did next: send a friendly follow-up, send a confrontational one, or quietly go cold themselves. People higher in rejection sensitivity, fear of missing out, or with a history of being excluded online tended to snap to "ignored" faster than everyone else.

The part that should bother anyone tracking their own reply habits

The detail worth sitting with is "how responsive the other person had already been." Delay tolerance isn't a universal setting. It's relative to the pace a specific person has already established with you. Reply fast for a week and a two-hour gap can read as a red flag. Reply slow and consistent from day one, and a two-hour gap barely registers.

That's a pace problem, not a volume problem, and it's exactly the kind of thing a single aggregate number can't show. RizzStats' reply rate tells you what share of your matches you responded to at all. It says nothing about whether you replied in six minutes to one person and six hours to the next, or whether your pace with any one match held steady or lurched. That rhythm only shows up in the activity timeline, the day-by-day shape of when you actually opened the app and typed something back, and in streaks, which are really just a record of how consistent your own tempo has been.

None of this means faster is better. Consistency, even a consistently slow one, appears to be what keeps the clock from running out on you. It's the whiplash, quick then quiet, that seems to read as ghosting even when nobody meant it that way.

If you're curious whether your own pattern looks steady or spiky, that's the kind of thing an actual export shows more honestly than memory does. Upload one and the timeline will tell you what your matches were probably reading into your silences before you ever did.