When creating templates in Hoops, there are three important naming fields:
Document Type
Template Name
Description
Understanding the difference between these fields is important, especially when managing many templates.
Document Type (Customer-Facing)
The Document Type is what your customer sees.
Examples:
Quote
Estimate
Proposal
Invoice
This text appears directly on the document itself and helps define the type of experience the customer is receiving.
Template Name (Internal)
The Template Name is your internal identifier for the template.
This is how your team distinguishes between templates that may share the same customer-facing document type.
For example, you may have several templates where the document type is simply:
Quote
But internally, the templates could be:
Quote – Accept & Pay
Quote – 30 Day Terms
Quote – Schools
Quote – Bank Transfer Only
The customer may see “Quote” on all of them, while your team sees the specific workflow version internally.
Description (Internal Notes)
The Description field is for internal guidance.
Use this to explain:
When the template should be used
Which workflow it supports
Any important setup details for your team
Examples:
“Use for schools and government customers”
“Large-value quotes without online payment”
“Retail-style quote with rolled-up pricing”
Example Workflow
You might create:
Document Type:
QuoteTemplate Name:
Quote – Accept OnlyDescription:
Use for large-value quotes paid via bank transfer
This allows:
Customers to receive a clean “Quote” document
Your team to clearly identify the intended workflow internally
Viewing Templates
When selecting templates from the SalesBoard:
The Document Type appears as the customer-facing label (Pink Highlight)
The Template Name appears as your internal reference (Purple Highlight)
💡 Pro Tip
Most advanced Hoops users create many templates with the same Document Type.
The power comes from:
Different workflows
Different payment settings
Different pricing structures
Different customer experiences
all hidden behind a clean, consistent customer-facing document name.
Template Use Cases & Ideas
Check out this doc for some useful ideas and recommended configurations for different templates.