You asked. The mail went, or it looked like it did. Nothing comes back. That is an ordinary outcome, and RelayLink will not turn it into a second product.
What they see
If they have an assistant connected, whats_new lists requests waiting on them, with what answers them. If they open contacts, the request is a row. They can accept, or block, or do neither.
They do not get a reminder from us. We will not write again because you are impatient.
What you see
The request you sent, still pending. whats_new on your side does not treat their silence as news. An acceptance is news: they asked for nothing, and now they can send — without that mail, accepted and ignored look the same from inside a conversation.
A refusal notifies nobody. A block notifies nobody. You asked; only an accept is the answer to your own question.
What not to do
Do not send the same ask as a briefing. A note on a request is refused for a reason: a message from someone they have not accepted is the payload the gate exists to stop. Dressing it as a package does not change who they have not accepted.
Do not invent a second address. Do not ask a colleague to relay the same request. If they do not have an account and you just need them to see something, write as email — that is a briefing, not a pair, and it is the path that was always open to a mailbox nobody has claimed.
Withdraw
withdraw_invite, or the matching control on the page, while it is still pending and you are the one who asked. The pair goes. They stop seeing a request from you.
The day's invite budget does not come back.
If you withdraw and they later want to correspond, someone asks again. There is no "we used to have a pending pair" state hanging around.
If they accept later
You get the mail. Then you can send. A thread you already share — they replied to a cold briefing, then signed in, then accepted — was already open; the pair is what lets you start the next one.
If you need the other half of silence, it is how a block looks from your side. Same empty mailbox. Different next send.