Decide whether you need many packets or many signers
A service agreement sent separately to twenty customers is different from one agreement that requires twenty people to sign it together. Choose the workflow that matches your purpose before building the recipient list.
For a separate-copy workflow, check that each packet will go to the intended recipient and that any personalized fields belong to that recipient. Do not include one customer’s details in another customer’s packet.
Prepare the template and recipient list
Test a single fictional entry first, then review the entire list before sending.
- Confirm templates and bulk sending are included in the plan.
- Choose the correct document version and inspect field assignments.
- Check recipient addresses and any imported values for missing or duplicated rows.
- Preview a sample packet and the signer experience.
- Review the number of packets and the total credit usage before confirming the send.
Budget for each packet’s limits
One credit per packet. Unlimited files and pages on every plan. Upload limits: 20 MB per file and 100 MB per packet. Review the actual credit usage rather than assuming the number of recipients equals the number of credits.
Sending places the relevant credits on hold. For each packet, at least one signer completing signing consumes the held credits. If nobody completes signing and that packet is voided or expires, the hold is released subject to original credit expiration. Other packets in the batch have their own status.
Follow up at the packet level
After sending, review the individual packet and signer states. A successful send is not a completed signature, and one completed packet does not mean the whole batch is done. Download completed PDFs when the corresponding packets are fully complete.
Docupacket does not automatically purchase additional credits. Review your balance and the published additional-credit rate before a large batch. Normal subscription billing is separate from any optional additional-credit purchase.