Route inbound CRE leads to the right broker instantly
When a new lead arrives by email, WebRun reads the inquiry, extracts the property type, deal size, and geography, creates the contact in Buildout, assigns it to the right broker based on your routing rules, and posts an alert to Slack so no lead sits idle.
- No credit card
- Under $0.01 per run
- Cancel anytime
How can I automatically route inbound CRE leads to the right broker?
WebRun monitors your leasing inbox, parses each new inquiry for property type, deal size, and geography, creates the contact in Buildout CRM, assigns it to the right broker by your routing rules, and posts a lead card in Slack, so every inbound lead is routed within minutes.
- Every inbound lead is routed to the right broker within minutes, not hours
- No inquiry sits unassigned in a shared inbox overnight
- Duplicate contacts are caught before they pollute the Buildout CRM
Built for commercial real estate brokers · CRE brokerage teams · leasing agents · tenant rep brokers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.buildout.comin a real browser with your saved login - no setup, no API keys. -
1
Gmail - detect and parse new inquiry
WebRun opens Gmail to detect and parse new inquiry. - Monitor the shared leasing inbox for new listing inquiries and tenant leads
- Extract the property type, deal size, location, and contact details from the email
- Flag the lead tier based on deal size thresholds you define
Done when Every new inquiry has been parsed and a lead tier assigned.
-
2
Buildout - create contact and assign broker
WebRun opens Buildout to create contact and assign broker. - Open Buildout CRM and check for a duplicate contact using email and company name
- Create a new contact record with the parsed details if no duplicate is found
- Assign the lead to the broker whose territory or specialty matches the property type and market
- Log the source, tier, and assignment timestamp in the deal notes
Done when The lead is created and assigned in Buildout with full context logged.
-
3
Slack - alert the assigned broker
WebRun opens Slack to alert the assigned broker. - Post a concise lead card to the #new-leads Slack channel naming the assigned broker
- Include the property type, deal size, and inquiry source in the card
- At-mention the assigned broker so they see the alert immediately
Done when The assigned broker has a Slack alert with the lead summary.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it reply to the prospect on my behalf?
No. WebRun routes the lead internally and alerts your broker in Slack. Any reply to the prospect is drafted for your review first, never sent automatically.
How does it know which broker to assign?
You define routing rules by property type, market, and deal size. WebRun reads those rules each time and assigns accordingly, flagging any lead that does not match a rule for manual review.
What if a lead already exists in Buildout?
WebRun checks for a duplicate by email and company name before creating a record. Duplicates are flagged in Slack instead of creating a second contact.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.