Signature Request Routing

Docnify sends a document to one or more signers in a defined order and tracks who has signed and who has not. A Beam agent triggers when a document is ready for signature, for example after a deal is marked won, reads the signer list from the source record, and starts the request through Docnify. It checks status on a schedule and notifies the internal owner once every signer has completed their part. When a signer declines, a signing link expires, or the order needs to change midway, the agent stops and hands the document to a human to resolve.

Signer Reminders and Deadlines

Docnify can nudge a signer who has not acted and mark a request as expired after a set window. A Beam agent reads the outstanding signer list on a schedule, sends the reminder Docnify supports, and updates the source record with the current wait time so the owner can see where a deal or contract stands without checking manually. If a deadline passes with no signature, the agent flags the document rather than resending automatically, since a missed signature can mean the deal itself has changed and a person should decide the next step.

Signed Document Storage

Once every party has signed, Docnify produces a completed file with the signature trail attached. A Beam agent retrieves that finished document, saves it to the folder or record tied to the original request, such as a customer file or contract archive, and notifies whoever owns that record that signing is complete. Where the storage destination is ambiguous, for example a document tied to more than one deal, or the naming convention is unclear, the agent leaves the file in a holding location and asks a person to confirm where it belongs before filing it.