Lead sources
Every ping, one stream
Facebook, Google, Gmail, Outlook, OEM ADF, website forms, and marketplace feeds land as one buyer not a morning export.
50% off your first month for new dealerships
Lead sources in. CRM and DMS out. Phone, SMS, and calendar in the middle so a marketplace ping becomes a held visit without a weekend import project.
Connected stack
Source
Facebook in
Thread
Owner assigned
CRM
Lightspeed
LeadStreamIQ does not replace the tools on the floor. It captures the ping, owns the conversation, and writes the visit back.
Lead sources
Facebook, Google, Gmail, Outlook, OEM ADF, website forms, and marketplace feeds land as one buyer not a morning export.
LeadStreamIQ
AI replies on SMS. A specialist can jump in. Calendar Booking puts Saturday on the board and cadence stops.
CRM & DMS
Lightspeed, Aimbase, DP360, BoatCrazy, ADF Email, HubSpot, or a custom API per rooftop, with source tags intact.
Filter the catalog, then open any card for how it connects on the floor.
Meta leads land in the stream the moment they submit not in a morning export.
Learn morePaid and local inquiries join the same queue as marketplace and Facebook.
Learn moreDealer-site forms post into LeadStreamIQ instead of a personal mailbox.
Learn moreOEM and marketplace ADF payloads parse into clean buyer records.
Learn moreLead mailboxes in Gmail feed Aggregator instead of a buried Promotions tab.
Learn moreMicrosoft 365 lead mailboxes connect the same way Gmail does.
Learn moreFactory and program leads join dealer-site and marketplace inquiries.
Learn moreBoatCrazy, Boat Trader, YachtWorld, RV Trader, and similar listing pings in one queue.
Learn moreOwner, transcript, and held visit write back to Lightspeed per rooftop.
Learn moreQualified leads and visit context land in Aimbase not a CSV.
Learn moreDP360 stays the desk CRM. LeadStreamIQ is the intake and follow-up layer.
Learn moreMarine CRM and listing traffic capture in, visit written back.
Learn moreWhen the stack still wants ADF out, we deliver a clean payload not a messy forward.
Learn moreWhen HubSpot is in the stack, qualified leads and next steps can write back.
Learn moreREST and webhooks when Lightspeed or Aimbase is not the destination.
Learn moreAI SMS on the original number. Human takeover anytime.
Learn moreInbound calls get a record, a transcript path, and an owner not a voicemail pile.
Learn moreWalkthroughs and test rides land on live calendars. Cadence turns off.
Learn moreSite chat that qualifies and captures then joins the same owner as SMS.
Learn moreOne owner. Shared history. Handoffs that carry the transcript.
Learn moreYou do not need a custom science project if leads already hit a mailbox, ADF, or an API.
Gmail, Outlook, and dedicated ADF inboxes parse, de-dupe, assign. The Promotions tab stops being the CRM.
OpenOEM payloads in. Custom webhooks out when your CRM is not Lightspeed, Aimbase, DP360, or BoatCrazy.
OpenQualified buyer, owner, transcript, and held slot land in the system the desk already opens.
OpenMailbox parse, ADF, and a custom API cover most dealer systems. If yours is not listed, we map it on a demo.
No. LeadStreamIQ sits in front of the system the floor already runs. Qualified buyers, transcripts, and held visits write back to Lightspeed, Aimbase, DP360, BoatCrazy, ADF Email, or your own endpoint.
Most rooftops start with a connected Gmail or Outlook mailbox, ADF/XML parse, and website form webhooks. Facebook Lead Ads and Google inquiries join the same de-duplicated stream.
Open REST, webhooks, and outbound ADF cover one-off stacks. Bring the tool name and how leads land today we will tell you on a demo whether it is mailbox parse, a destination, or a short mapping project.
Sources and phones are usually live in 24–48 hours after go-ahead. CRM write-back follows the destination you already use. We walk the map on the demo so you are not guessing in a spreadsheet.
Yes. Intake, assignment, and write-back are per rooftop. Hudson does not eat the south lot. Group operators still see one stream.
Twilio SMS, call tracking, and calendar booking live on the original thread. AI drafts the first reply. A specialist can jump in. When the visit is held, cadence stops.
We will walk the map on your rooftops usually live in 24–48 hours after go-ahead.