Ability to require a reason for lifecycle | Voters

Ability to require a reason for lifecycle

closed

Marwan Yaba

When a lead lifecycle changes from new lead to junk/cold lead, the system requests a reason why this change to that state, along with the ability to select prefilled categories with a simple description, and this event is available to automate it and route it to your desired CRM.

January 20, 2026

Nabilah Binti Salleh

marked this post as

closed

Nabilah Binti Salleh

Hi Marwan Yaba, thank you for your request. To better understand the use case, could you share a few examples of:

When and why your team would require a reason for changing a lead’s lifecycle (e.g. operational review, sales coaching, CRM reporting)?
How this reason would be used downstream - for example, in automations, CRM workflows, or analytics?

This will help us ensure the feature is designed to support the right workflows.

Nabilah Binti Salleh

Or Marwan Yaba - you can try setting up Closed Lost Stages. You can add multiple lost stages (e.g. no urgency, price too high, no response), so that your team can select accordingly.