LeanData BookIt is the scheduling layer for revenue teams that route on LeanData, and roughly half of Breakout's customers run it. When a visitor qualifies in a Breakout conversation and is ready to book, Breakout hands that visitor to BookIt— so the rep, the calendar, and the meeting ownership are all determined by the LeanData routing graph.
How it works
A visitor engages the Breakout agent. The agent qualifies them conversationally, capturing the signals your BookIt routing graph needs — company, region, product interest, segment, or whatever your graph branches on. When the visitor is ready to book, Breakout passes those values to LeanData through a chat trigger node on your BookIt for Forms graph.
LeanData's matching engine resolves the visitor against your CRM, runs your routing logic, and returns a booking experience for the correct rep. Breakout renders that inside the conversation. The visitor picks a time, BookIt creates the meeting, and it's written back to Salesforce with ownership and attribution.
Because routing happens in LeanData, the conversation inherits everything your graph already does — lead-to-account matching, territory rules, account ownership lookup, round robin pools, prior-demo-owner logic, and fallback paths when the primary rep has no availability.
What Breakout configures for you
Everything on the Breakout side is handled during onboarding. Breakout sets up the visitor fields that carry BookIt data through the conversation, builds the field-mapping string that pairs each captured signal to its counterpart in your trigger node, wires the routing call into your playbooks, and sets the timing so the routed calendar is ready before the agent presents it. Breakout also configures which booking experience the visitor sees — a routed booking link delivered in the conversation, a popup calendar over the current page, or a branded landing page you control — based on your preference.
What you set in Breakout is configuring your forms: Any signal your BookIt graph branches on has to actually be collected in the conversation, which means the corresponding field needs to exist on the Breakout form. If your graph routes on company size and the form doesn't capture it, LeanData can't route on that. Those fields can be configured in the form that you are using in chat.
What your team configures in LeanData
In your LeanData dashboard, open BookIt for Forms > FlowBuilder and go to your deployed graph. Drag a New Chat Prospect Trigger node onto the canvas. Inside it, map the form field API names to the variables your graph uses, then direct the trigger node's insert edge to the next step in your routing logic. From there, the conversation enters the same graph your webforms already use, you're just adding an entry point.
If different conversations should route differently — a pricing-page conversation versus a support conversation — create a separate trigger node for each and tell Breakout which node name goes with which playbook.
Two values need to come back to Breakout so we can finish our side: your BookIt Org ID, found under BookIt > Settings > General, and the name of each trigger node you create.
The field names in your trigger node are the contract between the two systems. They need to match exactly what Breakout sends, we ensure that's set up correctly during configuration.
Records, ownership, and avoiding double routing
BookIt creates or updates the Lead or Contact as part of the routing process and stamps the BookIt Log ID onto the record. That ID links the conversation, the booking, and the CRM record together, and it's what your Lead Routing graph should check.
This matters because your BookIt for Forms graph and your Lead Routing graph are separate graphs. They coordinate through fields on the shared Salesforce record, not through implicit knowledge of each other. If your lead routing graph doesn't check whether a record already has a BookIt Log ID or a recent booking timestamp, it can re-route a record BookIt already assigned.
Teams already running BookIt for Forms will have built this check, and Breakout-originated bookings flow through the same path. Teams standing up BookIt for the first time should build that check as part of implementation, for chat and webforms alike.
Meetings booked through Breakout appear in the BookIt for Forms audit logs alongside every other BookIt booking.