Signature Requests

eSignatures.io sends a document out for signature and tracks who has signed and who hasn't, without requiring either party to print or scan anything. A Beam agent starts a signature request when a record reaches an approved stage, such as a contract ready for a customer's signature, and reads back the status as recipients complete their part. Once every party has signed, the agent updates the record and stores the signed copy with it. A request that stalls past an approved waiting period, or a signer who asks for a change, gets routed to a person to follow up.

Signing Status Tracking

Each document in eSignatures.io carries a status such as sent, viewed, or completed, which a Beam agent reads to know where a contract stands without anyone opening the tool directly. On a schedule the customer sets, the agent checks outstanding requests, applies the approved rule for what counts as overdue, and updates the linked record or notifies the team responsible for the deal. Completed documents get marked closed automatically. A document stuck at viewed for longer than the approved window, with no signature following, gets routed to a person to chase.

Signed Document Storage

Once a document is fully signed, eSignatures.io keeps the completed file with a record of who signed and when. A Beam agent retrieves this completed copy and attaches it to the matching record in the system of record, applying the approved rule for where a signed contract or form belongs. It confirms the attachment succeeded and notes the completion date against the record. A completed document that doesn't match any existing record, or one missing an expected signer, gets routed to a person to file correctly.