Signature Requests

Zoho Sign sends a document to named signers and records each signature in order. A Beam agent reads the status of a request, who has signed, who is pending, and applies the rule, reminding a late signer, notifying the owner, or updating a linked record once every party has signed. Requests moving through signing need no attention. A request stalled past its deadline, a signer who declines, or a document flagged for legal review is routed to a person, so a contract is never chased or closed out in a way the sender did not intend.

Completed Documents

Once every signer finishes, Zoho Sign produces a completed, legally binding document with an audit trail. A Beam agent detects completion, reads the signed document's metadata, and files or forwards it by the rule, for example attaching the executed agreement to the right deal or storage folder. Standard completed documents are routed to their destination automatically. A completed document with an unexpected signer, a mismatch against the originating record, or one marked as needing retention handling is passed to a person, keeping executed agreements filed correctly and defensibly.

Templates and Fields

Zoho Sign lets teams reuse templates with predefined fields and signer roles for common agreements. A Beam agent reads which template a request came from and the values in its fields, applies the rule tied to that template, and updates the matching system record when the agreement is executed. Requests built from a known template are handled predictably. A request using a modified template, a field left blank that the rule requires, or a template the rule does not recognize is flagged for a person, so no agreement is processed on an incomplete or altered form.