What people see when you send a document to sign

The signing experience, end to end, from the recipient's side.

When to use this. A signer has asked what they will be expected to do, or a document is stalling and you want to know where.

What you’ll need. A document you have sent, or one you can send to your own address to test.

They get an email with a link
The signing invitation carries your branding and sender if you have configured them, plus any private message you wrote for that specific recipient. The link is personal to them — forwarding it passes on their ability to sign.
They may have to prove who they are
If you set an access code they must enter it before the document opens; send that code by a different channel than the email. If you required authentication they must sign in to Formbot first.
They are walked through the fields
The signer is guided field by field through everything they must complete, rather than left to hunt across pages. On a phone the controls sit at the bottom of the screen.
They provide a signature
They can select a typed style, draw one, or upload an image. Anyone who signs often can save a signature once and reuse it. They may also be asked to attach supporting files.
They can refuse
Declining is a formal option, and Formbot asks them for a reason, which is recorded. A decline is a real outcome to design for, not an error.
Everyone gets the finished PDF
Once all recipients are done, the completed document is available to download, along with an audit certificate recording who did what and when.

How to know it worked

You have signed one of your own documents as a recipient and seen every step they go through.