LeanData is the routing and scheduling backbone for a large share of B2B revenue teams — roughly half of Breakout's customers run it. When a team adds an AI agent to a site that already routes through LeanData, it creates a new challenge: a chat conversation can now produce a meeting, putting two systems in a position to decide who owns the lead and whose calendar the prospect sees. Left unresolved, that produces an undesirable outcome — conflicting owners.
Breakout is designed to coexist with LeanData. There are two architectures for doing this, and they differ on which system holds routing authority for meetings that originate in chat. Here's how each works, what conflict avoidance actually depends on, and how to decide which fits your environment.
Chat-native booking with a routing handback
This is the model Breakout runs in production today with customers on LeanData, and the one most teams should start with.
When a visitor engages the chat agent, Breakout qualifies them conversationally and, at the point they're ready to book, determines the assigned rep using its own routing logic — account ownership lookup and round robin — then shows live availability pulled from that rep's connected calendar. The visitor books, and Breakout creates the calendar event directly and writes the booking to the CRM record.
The critical step happens at the moment of booking. Breakout stamps a value into a CRM field (contact or lead, depending on what you use), which LeanData then reads to track what routing action has been taken on a record. LeanData's workflows check that field before acting; seeing the Breakout stamp, they treat the record as handled and don't re-route or re-assign it. That single field is the conflict-avoidance mechanism, and it works cleanly because LeanData is built to run off account, lead, and contact attributes. Everything else about your existing LeanData setup is untouched — it routes everything else exactly as it does today.
Setup is a one-time field-mapping exercise: identifying the specific field LeanData monitors in your instance, granting Breakout write access to it, and mirroring your lead routing logic in Breakout workflows. It only works for LeanData workflows that check that specific field to read routing status.
The tradeoff is that LeanData's matching and round-robin engine isn't involved in chat-originated assignment. For teams whose routing is ownership lookup plus round robin, there's no real loss — Breakout expresses the same logic. Since chat generates high-intent hand-raisers, the routing logic needed is generally simpler anyway, since the goal is getting a rep in front of the visitor quickly.
LeanData-governed routing
The second architecture makes LeanData the single routing authority across every channel, chat included.
Under this model, Breakout's agent still qualifies the visitor conversationally, but instead of booking on its own, it captures the fields LeanData's routing graph needs — company, region, product interest, and similar signals — as chat-native fields and passes them to LeanData at the point of booking. This happens either through BookIt's real-time API, which checks availability, applies routing rules, and confirms the meeting programmatically, or through the chat-to-FlowBuilder trigger pattern LeanData provides for chat tools. LeanData determines the rep and returns a booking link or live availability, which Breakout renders inside the conversation. The visitor books, BookIt creates the calendar event, and it's written back to the CRM with attribution intact. Full setup steps are in Breakout's help center.
This model doesn't require Breakout to set anything in the CRM for LeanData to read. Note that the BookIt Routing Graph is different from the Lead Routing Graph — you're still running two separate graphs, one for lead routing in the CRM and one for leads coming through BookIt. LeanData resolves repeat-routing the same way here too, by stamping a field in the CRM, so conflict resolution ends up working the same in both scenarios: whether Breakout is routing chat leads directly, or BookIt is routing them.
Choosing between them
The choice largely comes down to whether you've purchased BookIt alongside Lead Routing. If you have, the second model is the way to go, since it makes use of what you're already paying for — as long as the routing logic you'd use for direct BookIt meetings matches the logic you'd use for leads coming through chat. If you haven't, you're better off with Breakout's native routing, writing back to the CRM to tell LeanData not to re-route that lead.
Either way, you'll need to configure field mapping in the CRM and settings in LeanData to avoid routing conflicts — the effort is similar for both, so the better tiebreaker is which platform makes it easier for your team to configure and maintain that routing logic.
