Signature request sending

BunnyDoc sends a document to one or more signers and records each step of the signing process. A Beam agent creates and sends a signature request when a trigger fires, such as a new contract or onboarding form being ready, filling in the signer details the customer has approved. It reads back the request status and updates the linked record, such as an onboarding or deal tracker, once all signers have completed the document. Requests where a signer's details are missing or unclear are held back for a person to confirm before sending.

Signing progress tracking

BunnyDoc shows which signers on a document have signed, viewed, or not yet opened it. A Beam agent reads this progress on a schedule and applies the rule the customer has set for follow-up, for example sending a reminder to a signer who has not opened the document after an agreed number of days. It updates the related record with current status so other systems reflect where a document stands. Documents stalled well past the expected signing window are routed to a person to decide whether to resend or escalate.

Completed document archiving

Once every signer completes a document, BunnyDoc finalizes it as a signed record. A Beam agent reads that completion event and files the finished document into the destination the customer has agreed on, such as a contract folder or record management system, tagging it with relevant metadata like signer names, dates, and the associated deal or employee record. Documents that complete with a mismatch, such as a signer using a different name than expected or a missing page, are flagged to a person to verify before the document is filed as final and treated as the authoritative signed copy.