Enquiry Status Updated

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 8 enquiry status updated description triggered when the status of an enquiry is updated (e g , won, lost) trigger conditions status specify the updated status pipeline define the pipeline where the status update occurs practical use cases success notification notify the user when their enquiry is successfully resolved loss analysis trigger workflows to analyze reasons for lost enquiries pipeline management automate pipeline updates based on the status best practices regularly review and update status categories use automation to ensure consistent pipeline updates analyze data to identify trends and improve processes faqs can i use this trigger to send a final summary to the customer? yes, you can create a follow up flow to send a summary message, invoice, or satisfaction survey when an enquiry reaches a final status like “won” or “lost ” how do i track the reasons for lost enquiries? use tags or fields to document reasons and generate reports for analysis how do i filter workflows for specific service types? use conditional logic based on enquiry fields, tags, or source pipelines to tailor flows for different services is it possible to trigger a status update from a customer action (like a form submission)? yes if the form submission updates the enquiry’s status, the linked flow will be triggered automatically can i run internal surveys after an enquiry is marked as “lost”? yes, you can trigger internal review forms or surveys to understand what led to the loss and collect insights from your team what happens if a status is set incorrectly? if the wrong status is set, the flow will still run you should build validation into your team’s processes or use automation checks if needed how can i prevent duplicate follow ups for status changes? use tags or custom fields as flags to mark enquiries that have already received a follow up message can i create a report based on status change flows? yes, you can use the reporting module to analyze how many enquiries move through each status and evaluate performance over time how is this different from stage updated? stages track progress in a pipeline (e g , new, follow up, escalated), while status indicates the overall state of the enquiry (active, waiting, or finished) why is this trigger useful? it ensures that important actions happen automatically whenever an enquiry’s status changes, improving response times and follow ups