Track offer openings and signatures

After you send an offer for signature, the offer's activities feed records every event tied to the signature request. Use it to check whether the customer ever received the email, how many times you've resent it, when the customer signed, and whether that signature was digital or on paper.

Before you start

The offer needs at least one signature request on it. The activity feed tracks signature events, not offer creation. If you haven't sent the offer yet, see Preview, variants, legal texts, and offer link validity.

Read the activity feed

1. Open the offer in the Portal.
2. Find the Activities or Audit feed on the offer's main view.
3. Scan for the signature events listed below.

Each row shows the event name, the timestamp, and the user who triggered it. If the customer triggered it from the public link, the row shows the customer.

Signature events you'll see

• Signature request created — A Send for signature action. The customer's email left Reonic at this timestamp.
• Customer notification about signature request sent — A Notify action (see Remind customer). The customer got a fresh copy of the same email.
• Signature request withdrawn — A Withdraw action (see Revoke offer). The link went dead at this timestamp.
• Signature request accepted by customer — The customer signed digitally through Reonic's public signing flow. The PDF is stamped with the attestation watermark, and the offer moves to Won.
• Signature request accepted analogously — You uploaded a paper signature (see Upload manual signature). The PDF is the customer's paper signature scan, and the offer moves to Won.

If you're auditing a signed offer, look for Signature request accepted by customer or Signature request accepted analogously. Exactly one of those closes the trail. If you're chasing a customer who says they didn't receive the offer, look for Signature request created and Customer notification about signature request sent. Those tell you whether the email left Reonic.

Confirm the offer email was sent

If the customer says they didn't receive the offer:

1. Open the activity feed and find the Signature request created event.
2. Note the timestamp. That's when the email left Reonic.
3. Check that the email address on the signature request matches what the customer expects.

If the created event exists and the email address is right, Reonic did its part. The email most likely went to spam, bounced at the customer's mail server, or the customer is checking the wrong inbox.

Delivery tracking limits

Reonic confirms when a signature email leaves the system, through the Signature request created event. It doesn't confirm whether the customer's mail server accepted the email, whether the customer opened it, or whether the link was clicked. There's no bounce webhook and no delivery status.

What you can do:

• Treat the Signature request created event as proof the email left Reonic. That's the limit of what Reonic can confirm on its own.
• Use CC on offer sent to check the email content yourself.
• Treat delivery problems as troubleshooting on the customer's end: check spam, verify the email address, and ask the customer to add Reonic's send domain to their safe senders list.

Things to know

• View count carries forward across resends. The signature row (not the activity feed) shows a running view count that increases every time the public link loads, including your own test opens. Resending doesn't reset it, so a high view count on a signed offer reflects every open since the original send.
• The activity feed is the only record of signature events. There's no separate email or delivery log. You read it in the Portal, and it doesn't export as a file.
• Activity feed entries are append-only. Useful when an audit asks whether you contacted the customer between two dates.
• Customer-side events are recorded too. Signature request accepted by customer fires when the customer clicks to sign on the public link, so it's evidence of customer action, not just an internal event.
• A resent signature can leave more than one live link on the offer. If you send a new signature request instead of notifying on the existing one, each send creates its own Signature request created event and its own public link. Withdraw the requests you no longer need (see withdraw).
• Expired links don't notify the customer. If the customer doesn't sign before the validity window ends, the link stops working and no email tells them it closed. Notify the customer ahead of the expiry date to avoid this.

Last updated on September 30, 2026