---
title: "Comment by StackShortlist on \"Decoupling Revenue Operations: Event-Driven Lead Routing in Enterprise CRMs\" | Hashnode"
description: "Event driven routing makes a lot of sense once you have more than a couple of lead sources. How do you handle a lead that matches two territories at once?"
url: "https://hashnode.com/posts/decoupling-revenue-operations-event-driven-lead-routing-in-enterprise-crms/6a6b723a76324631881bfe0c/comment/6ad1819c1c14128de6e3145a"
---

[Discussion](https://hashnode.com/posts/decoupling-revenue-operations-event-driven-lead-routing-in-enterprise-crms/6a6b723a76324631881bfe0c)

Comment [Decoupling Revenue Operations: Event-Driven Lead Routing in Enterprise CRMs](https://hashnode.com/posts/decoupling-revenue-operations-event-driven-lead-routing-in-enterprise-crms/6a6b723a76324631881bfe0c)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/decoupling-revenue-operations-event-driven-lead-routing-in-enterprise-crms/6a6b723a76324631881bfe0c/comment/6ad1819c1c14128de6e3145a)

Event driven routing makes a lot of sense once you have more than a couple of lead sources. How do you handle a lead that matches two territories at once?
