All templates

Automated Proof Signing Session Status Tracking

Every morning, WebRun opens Proof, checks the status of every notarization and signing session scheduled since the last run, logs each one to Google Sheets with its outcome, and drafts a Gmail follow-up for any session that was scheduled but never completed, ready for you to review and send.

Runs on WebRun · Strict Lockdown policy
Every day at 8:00 AM WebRunorchestrates each step
1 Proof check every signing session's status
2 Google Sheets log each session's outcome
3 Gmail draft a follow-up for incomplete sessions
In short

How do I track incomplete Proof signing sessions?

WebRun checks Proof every morning for the status of every notarization and signing session, logs each one to Google Sheets, and drafts a Gmail follow-up for any session that didn't complete. You review and send every follow-up, so incomplete sessions get chased without an automated email reaching a signer unreviewed.

  • Every signing session's status is logged the same morning
  • Incomplete sessions get a follow-up draft ready within a day
  • No signing session silently falls through without a next step

Built for title companies · mortgage lenders · real estate teams · legal operations

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens proof.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Proof - check every signing session's status
    proof.com
    WebRun in Proof: check every signing session's status
    WebRun opens Proof to check every signing session's status.
    • Open Proof and list signing sessions scheduled since the last run
    • Read each one's current status
    • Separate completed sessions from anything incomplete

    Done when Every recent signing session's status has been read.

  3. 2
    Google Sheets - log each session's outcome
    google.com
    WebRun in Google Sheets: log each session's outcome
    WebRun opens Google Sheets to log each session's outcome.
    • Add a row for each session with the signer, document, and status
    • Mark whether it completed, was rescheduled, or is still pending
    • Keep one running log across all sessions

    Done when Every recent session's status is logged in Google Sheets.

  4. 3
    Gmail - draft a follow-up for incomplete sessions
    gmail.com
    WebRun in Gmail: draft a follow-up for incomplete sessions
    WebRun opens Gmail to draft a follow-up for incomplete sessions.
    • Draft a follow-up email for each incomplete session
    • Reference the document and the original scheduled time
    • Leave every draft unsent for your review

    Done when A follow-up draft is ready in Gmail for every incomplete session.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
proof.com
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Session status log · Google Sheets
OutputWhat each run produces - A Google Sheets log of every signing session's status plus a draft Gmail follow-up for anything incomplete.
Spreadsheet
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it email the signer without me?

No. WebRun only drafts the follow-up in Gmail. A human reviews and sends every email, WebRun never sends one on its own.

Does it reschedule a notarization session?

No. It only reads the session status Proof already recorded and reports it. It never books, moves, or cancels a session.

How does it decide a session is incomplete?

It reads the actual status recorded in Proof for each session, so a session is only flagged once Proof itself shows it as incomplete or not finished.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.