--- title: "Lead Orchestration and Branching" slug: "lead-orchestration-and-branching" updated: 2026-08-24T10:06:31Z published: 2026-08-24T10:06:31Z canonical: "documents.revsure.ai/lead-orchestration-and-branching" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revsure.ai/llms.txt > Use this file to discover all available pages before exploring further. # Lead Orchestration and Branching ## Overview RevSure Lead Orchestration helps teams automatically decide what should happen next when a lead or buying signal enters the system. Instead of treating every lead the same way, RevSure lets you create different workflow paths based on real-time events, lead attributes, account context, engagement signals, intent data, and any other available RevSure data. With branching, teams can define conditions such as: - Is this lead a good ICP fit? - Is the title relevant? - Has the account shown high intent? - Is there an open opportunity? - Is the lead from a target account? - Is key data missing? - Should this lead go to sales, nurture, enrichment, or review? Each branch can trigger its own set of actions, such as creating a lead, enriching the record, sending a Slack alert, updating CRM fields, routing to a rep, enrolling in nurture, or triggering another workflow. ![Flowchart illustrating the RevSure Module process for lead prioritization and email notifications.](https://cdn.document360.io/1ba0d15e-f1ca-43db-aba7-8e6b7d8766f9/Images/Documentation/Screenshot 2026-06-24 at 3.00.20 PM.png) --- ## What You Can Do With RevSure Lead Orchestration, you can: - Create workflows for new and existing leads - Branch workflows based on real-time event conditions - Use any RevSure attributes, dimensions, scores, or signals as conditions - Create new leads when they do not already exist - Enrich leads with additional company, contact, and account context - Use enriched data to decide which path the lead should follow - Route leads to the right team, rep, queue, or system - Trigger different actions for different types of leads - Send alerts to Slack or other connected systems - Update CRM or marketing automation records - Send low-priority leads to nurture or review --- ## How It Works A lead orchestration workflow is built using nodes inside RevSure Agent Builder. A simple workflow may look like this: 1. A lead or event enters RevSure. 2. RevSure checks whether the lead already exists. 3. If needed, RevSure creates the lead. 4. RevSure enriches the lead with additional context. 5. RevSure evaluates the lead using selected conditions. 6. The workflow branches based on the matching condition. 7. Each branch runs its own actions. Example: A new website form fill comes in. RevSure can: - Create or update the lead - Enrich the lead with title, company, industry, and account data - Check ICP fit, title, intent, and engagement - Route high-fit leads to sales - Send medium-fit leads to nurture - Send incomplete leads to enrichment or review - Suppress low-fit leads from sales handoff --- ## Branching Logic Branching allows a workflow to split into different paths. Each branch has a condition that determines when it should run. Example branches: ### Branch 1: High-Intent ICP Lead Condition: - ICP Score is high - Title matches target persona - Account has strong engagement Actions: - Send Slack alert to the assigned rep - Create CRM task - Update lead status - Generate follow-up context --- ### Branch 2: Existing Opportunity Lead Condition: - Lead belongs to an account with an open opportunity Actions: - Notify opportunity owner - Add activity note to CRM - Create follow-up task --- ### Branch 3: Enrichment Needed Condition: - Job title is missing - Company name is missing - Account match is missing Actions: - Run enrichment - Update the lead record - Send to review if enrichment fails --- ### Branch 4: Marketing Nurture Condition: - Lead is relevant but not sales-ready Actions: - Add to nurture list - Update lifecycle stage - Sync to marketing automation --- ### Default Branch If no other condition matches, the lead follows the default branch. The default branch can be used to: - Send the lead to review - Add the lead to a general nurture program - Stop the workflow - Notify Marketing Ops --- ## Using Real-Time Event Conditions RevSure can trigger workflows based on real-time events. Examples of real-time events include: - Form submission - Demo request - Pricing page visit - Website activity spike - Content download - Webinar registration or attendance - Account intent increase - Lead created in CRM - Contact updated in CRM - Campaign engagement - Product usage signal These events can be used to start a workflow and decide which branch the lead should follow. Example: If a lead submits a demo request and belongs to a high-fit account, RevSure can immediately route the lead to sales and send a Slack alert. If the same lead has missing company data, RevSure can first enrich the record before routing it. --- ## Creating and Enriching New Leads For new leads, RevSure can help create and prepare the record before any routing or branching decision happens. A new lead workflow can include: 1. Detect new lead or event 2. Create lead in CRM or connected system 3. Match lead to account 4. Enrich missing fields 5. Add context and dimensions 6. Evaluate branch conditions 7. Execute the right downstream action This helps teams avoid routing incomplete or low-context leads to sales. Instead, RevSure can enrich the lead first and then decide the right next action. --- ## Example Workflow: ICP Lead Routing to Slack A Marketing Ops user wants to route ICP leads to the right rep on Slack. Workflow: 1. Trigger: New lead created or form submitted 2. Create or update lead 3. Enrich lead with title, company, and account data 4. Access RevSure lead prioritization data 5. Branch based on ICP title criteria Example branches: ### Marketing Leader Branch Condition: - Lead title contains “Marketing” - ICP fit is high Action: - Send Slack alert to the marketing-focused sales rep ### RevOps Leader Branch Condition: - Lead title contains “Revenue Operations” - ICP fit is high Action: - Send Slack alert to the RevOps-focused sales rep ### Default Branch Condition: - No ICP title match Action: - Send to review or nurture Example Slack alert: “New ICP lead routed to you. This lead matches the target title criteria, belongs to a high-fit account, and has recent engagement. Recommended next step: follow up with a relevant message based on their role and account context.” --- ## Common Use Cases ### 1. Inbound Demo Request Routing Route high-intent demo requests to the right sales rep in real time. ### 2. ICP Lead Routing Identify leads with target titles, industries, account fit, and intent, then send them to the correct rep or workflow. ### 3. Enrichment Before Handoff Create and enrich new leads before deciding whether they should go to sales, nurture, or review. ### 4. Existing Opportunity Alerts Notify opportunity owners when new leads or contacts from their accounts show engagement. ### 5. Nurture Segmentation Send leads to different nurture paths based on persona, intent, source, or account stage. ### 6. Marketing Ops Review Send leads that do not meet clear conditions to a manual review branch.