Sliick / Apps / Sliick Docs / Starter templates
Sliick Docs · Starter gallery

Starter templates.

Six ready-to-import templates built on Salesforce standard objects. Download the .sdt file, import from the Sliick Docs Template Library, set a test record, validate, proof, and publish.

← Back to Sliick Docs Read the user guide
What's in the box 6 templates
Schema templateExport · schemaVersion 2
Objects Standard objects only
Status on import Draft (you publish)
Cost Free
How to import

From download to published template in five clicks.

  1. Step 01

    Download the .sdt for the template you want.

  2. Step 02

    In Sliick Docs Template Library, click Import Template.

  3. Step 03

    Pick the file. The template lands as a Draft.

  4. Step 04

    Set a Test record, Validate, then Proof.

  5. Step 05

    Publish and drop the Generator on the record page.

The gallery

Six starters. Every one a standard-objects template.

01 · Base object · Opportunity
SDT

Sales Proposal

Cover proposal with line items and signature

Cover proposal generated from an Opportunity. Account info, deal summary, line items, totals, and a signature block ready for the customer.

  • Repeat over OpportunityLineItems
  • Aggregate totals (SUM, COUNT)
  • Signature block
Download sales-proposal.sdt ↓ View raw SDT
02 · Base object · Account
SDT

Account Statement

Account snapshot with addresses and recent Opportunities

Snapshot of an Account with billing and shipping addresses and a list of recent Opportunities. Ideal as a quarterly portfolio recap.

  • Billing + shipping addresses
  • Repeat over related Opportunities
  • 5-hop parent lookups
Download account-statement.sdt ↓ View raw SDT
03 · Base object · Contact
SDT

Welcome Letter

Personalised welcome letter for a new contact

Personalised welcome letter sent to a new Contact. Pulls salutation, account, and assigned owner so the letter is one click away from being sent.

  • Salutation handling
  • Owner traversal
  • Print-ready layout
Download welcome-letter.sdt ↓ View raw SDT
04 · Base object · Lead
SDT

Lead Follow-up

Post-first-contact follow-up summary

Follow-up summary sent to a Lead after first contact. Captures the conversation, next steps, and owner contact details.

  • Conditional content blocks
  • Owner contact details
  • Compact one-pager
Download lead-follow-up.sdt ↓ View raw SDT
05 · Base object · Case
SDT

Case Summary

Service-team case summary for the customer

Service-team summary of a Case for sharing with the customer. Subject, status, resolution notes, and contact information laid out for a quick read.

  • Status and priority surfacing
  • Contact traversal
  • Resolution notes section
Download case-summary.sdt ↓ View raw SDT
06 · Base object · Order
SDT

Order Confirmation

Customer-facing confirmation with line items

Customer-facing confirmation generated from an Order, including line items and totals. Uses OrderItemNumber and Description so it works without Product2.

  • Repeat over OrderItems
  • Order totals
  • OrderItemNumber + Description fallback
Download order-confirmation.sdt ↓ View raw SDT
What's in the box

What each file carries

  • · Template header (name, description, base object, default file-name pattern, default output mode)
  • · A single Draft version carrying the editor-state payload
  • · templateExport payload at schemaVersion 2
  • · Editor state nested under draft.editorState as a structured payload
What it doesn't carry

Scrubbed at export

  • · Test record IDs
  • · Auto-email recipient, from, and template IDs (wire those in your target org)
  • · Active release pointers (you re-publish in the target org)
  • · ContentVersion artifacts, audit rows, or generation history
Field choices worth knowing

A few opinionated decisions per template.

Owner traversal

Owner.Name and Owner.Email render blank when the record is owned by a queue rather than a user. The starters render blanks rather than failing.

Order line items

Uses OrderItems.OrderItemNumber and OrderItems.Description because OrderItem has no Name field. If your team populates Product2, switch to OrderItems.Product2.Name.

Opportunity line items

Uses OpportunityLineItems.Name, which surfaces the related product name automatically when the Opportunity has a price book attached.

Need something more bespoke?

We'll build the template for you.

If a starter is close but not quite right, or you have a workflow that needs a custom template, we'll author it against your real data and hand it back as a deployable .sdt file.

Talk to us → Back to Sliick Docs