Lifecycle: Support for Multiple Lifecycles for Different Teams
Eduardo Escobedo
Desired outcome:
We would love to have the ability to define and manage multiple lifecycles, that is useful for teams with diverse processes.
This feature would allow different teams to utilize lifecycles tailored to their specific workflows and needs.
- The ability to create and customize different life cycles for various teams.
- A way for teams to switch between lifecycles depending on the situation or context.
- Custom stages, automations, and triggers for each lifecycle.
- Admins can monitor and track performance across all active lifecycles.
Benefits:
- Streamlines operations for specialized teams.
- Improves flexibility and adaptability to business needs.
- Enhances both internal workflows and customer experience.
Use Case Examples:
- Sales Team: A lifecycle to manage lead nurturing, deal stages, and closing opportunities.
- Post-Sales Team: A lifecycle for onboarding, escalations, and tracking delivery milestones for customers.
- Customer Service Team: A lifecycle to focus on ticket resolution, SLA adherence, and proactive follow-ups.
N
Nabilah Binti Salleh
Merged in a post:
Lifecycle: Support Team-Specific Lifecycles
O
Olman Castro
Business Problem:
Currently, the lifecycle feature applies globally across all teams in a workspace. However, businesses often have multiple teams providing different services, such as Customer Service and Sales, each requiring its own lifecycle stages. The inability to assign separate lifecycles to different teams makes it difficult to track progress and manage workflows effectively.
Desired Outcome:
Introduce the ability to define and assign team-specific lifecycles within a workspace. This enhancement should:
- Allow each team (e.g., Sales, Customer Service) to have its own unique lifecycle stages.
- Enable better tracking and reporting for different workflows based on team functions.
- Improve visibility into how contacts progress through each team’s specific lifecycle.