Send from a template: Quick Send vs Customize

Template sending is powerful only when the decision between Quick Send and Customize Before Sending is clear. Many teams lose time because senders pick a path by habit rather than by transaction needs. This guide provides a simple decision framework you can apply in seconds without sacrificing quality.

If your template catalog is not stable yet, first review Create a reusable template. A strong template baseline is the foundation for fast and accurate send decisions.

What Use Template is designed to do

Use Template starts from a known document packet with predefined roles and field placement. It is designed to reduce repeated setup work. After clicking Use Template, you decide whether this send needs only recipient substitution or deeper wizard edits. That single decision determines whether Quick Send or Customize Before Sending is appropriate.

Quick Send in one sentence

Quick Send is the fast path when structure is fixed and only signer identity changes. You provide current recipient names and emails for existing roles, then send. It is ideal for recurring agreements where the same fields and routing apply every time.

Quick Send advantages:

• Fewer steps and reduced manual editing risk.
• Consistent output across repetitive transactions.
• Faster onboarding for occasional senders.

Customize Before Sending in one sentence

Customize Before Sending opens the full envelope wizard with template content preloaded. Choose this when transaction specifics require edits in Details, Documents, Roles, Fields, or Review. You keep template acceleration while retaining full control.

Customize Before Sending is best for:

• Adding or replacing packet documents for a special case.
• Changing signer count, order, or role assignment.
• Adjusting fields due to negotiation or legal revisions.
• Routing exceptions that differ from default template logic.

Decision matrix you can train your team on

Step-by-step: Execute Quick Send correctly

1. Open template and click Use Template.
2. Select Quick Send.
3. Enter recipient details for each predefined role.
4. Validate names and emails against source records.
5. Send and open envelope detail for immediate status check.

Even in fast mode, do not skip email verification. Most post-send issues are delivery problems caused by typos introduced in a hurry.

Step-by-step: Execute Customize Before Sending correctly

1. Open template and click Use Template.
2. Select Customize Before Sending.
3. Review Details and adjust title or folder as needed.
4. Update Documents for transaction-specific additions.
5. Confirm Roles order and recipients.
6. Adjust Fields and run final Review checks.
7. Click Send Envelope once validation is complete.

This path takes longer by design. The extra minutes are usually cheaper than correcting a sent envelope with wrong structure.

Team policy example for consistent decisions

Many teams benefit from a short policy:

• Default to Quick Send for standard recurring transactions.
• Require Customize Before Sending for any structural exceptions.
• Require second reviewer for high-risk customized sends.
• Document repeated exceptions and convert into a new template version.

This policy avoids endless debate while preserving quality controls. It also creates a feedback loop for template improvement.

Common mistakes and corrective actions

• Using Quick Send when packet changed: resend via Customize Before Sending.
• Editing template too often for edge cases: fork a new specialized template.
• Ignoring role order changes in custom flow: recheck sequence in Roles.
• Skipping post-send monitoring: open detail and assign reminder owner.

Troubleshooting resources: /help-center/send-from-template and /help-center/track-signers-and-reminders.

How this decision ties into the full sending lifecycle

The path you choose at Use Template affects downstream tracking and support. Clean Quick Send execution should produce predictable reminder patterns. Customized sends require stronger Review discipline and often closer follow up. Build this understanding into onboarding so senders treat path selection as an operational decision, not a speed preference.

Continue with Track signers and send reminders to close the loop after Send Envelope.