What the person you ask actually sees

This is the part most worth understanding and the one almost nobody looks at, because it is invisible from your screen. When a supplier does not deliver, very often it is not unwillingness: it is that they did not understand what you were asking for, or did not know how to send it.

What they receive

A message — by email, SMS or WhatsApp — with your name, your organisation's name, what you need and a button. You can personalise the text: a message written by you gets noticeably more replies than a generic notice.

What they do when they open the link

1. 1

   They see the list of what you are asking for

   Only their own: their requests for this phase, with the title and description you wrote.

2. 2

   They upload the file or take a photo

   From a phone they can photograph the document directly. If the photo comes out skewed, the platform straightens it.

3. 3

   They fill in any data you asked for

   If the request included fields, they appear below the file, pre-filled with whatever could be read from the document.

4. 4

   They confirm and finish

   They get an acknowledgement. If you asked for several things, they can come back later with the same link for whatever is left.

Why they do not need an account

That is a product decision, not a limitation. The person you are asking for a certificate is not your user: they are doing you an administrative favour. Forcing them to register means a share of them simply will not, and then you are back to chasing by email — exactly what you were trying to avoid.

The link is personal: it identifies that person and that request, and gives access to nothing else. If they forward it to a colleague, the colleague can deliver on their behalf, and the record shows where it came from.

Frequently asked questions