This guide provides technical instructions for orchestrating manual and automated reminders to maintain workflow momentum and ensure timely document execution.
Prerequisites
- An active (Sent) envelope with at least one pending recipient.
- Assigned role with permission to manage active transactions.
Strategic Overview
In high-volume document logistics, recipient inertia is the primary cause of delayed transactions. IUSign provides a robust notification engine that allows administrators to proactively engage recipients through both manual "nudges" and pre-configured automated schedules. These notifications are delivered via cryptographically signed SMTP channels to ensure high deliverability and trust. Every reminder event is logged in the transaction timeline, providing an audit trail of engagement efforts.
Implementation Sequence
1. Manual Notification ("Nudge")
Manual reminders are ideal for high-priority transactions requiring immediate intervention:
- Navigate to the Documents repository and select the target envelope.
- In the Recipients module, locate the participant with the Pending status.
- Select the Send Reminder action.
- Forensic Impact: This action immediately dispatches a fresh invitation link and records a
REMINDER_SENTevent in the audit trail.
2. Automated Reminder Orchestration (Growth+)
For organizational efficiency, IUSign supports automated reminder schedules that can be configured during the envelope creation phase or updated while the transaction is active:
- Frequency Configuration: Define the interval between notifications (e.g., "Every 2 days").
- Decay Policy: Set the number of total reminders to be sent before the system flags the envelope for administrative review.
- Logic: The system automatically ceases notifications once the recipient executes their assigned fields.
Technical Specifications: Notification Engine
| Feature | Technical Detail |
|---|---|
| Delivery Mechanism | Secure SMTP (TLS 1.2+). |
| Link Integrity | Reminders utilize the same unique, high-entropy token as the original invitation. |
| Audit Resolution | Millisecond-accurate timestamping of every dispatch attempt. |
| Spam Mitigation | Heuristic rate-limiting to prevent "notification fatigue" and mail server blacklisting. |
Efficiency Pro-Tips for Enterprise Workflows
- Customized Messaging: When sending a manual reminder, append a personal note to provide context or emphasize a specific deadline.
- White-Label Integration: Ensure your White-Label Settings are active so that reminders originate from your corporate domain, significantly increasing open rates.
- Status-Based Filtering: Use the Pending filter in the repository to identify all envelopes requiring reminders in a single view, then utilize Bulk Actions to nudge all recipients simultaneously.
Diagnostic and Resolution Protocols
| System Exception | Probable Cause | Resolution Protocol |
|---|---|---|
| Reminder not received | SMTP block or spam filter | Verify address syntax and advise recipient to whitelist the iusign.com domain. |
| "Send Reminder" inactive | Recipient has already signed | Review the recipient status; reminders cannot be sent to parties who have completed their requirements. |
| Excessive notifications | Automation conflict | Review and adjust the automated schedule in the Envelope Settings. |