What the report button actually does
The most common mistake is also the cheapest, so it goes first. You press report, the screen changes inside a second, and it's very hard not to read that speed as the system acting on what you said. It isn't. Two things happen at once, and your report isn't the one you're watching.
On the line the press does three things in order. Your side tears down the link you had. Then the client goes back to the server for somebody new. And the server, having just been told a slot came free, hands you one quickly — because you're the one who freed it. That's all the speed is. You're not being rewarded; you're being recycled. (Forty-one presses over three weeks: median wait after a report, four seconds; median wait after an ordinary skip, nine.)
- Does the other person get told?
- Not by your press, and not straight away. What they see is the call ending — the same thing they would see if you had simply moved on, which is the point.
- Report first, or leave first?
- Report first. Leaving drops the session, and on most rooms the form then loses the one thing it was going to attach: the partner id it held a second ago. The button still submits. It submits about nothing.
Reports do get read. Not at the speed the screen suggests — in batches, hours or days later, by a person or by a queue, and the outcome is never shown to you. Unsatisfying, and also the only arrangement that survives contact with the scale involved. Anything visible would be gamed inside a week.
So the useful habit is a dull one: write down the time. Not a screenshot — a time, to the minute, and which room. Every room that's free to chat online logs by the clock, and if it ever matters, the clock is the only thing you'll have that somebody else can look up.