Contract Trigger Follow-up Settings

Automatic follow-up actions triggered by contract closure with time delays

HubSpotWorkflowFollow-upOnboardingDealTime Delay
3 min read

About This Article

"I want to check utilization status 30 days after contract" "I want to send follow-up emails 7 days after service start"

HubSpot workflows can automatically execute follow-up actions based on deal closures or CRM property changes with specified time delays.

Contract Trigger Basics

Trigger Conditions

Delay Action Types

Implementation Patterns

Pattern 1: Onboarding Sequence

Onboarding Sequence
Trigger: Deal stage changed to Closed Won

Start sequence on contract closure

Immediately: Send welcome email

Welcome message + setup guide

3 days later
Email: Initial setup check

"Have you completed the initial setup?"

7 days later
Email: Tips for success

Best practices and tips

30 days later
Task: 1-month follow-up call

Create task for account manager

Pattern 2: Contract Renewal Reminder

Contract Renewal Reminder
Trigger: 90 days before contract end date

Based on contract end date property

Internal notification

Notify account manager

60 days before
Customer email: Renewal notice

"Your contract renewal is approaching"

30 days before
Task: Renewal confirmation call

Create task for rep

Pattern 3: Usage-Based Follow-up

Usage-Based Follow-up
Trigger: 14 days after contract start

2 weeks post-contract

Branch: Login count?

Branch based on login activity

Result

5+ logins → Thank you + advanced features / 1-4 logins → Check-in + support info / 0 logins → Urgent task for rep

Configuration Steps

1. Prepare Date Properties

Date properties are needed as the basis for time-based follow-ups:

  • Contract start date
  • Service start date
  • Contract end date
  • First login date

2. Create Workflow

3. Set Branch Conditions

Use branches to personalize follow-up content based on product, customer attributes, or usage.

Important Notes

Re-enrollment Settings

Configure whether to re-run the workflow when the same contact contracts again.

Exclusion Conditions

Exclude cases where follow-up is unnecessary:

  • Contract cancelled
  • Currently in support interaction
  • Email unsubscribed

Business Days Consideration

Configure delivery timing for business hours using day-of-week and time-of-day delays.

Summary

  • Prepare date properties: Record dates as follow-up basis
  • Design staged sequences: Follow up gradually, not all at once
  • Branch by usage: Personalized, not one-size-fits-all follow-up
  • Set exclusion conditions: Prevent unnecessary follow-ups

Appropriate post-contract follow-up improves customer retention and builds long-term relationships.