Product
...
Triggers
Enquiry Stage Updated
7 min
 this document provides a comprehensive guide to one of the seven sources used within the flow builder, detailing their functionality, configuration options, and potential applications each source is paired with practical use cases, best practices, and frequently asked questions to enhance your understanding and enable efficient implementation the sources form the backbone of automated workflows, allowing for dynamic triggers and streamlined processes in communication and enquiry management flow type 7 enquiry stage updated description triggered when the stage of an enquiry is updated in the pipeline trigger conditions stage specify the stage being updated (e g , qualified, booked) pipeline define the pipeline associated with the enquiry practical use cases stage notifications notify the user when their enquiry moves to the next stage task automation assign tasks to team members based on the updated stage conditional workflows trigger different actions based on the new stage best practices keep users informed at critical stages of their enquiry automate repetitive tasks like follow ups and reminders use conditional logic to streamline workflows faqs can i trigger different flows for each pipeline stage? yes, you can set up individual workflows for each stage to deliver tailored responses or automate specific tasks why is this trigger useful? it helps you automate actions based on enquiry progress, ensuring that no stage transition goes unnoticed what if a user skips a stage in the pipeline? flows will only be triggered when the specific stage defined in the trigger conditions is reached skipped stages will not activate their corresponding flows can i use this trigger for internal team alerts? yes you can configure it to notify team members via internal messages or assign tasks when an enquiry hits a particular stage is it possible to delay actions after a stage update? yes, you can use βwait actionβ before executing specific steps like sending notifications or assigning tasks how do i prevent duplicate workflows if a stage is updated repeatedly? add logic checks (e g , tags or custom fields) to ensure the flow only runs once per stage transition can i include multiple pipelines in one trigger? no, each pipeline should have its own separate trigger for updating the stages how do i log stage changes in the system? you can track the stage changes log in the enquires report module are there reports to track how often stage changes occur? yes, use the reporting module to analyze enquiry flow and track the frequency and timing of stage transitions can it send updates to customers? yes for example, when an enquiry moves to in progress , you can send a message confirming that an agent is handling their request