Lifecycle Stages
Learn how to set up and use lifecycle stages to track your contacts through the customer journey.
What are Lifecycle Stages?
Lifecycle stages let you track where each contact is in your customer journey. Think of it as a visual sales pipeline built directly into your messaging platform. Every contact can be assigned to a stage, giving your team instant visibility into their status.
Getting Started
Navigate to Workspace Settings → Lifecycle in the sidebar. If you haven't created any stages yet, you'll see an empty state with two options:
- Use defaults — Creates 5 common stages: New Lead, Hot Lead, Qualified, Customer, and Churned
- Add Stage — Create your own custom stages from scratch
Creating a Stage
Click "Add Stage" to open the creation form. Fill in:
- Name — The name of the stage (e.g., "New Lead", "Customer")
- Description — A brief explanation of what this stage means
- Color — Pick a color for visual identification in the pipeline
- Sort order — Controls the position in the pipeline (lower = earlier)
- Default stage — Toggle on to automatically assign new contacts to this stage
Click "Save changes" to create the stage.
Pipeline Overview
Once you have active stages, a visual pipeline is shown at the top of the page. Each stage displays its name, color, and the number of contacts currently in that stage. A star icon indicates the default stage.
Managing Stages
For each stage, you can:
- Edit (pencil icon) — Update name, color, description, or settings
- Set as default (star icon) — Make this the default stage for new contacts
- Archive (archive icon) — Hide from active list without deleting
- Delete (trash icon) — Permanently remove. Contacts in this stage will be unassigned.
Archived stages can be restored at any time from the "Archived Stages" section.
How Contacts Move Through Stages
Contacts can be moved between stages in two ways:
- Manually — Change a contact's lifecycle stage from the contact details panel
- Via automations — Set up automations to automatically move contacts when certain events occur (e.g., payment received → Customer)
Tips
- Only one stage can be the default at a time
- Keep your pipeline simple — 4 to 6 stages is usually ideal
- Use descriptive names so all team members understand what each stage means