Document Request: one checklist, one client link.

For the client

One link. No account. Works on a phone.

The client gets one text or email with one link. The page shows what is still needed and what is done. Each item is a short step: take a photo, answer a few questions, or sign. Before a photo leaves the phone, the page checks whether it is blurry, dark, or cut off, and says so in plain words. The client can retake it, or send it anyway and let staff decide. A large phone photo is shrunk on the device before it is sent, so the client never sees a "file too large" error for a photo.

For the reviewer

Accept it, or ask for a replacement with a reason.

Staff open each received file next to the checklist. The panel shows what the phone reported about the photo, labelled as guidance, because the server does not rely on it. Accept locks the item and stops its reminders. Reject reopens only that item for the client, with your reason, and leaves the rest of the checklist alone.

Under investigation: AI-assisted review. We are looking at an AI step that reads the received file and tells the reviewer whether it looks like the item that was asked for, for example a statement dated within the last 60 days that shows the client's name. It would use Einstein in an org that has it, or the AI path AutoSurvey already includes. It would not verify identity or authenticity, and staff would still decide.

In the office

Hand the client a tablet to sign in person.

Many consents are signed across a desk. From the request, staff open a link that is limited to one item and expires in 30 minutes, lock the tablet to that page, and hand it over. The log records that the item was signed in a hand-off session that this staff user opened. The client's own private link is never shown on the staff device.

Security, setup, limits and pricing

• Where the data goes. The client link runs on your AutoSurvey Experience Cloud site. Files are stored as Salesforce Files on the record in your org. No third-party document or e-signature service is involved.
• The link. One random 64-character token per request, with an expiry you set. The same guest rate limits that protect AutoSurvey surveys apply.
• The log. Signing activity is written to an append-only object, and each entry carries a hash of the one before it. Checks can flag inconsistencies in retained history, but cannot detect every administrator change.
• Photo checks. The checks run in the client's browser, with no library and no upload. They are guidance for the reviewer, and the reviewer decides. The thresholds are not yet calibrated. AI-assisted review of the received file is under investigation, see above.
• File size. A photo can be any size. The page shrinks it on the device until it fits the 3.5 MB single-upload limit, the same way AutoSurvey's survey file upload works today. A PDF or other non-photo file must be 3.5 MB or smaller in the first release.
• SMS. AutoSurvey builds the short link and the message text, and the SMS tool your org already has sends it from a Flow: Twilio for Salesforce, 360 SMS, Mogli, SMS Magic or Salesforce Messaging. You keep your vendor contract, your sender registration, your consent policy and your opt-out list. AutoSurvey is building this path for survey invitations now, and Document Request uses the same path for the request link and its reminders. Messaging fees are your vendor's. Email reminders use AutoSurvey's existing reminder service.
• Setup. Requires AutoSurvey and its Experience Cloud site. Permission sets split who can send, who can review, and who can see scored results.
• Price. Add-on pricing is not final. There is no per-envelope fee. No delivery date is promised.