Skip to main content

Response rates on profiles, with a minimum reply rate to continue viewing new profiles

Many requests never receive an answer. The sender waits a week without knowing whether their request was even looked at. We're planning two changes to address this.

  1. A response rate on every profile

Each profile will show a response rate: out of all the requests that person has received, how many they accepted or declined. Requests left to expire without an answer count as not answered.

Before sending a request, you'll be able to see whether a profile usually replies. You'll also be able to sort and filter the profiles list by response rate. The rate appears on profiles, in the profiles list, and on requests you've sent.

A rate is only shown once someone has received at least 5 requests, so nobody is judged on one or two.

  1. A minimum reply rate to keep viewing new profiles and sending requests

If you open requests and leave them unanswered, you'll need to reply to them before you can view new profiles or send new requests. The requirement is 75%, and it only begins once you've opened at least 5 requests.

How it works:

  • Only requests you have opened count. Requests you haven't looked at yet neve

  • Expired requests don't count, since they can no longer be answered.

  • You can always open, accept and decline the requests you've received. Nothin

  • Your rate updates immediately with each reply, so answering your pending requests lifts the restriction right away.

  • Profiles you've already viewed remain available to you.

  • You can decline requests without an active subscription and without wali verification. Declining is always available, so you're never left with no way forward.

This applies to all users.

Two rates, and why

On your own profile you'll see both:

  • Current response rate — based on the requests you've opened that are still awaiting your reply. This is the figure the 75% requirement uses, and expired requests are excluded from it.

  • Overall response rate — based on every request you've received, including the you let expire. This is the figure other users see on your profile.

The two can differ, which is intended. The first reflects what you can still aders see.

Why we're making this change

A decline is far better than silence. It tells the sender to move on and freeshe aim is not to penalise anyone, but to make sure that a request sent on Nisfreceives an answer.

We'd welcome your views on

  • Is 75% fair, or too strict?

  • Is 5 requests the right point for the requirement to begin?

  • Should letting a request expire affect the figure other users see, as planned, or should only opened requests count there as well?

  • Would seeing a response rate change which profiles you send requests to?

Status: Planned

Log in to comment and vote

No comments yet

Be the first to share your thoughts.