Match requests

How reaching out works

You send a request to a member, saying what you are proposing. They accept or they do not. If they accept, a conversation opens with your original message already in it, and you take it from there.

You cannot send a second request to somebody who already has one waiting from you, and you cannot send one to somebody you are already talking to.

Requests cost a token, replies do not

Your plan gives you a number of match tokens each month, and the allowance resets on the first of the month.

A token is spent when you send, not when they accept. This is deliberate. Charging on acceptance would make a request free to fire off and would fill everybody's inbox with copy-paste, which is the failure mode we watched happen elsewhere. Spending the token up front means you send fewer and mean them.

Receiving and accepting always costs nothing.

If a request is declined, the token stays spent. If nobody answers at all, the request expires after fourteen days, we email you, and the token comes back to your allowance for the current month.

A request that would be refused, because the member is unavailable or has set requirements you do not meet, is stopped before anything is charged.

Once it is accepted

A conversation opens containing the message you sent. What you proposed is carried over as a starting point, but it is not yet an agreement.

Agreeing is a separate, explicit step, and it is covered in Collaborations.

Requirements members can set

Members can decide who is allowed to contact them. The simplest is to accept requests only from verified profiles. Beyond that, a member on premium can set a minimum Authority Score, a minimum traffic figure, a matching niche, a particular traffic country, or a minimum share of traffic from that country.

When those requirements involve sites, they all have to be met by one single site you own, not spread across several.

If you do not meet them you are told, without the specific numbers. Members set their own bar and do not have to publish it.

Being unavailable

There is a switch on your profile that marks you as unavailable. While it is off, nobody can send you a request. Use it when you are busy rather than letting requests pile up unanswered, which costs the sender a token and gets them nothing.

What you cannot do

A request cannot be taken back once sent. There is no undo, and the token does not return. It comes back only if the request expires unanswered after fourteen days. Write it before you send it.