Automatic blocks when taking chats
We need a way to report listeners who BLOCK for no reason.
Every week, MANY listeners, "take" my chats but BLOCK AUTOMATICALLY, without introduce themselves neither saying hello! Most of time, I don't even have time to see who took the chat!! So much that when it tells me that "a listener is ready to chat" and I click on the button for going to the chat, then I get a ERROR CODE because the listener already blocked me !!
There is of course no way to review or report those listeners at all because we can't review/report a listener who did not send at least 2 message and/or blocked us, mainly if we don't even know their name !!
All what I can do is returning in queue AGAIN and again. sometimes SEVERAL listeners do the same in line.
The system protect listeners of fake reviews, yes, but is totally unfair toward members and also toward those listeners who NEED to learn when it's appropriate to block or not for improve.
When we are blocked, we should have the possible to give our version of the situation, maybe the same box like when we are the one who block by example. It would protect them from the fake reviews (affect their ratings) but ALLOW US TO REPORT THOSE ABUSIVE BLOCKS.
If you have any other ideas about SOLVING THIS ISSUE, then please, share it here. We really need to find a solution to it.
I agree with you that the current design is unfair.
It seems to me all you can do is report the error to community@7cups.com along with the time it happened. It also seems to me that this is likely to do no good at all. I trust someone will be kind enough to correct me if I'm wrong.
It's not obvious that anyone can identify the listener, though. It depends on how the system stores data about conversations, and on what queries are set up.
It's also possible that this really is an error made by the system, not an error made by any listener. There might not even be a listener.
Presenting end users with an error number when the system is working correctly (or in any circumstances at all, really) is such glaringly dreadful user interface design, it makes one "gasp and stretch one's eyes", to borrow a phrase from elsewhere.
I disagree, unfortunately, with the implication that we can find a solution to this by sharing ideas in the community. Whoever designed this doesn't seem to care about the community, and the community has no access to the underlying logic of the system.
@TortueDesBois