Working with starter presets and drafts
4 min read
Updated Apr 14, 2026
Starter presets help new drafts move faster, but they are not full template automation. In the current workflow they are best treated as draft accelerators layered on top of your own PDF and routing work.
Before you begin
A new or existing draft
A source PDF or a planned source PDF upload
An understanding that presets do not build reusable field maps yet
Use presets as accelerators
The built-in presets prefill draft copy and category context for common document types.
You can still edit every later step before sending.
Keep drafts explicit
Draft titles, descriptions, tags, and references matter because they help your team find and review packages later.
A good draft record is also easier to reopen if the package needs more work before delivery.
Do not over-assume template automation
Reusable server-side document templates and shared field-map automation are not the live behavior in the current rollout.
If your process depends on strict standardization, document it internally rather than assuming the product enforces it yet.
Pro Tips
Rename preset-based drafts immediately so they reflect the real package.
Use tags and references consistently if your team searches by case or contract ID.
Review old drafts regularly so stale work does not clutter sender boards.
Was this article helpful?
Use this as a quick signal while the public knowledge base is static.
Need more help?
Our support team is here to assist you.