Skip to main content

🧲 Leads Pipeline Workflow

Learn what triggers the Leads pipelines and what are the actions of each workflow.

Written by Tommy

Appointment Pipeline Workflow

  1. Initiation of Workflow

    • When an appointment is booked for a contact on the "appointments"calendar

  2. Actions Taken when Workflow is Triggered

    • Remove any existing opportunities on the contact

    • Add an appointment set tag

    • Remove bot follow-up tags

    • Mark as read

    • Remove from all workflows

    • Move into the appointments pipeline

    • sends multiple notifications leading up to the appointment to the user

Bot Booking Error Pipeline Workflow

  1. Initiation of Workflow

    • An ai booking error tag is added to the contact when the Bot is unable to book an appointment. Adding the tag to the contact initiates the workflow

  2. Actions Taken when Workflow is Triggered

    • Remove any existing opportunities on the contact

    • Remove bot follow-up tags

    • Mark as read

    • Remove from all workflows

    • Move into the bot booking error pipeline

    • send internal notification of the booking error to the user

Bot Responded Pipeline Workflow

  1. Initiation of Workflow

    • when ai responded or bot responded tag is added to contact

  2. Actions Taken when Workflow is Triggered

    • Remove any existing opportunities on the contact

    • Mark as read

    • Move into the bot responded pipelineBot

Website Lead(opt-in) Pipeline Workflow

  1. Initiation of Workflow

    • Opt-in form needs to be selected within the trigger

    • when a contact opts-in on user's website

  2. Actions Taken when Workflow is Triggered

    • Move into website leads opt-in pipeline

    • sends internal notification to user notifying them of a new opt-in lead

Bot Unsure Pipeline Workflow

  1. Initiation of Workflow

    • Bot unsure selected by the Bot while working it's goals

    • contacts is missing a name on file

  2. Actions Taken when Workflow is Triggered

    • Move into user not assigned pipeline

    • contact removed from pipeline manually by user, but contact will have to have a name added to not re appear in the pipeline.

Deceased Pipeline Workflow

  1. Initiation of Workflow

    • User selects deceased under the dispositions section

  2. Actions Taken when Workflow is Triggered

    • Remove any existing opportunities on the contact

    • Add deceased tag

    • Remove from all workflows

    • Move to deceased pipeline

    • Mark as read

Listed With Realtor Pipeline Workflow

  1. Initiation of Workflow

    • User selects listed with realtor under the dispositions section

    • Listed with realtor selected by the Bot while working it's goals

  2. Actions Taken when Workflow is Triggered

    • Remove any existing opportunities on the contact

    • Add a listed with realtor tag

    • Remove bot follow-up tags

    • Mark as read

    • Remove from all workflows

    • Move into the listed with realtor pipeline

    • Turns Bot off

    • Wait for 2 months

    • After 2 month wait moves to the Bot 1 month follow up workflow

Asking Too Much Pipeline Workflow

  1. Initiation of Workflow

    • User selects asking too much under the dispositions section

    • Asking too much selected by the Bot while working it's goals

  2. Actions Taken when Workflow is Triggered

    • Remove any existing opportunities on the contact

    • Add a asking too much tag

    • Remove bot follow-up tags

    • Mark as read

    • Remove from all workflows

    • Move into the asking too much pipeline

    • Turns Bot off

    • wait 7 days

    • Added to Bot - 3 month follow up

Did this answer your question?