Frequently asked questions.

For document generation, no — DocRoute renders PDFs entirely inside your Salesforce org and stores them as Salesforce Files. The only time data leaves your tenant is when you explicitly dispatch a generated PDF to an e-signature provider (DocuSign or Adobe Sign), which happens at your request, on your contract with that provider.

A minimal permission set granting read access to the records you plan to template against, plus write access to the DocRoute custom objects (templates, selection rules, generation jobs) and to Salesforce Files for saving generated PDFs. The package ships a recommended permission set you can review before install.

Inside your Salesforce org. The enterprise-grade renderer that ships with DocRoute is implemented as Apex + Visualforce (or via a sandboxed Apex callout to an org-private compute endpoint, depending on tier). If you prefer your own renderer, the plug-and-play adapter interface lets you point at any internal PDF endpoint.

DocRoute hands the PDF and recipient list to your e-signature provider (DocuSign or Adobe) using their official SDK. Signed documents are returned and stored in Salesforce Files; the signing process itself happens on the provider's infrastructure, governed by your contract with them. DocRoute never proxies signatures.

Standard double-brace handles: {`{{Quote.Name}}`}, {`{{Account.BillingCountry}}`}, plus collection syntax for related lists: {`{{quote.lineItems[].product.Name}}`}. Aggregates (sum, count, avg) and conditionals (if/else) are built in.

Yes — DocRoute resolves multi-object queries via your record's relationships. A quote template can reference the parent Account, the Opportunity, line items, contacts, custom objects — any related record reachable from the originating record.

Auto values like {`{{_today}}`}, {`{{_pageNumber}}`}, {`{{_totalPages}}`}, and formatted dates ({`{{_today:"MMM d, yyyy"}}`}) are built in. You can also define computed expressions in the template builder.

Yes — {`{{#if condition}}…{{/if}}`} and {`{{#each list}}…{{/each}}`} with optional {`{{else}}`}. Use any boolean expression or comparison.

Both. Starter includes DocuSign; Growth and Enterprise include both. You can dispatch to either provider from the same Generate Document action — the routing is configured per template.

A template defaults to one provider per dispatch, but you can let the originating user pick at runtime, or set the provider via your own logic (e.g., region-based routing). Both DocuSign and Adobe webhook callbacks update Salesforce automatically.

Each e-signature provider posts callbacks to a DocRoute Apex REST endpoint inside your org. DocRoute verifies the signature, updates the related case/job record, and triggers any downstream automation you've configured (Flow, Apex trigger, etc.).

Roughly 5 minutes for the managed package install plus 30–60 minutes for the first template and selection rule. Most orgs ship their first production document in an afternoon.

No. DocRoute is built to be configured by a Salesforce admin without consultant help. The WYSIWYG template builder, selection rule builder, and Setup wizard cover the standard rollout end to end.

Yes — install the same package in any sandbox. Useful for staging template changes or testing e-signature flows without consuming production document credits.

Most existing templates port well to the DocRoute builder. We typically run dual-rail for one billing cycle: keep your existing tool generating production documents while you author and test DocRoute templates side-by-side, then flip the source. Get in touch and we'll help scope the migration.

No. DocRoute is priced on document generation volume per org. Add as many users as you want — pricing tracks only the documents you actually generate.

One generated PDF = one doc gen, regardless of page count or whether you also dispatch it for signature. Re-generating the same document from the same record counts each time. Failed or test generations in dry-run mode do not count.

You can either purchase additional volume blocks (pre-pay) or move to the next tier. Hard caps are off by default — we'll alert you well before you exceed your plan so you can decide. Enterprise customers can negotiate burst allowances.

Yes — 30 days, no credit card. Request access from the contact page and we'll email you the install URL and a trial activation token.

DocRoute uses batched Apex + queueable jobs for multi-page or multi-record renders. Each page render runs within its own transaction. Very large documents (50+ pages with complex queries) automatically chunk into multiple jobs and reassemble.

Yes — that's the Growth tier and up. Implement the DocRoute adapter interface (Apex), point at your internal renderer's endpoint, and DocRoute will use it instead of the built-in. Useful for orgs with specific font, layout, or compliance requirements.

Every generation creates an immutable record (template version + record snapshot + generated PDF). Re-generating the same record creates a new version; older versions remain in Salesforce Files. Growth tier and up includes version comparison and rollback.