What this article covers
When you create a document in GetAccept, you can:
Upload a file (PDF)
Build content in the Editor
Use a GetAccept template (Editor or PDF)
Use a Google Docs template
Use a Word Merge document
For most sales teams, the recommended path is:
Use GetAccept templates built with the Editor
(best engagement, best analytics, easiest to scale and reuse).
Use upload / Word / Google Docs mainly when you’re bringing in existing content that must stay as‑is.
Quick recommendations
Use GetAccept template + Editor when:
You send this document type often (proposals, MSAs, NDAs, quotes).
You want branded, interactive content (video, pricing tables, layouts).
You want dynamic data from GetAccept or your CRM (merge fields).
Use Editor (from scratch, no template yet) when:
You’re drafting a new format you’ll later turn into a template.
You need to experiment with content, layout, or messaging.
Use Upload a file (PDF) when:
Legal or marketing owns a locked, final PDF.
You just need signatures and simple fields on top of a finished document.
Use Google Docs (template or import) when:
Your team still collaborates heavily in Google Docs and isn’t ready to move that workflow fully into GetAccept.
Use Word Merge when:
You already have mature Word templates with merge tags and want a quick path into GetAccept without rebuilding everything in the Editor.
Recommended: GetAccept templates + Editor
This is what you want most customers to end up using.
Why templates + Editor are the default choice
Faster sending: One template powers many send-outs; reps only tweak deal‑specific details.
On-brand and consistent: Layout, logos, fonts, colors, and disclaimers are controlled centrally.
Richer experience: Add video, images, tables, and interactive blocks to make proposals feel like mini‑microsites, not flat PDFs.
Data-driven: Use Editor merge fields to pull values from GetAccept or your CRM (recipient, sender, document, entity, deal data).
Easy to optimize: Update one template and every future send-out benefits.
Use a GetAccept template when…
You send similar documents repeatedly (proposals, renewals, NDAs, SOWs).
You want pre-configured fields, roles, pricing tables, and merge fields.
You care about engagement & analytics across a standardized sales process.
When to use the Editor directly (no template yet)
Use “Build content in the Editor” from the create-doc flow when:
You’re designing a new proposal/contract layout and want to play with sections, columns, images, and videos.
You’re creating a one-off, but still rich document where static PDFs aren’t enough.
You want to prototype content that you’ll later save as a reusable template.
Once the layout is stable, convert this into a proper template so reps can reuse it instead of rebuilding each time.
When to upload a file (PDF)
Upload a file is perfect when the document is already final elsewhere and should not be edited in GetAccept.
Use Upload a file if:
Legal has provided a locked, approved PDF and changes must go through them.
You’re sending scanned contracts, order forms, or vendor paperwork you don’t control.
You only need to overlay fields (signatures, text, checkboxes) without changing the underlying content.
What you can still do with uploaded PDFs:
Add signature, text, and other fields via the Add tab.
Connect fields to sender or specific recipients.
Add link fields to direct recipients to external resources.
Limitations vs Editor:
You can’t edit the PDF content itself inside GetAccept.
Fields from the Add tab go only on uploaded files, not on Editor blocks.
When to use Google Docs (keep this small)
GetAccept supports Google Docs templates and importing files from Google Drive, but this is not the primary, recommended path for new setups.
Use Google Docs if:
Your team is already deeply invested in Google Docs for collaboration and wants to keep drafting there.
You need inline edits in Google Docs right up until you’re ready to send.
Typical patterns:
Google Docs template → GetAccept template:
Store Google Docs templates in the configured template folder.
Select them from Use Template in GetAccept, edit in Docs, then send.
Import from Google Drive (PDF):
Choose Google Drive in the content step, select the file, and let GetAccept convert it to PDF for signing.
Positioning:
Use Google Docs when you’re not ready to move that workflow into the Editor yet.
For the best GetAccept experience long term, migrate key templates into Editor-based GetAccept templates.
Word Merge vs Editor merge fields
Both options let you personalize documents automatically, but they serve different scenarios.
Word Merge (good for existing Word templates)
What it is
You upload a .docx file that already contains merge tags (like
$recipient.first_name$).GetAccept reads those tags and replaces them with data from GetAccept when you send.
Best when
You already have mature Word templates and want a fast path into GetAccept.
Legal/ops still manage templates in Word and don’t want to rebuild everything in the Editor yet.
Layout is complex or highly regulated and must stay exactly as the Word output.
Trade-offs
Document behaves like a static PDF with data filled in; you don’t get Editor layouts, videos, or modern content blocks.
Any structural or layout change usually needs to happen back in Word, not in GetAccept.
Editor merge fields (recommended for new templates)
What they are
Merge fields you insert via the { } button in Editor blocks.
They pull data from GetAccept (sender, recipient, document, entity) and from integrated CRMs (via custom merge tags).
Best when
You’re building or modernising Editor-based templates (proposals, contracts, renewals).
You want rich layouts + dynamic data in the same place.
You care about maintaining and updating templates centrally in GetAccept.
Advantages over Word Merge
All content lives in GetAccept, so you don’t juggle Word file versions.
You can mix dynamic text, pricing tables, videos, and layouts in a single Editor template.
Merge tags are visible and selectable in the UI, so non-technical users can add/update them.
How to decide between Word Merge and Editor merge fields
Start with Editor + merge fields for any new or strategic templates (sales proposals, key contracts).
Use Word Merge only as a bridge for existing Word-based processes you can’t yet migrate.
Over time, plan to phase out Word Merge by recreating critical templates in the Editor so you get full benefit from GetAccept’s content, analytics, and AI features.