What Are Templates?
Templates are reusable onboarding blueprints that define your customer journey from kickoff to go-live. They capture your proven processes and ensure every customer gets a consistent, high-quality experience.Why Templates Matter
Without templates, every CSM invents their own process. With templates:- ✅ Consistency - Every customer follows proven best practices
- ✅ Scalability - Onboard 10x customers without 10x headcount
- ✅ Knowledge capture - Institutional knowledge lives in templates, not CSM heads
- ✅ Continuous improvement - Update templates based on learnings, improve all future customers
- ✅ Predictability - Set realistic expectations with data-backed timelines
Think of templates as your “onboarding playbook” - they codify what works and eliminate what doesn’t.
Creating Your First Template
Step 1: Access Template Editor
- Navigate to Templates in the main menu
- Click “Create New Template”
- You’ll see the template configuration screen
Step 2: Configure Template Metadata
Fill in the template basics:| Field | Purpose | Example |
|---|---|---|
| Name | Internal template identifier | ”Standard SaaS Onboarding” |
| Description | What this template is for | ”For mid-market SaaS customers with typical setup needs” |
| Est. Duration | Total weeks | 8 weeks |
| Target Segment | Who this template suits | ”SMB, Mid-Market” |
Step 3: Add Milestones
Milestones are the phases of your onboarding journey. Common structures:- Simple (3-4 weeks)
- Standard (6-8 weeks)
- Enterprise (12+ weeks)
Best for: Self-serve products, simple setups
-
Kickoff (Week 1)
- Welcome email
- Get credentials
- Initial setup
-
Configuration (Week 2)
- Configure settings
- Import data
- Test functionality
-
Launch (Week 3)
- User training
- Go-live
- Post-launch check-in
- Click “Add Milestone” in the template editor
- Enter milestone name (e.g., “Kickoff”)
- Set sequence number (1, 2, 3…)
- Set estimated duration in days
- Add dual descriptions:
- “What we’re doing” - Internal team tasks
- “What you’re doing” - Customer responsibilities
Step 4: Add Actions to Milestones
Actions are the specific tasks within each milestone. For each action:- Click “Add Action” within a milestone
- Select action type (Send Email, Request Docs, Collect Info, etc.)
- Configure trigger rules (when does it execute?)
- Set action content (email body, form fields, etc.)
- Configure portal visibility (what customers see)
Action Configuration Fields
Basic Info
Basic Info
- Label: Short name (e.g., “Welcome Email”)
- Description: Internal notes about purpose
- Type: Send Email, Request Docs, Collect Info, Schedule Meeting, Slack Message
Trigger Configuration
Trigger Configuration
When should this action execute?
- Milestone Start (Immediate): As soon as milestone begins
- Milestone Start (Delayed): X hours after milestone starts
- Manual: CSM must manually trigger
Content Configuration
Content Configuration
Action type-specific content:Send Email:
- Subject line template
- Email body template
- Recipient configuration (to/cc/bcc)
- Variable placeholders (, etc.)
- Document types needed
- Optional vs required
- Instructions for customer
- Form field definitions
- Field types and validation
- Intro text and instructions
- Meeting type
- Suggested duration
- Attendees list
- Channel configuration
- Message template
- Formatting options
Portal Configuration
Portal Configuration
Customer portal visibility:
- Hidden: Only CSMs see this action
- Visible: Customers see it in their timeline
- Interactive: Customers can complete it (forms, docs)
- Display label (what customers see)
- Status visibility (completed, pending, etc.)
- Section grouping (organize related actions)
Step 5: Use Variables for Personalization
Thread supports dynamic variables that populate at execution time:{{company_name}}- Customer company{{account_name}}- Account display name{{primary_contact_name}}- Main point of contact{{primary_contact_email}}- Contact email{{csm_name}}- Assigned CSM full name{{csm_email}}- CSM email{{arr}}- Annual recurring revenue{{close_date}}- Deal close date{{organization_name}}- Your company name
Step 6: Save & Test Template
Before applying to real customers:- Click “Save Template”
- Create a test account
- Apply this template
- Walk through the entire flow
- Review AI-generated drafts
- Check customer portal view
- Iterate based on findings
Template Design Principles
1. Start Simple, Add Complexity
Don’t try to capture every edge case in v1. Good first template:- 3-5 milestones
- 2-4 actions per milestone
- Mix of emails, forms, and documents
- Standard timing (no complex delays)
- 10+ milestones (too granular)
- Complex conditional logic
- Custom actions for rare scenarios
- Overly detailed instructions
2. Think Dual Perspective
Every milestone should clearly articulate: CSM side (“What we’re doing”):- Technical setup steps
- Internal preparation tasks
- Behind-the-scenes work
- Quality checks
- Information they need to provide
- Decisions they need to make
- Actions they take in portal
- Expected time commitment
3. Use Delays Strategically
Don’t bombard customers with actions all at once. Good delay strategy:4. Make Actions Completable
Every action should have a clear completion criterion:- ✅ Email sent - Marked complete manually by CSM
- ✅ Form submitted - Auto-complete when customer submits
- ✅ Document uploaded - Auto-complete when files received
- ✅ Meeting held - Marked complete by CSM after call
5. Balance Automation and Human Touch
Use AI for efficiency, but keep human connection: Automate:- Welcome emails
- Status updates
- Reminder emails
- Progress notifications
- Standard form requests
- Kickoff calls
- Problem-solving discussions
- Executive business reviews
- Escalation handling
- Relationship building
Common Template Patterns
Welcome Sequence
When: Milestone 1 (Kickoff)Technical Setup Phase
When: Milestone 2-3Training & Enablement
When: Milestone 4-5Launch Checklist
When: Final milestoneTemplate Versioning
Thread uses immutable snapshots for templates:- When you apply a template to an account, the entire configuration is copied
- Changes to the template don’t affect existing accounts
- Each account keeps its original template version
- Scenario: Template Update
- Scenario: Bug Fix
You improve your template:
- Add a new action in Milestone 2
- Change email copy
- Adjust timing delays
- ✅ New accounts get updated template
- ✅ Existing accounts keep original template
- ✅ No mid-flight disruption
- ✅ Consistency maintained
If you need to update live accounts, you’ll need to manually edit actions in the Implementation Tab for each account.
Next Steps
Milestones & Phases
Deep dive into structuring milestones effectively
Action Types
Complete guide to all five action types
Best Practices
Learn from proven templates that drive results
Apply Templates
How to apply templates to customer accounts
