Help center

How can we help?

Type a keyword SMS, CRM, booking, rooftop then jump to the article. Or pick a topic below and read it on this page.

Search this page
Guides by topic
Same stack you run

matches on this page

No matches. Try SMS, CRM, booking, or rooftop.

01 · Getting started

Getting started

LeadStreamIQ sits in front of the floor. Mailboxes, tracking numbers, and forms land in one stream. A specialist owns the thread. Held visits write back.

What you connect on day one

Facebook, Google, ADF, OEM programs, marketplace feeds, Gmail, Outlook, and site forms forward into LeadStreamIQ not a personal phone. Tracking numbers cover inbound calls. You do not rip out the phone system or the CRM.

How go-live works

Sources and phones are usually live in 24–48 hours after go-ahead. Onboarding is included. CRM write-back follows the destination you already use: Lightspeed, Aimbase, DP360, BoatCrazy, ADF Email, or a custom API.

What the floor sees first

Team Inbox is the single stream. One owner per rooftop Hudson does not eat the south lot. The closer opens the CRM with the transcript, not a cold sheet from Unread.

Multi-location groups

Intake, assignment, and write-back are per rooftop. Group operators still see one stream. Route rules keep the south lot’s pings on the south lot’s specialist.

02 · AI answering

AI answering

The first reply is on the buyer’s channel. Inventory answers come from the lot you actually have. A specialist can take over from Team Inbox at any time.

Channels the AI covers

SMS on Twilio numbers, inbound call tracking, email parse (Gmail, Outlook, ADF), website forms, Facebook Lead Ads, Google inquiries, and marketplace feeds. Site chat is on the catalog as coming soon.

The first reply

AI drafts SMS on the same thread the ping arrived on. Call tracking picks up after hours. Email parse reads the payload it is not an attachment sitting in Promotions. No “we will call you tomorrow.”

When a human takes over

A specialist jumps in from Team Inbox. You set how visible the handoff is. Cadence stops when the visit is held, the buyer opts out, or a human closes the loop.

Grounded in inventory

Unit questions get answered from stock on that rooftop. If the trim is not on the lot, say so and offer the next unit. No invented packages.

03 · Appointments

Appointments

A conversation that never becomes a slot is still Unread by another name. Calendar Booking uses the store’s real hours, then writes the hold back.

Qualify before you offer times

Intent and rooftop first. Do not book Hudson on the south lot. Budget, timeline, trade, and unit sit on the thread before a closer’s calendar opens.

Offer live availability

Calendar Booking uses the store’s real hours and the assigned closer not a generic “come by Saturday.” The slot is held against that rooftop.

Confirm on SMS

The buyer gets the visit on the same thread they started. One reminder, then the specialist walks in with the transcript.

Write-back, then stop nurture

Lightspeed, Aimbase, DP360, BoatCrazy, ADF Email, or your API gets the hold. Cadence does not ping the morning of. Review no-shows in Reporting on the same record.

04 · Integrations

Integrations

Sources land in. Destinations write back. Your names stay on your rooftops we do not run a shared lead mill.

Lead sources

Facebook Lead Ads, Google, Gmail, Outlook, ADF/XML, OEM programs, marketplace feeds, and website forms. Campaign tags and rooftop mapping stay on the record.

CRM and destinations

Write-back goes to Lightspeed, Aimbase, DP360, BoatCrazy, ADF Email, HubSpot, or a custom API. Owner, transcript, and held visit land where the floor already works.

If your CRM is not listed

Mailbox parse, outbound ADF, and open REST/webhooks cover most stacks. Bring the tool name to a demo we will tell you if it is parse, a destination, or a short mapping.

Data and access

Encryption in transit and at rest, role-based access, and the practices on our security page. Leads are not resold to other stores. Ask on a demo if you need a specific control for your group.

05 · Analytics & reporting

Analytics & reporting

The scorecard a GM can run lives next to the conversation. We do not invent a vanity chat count.

What to look at in standup

First reply, owner, held visit, write-back. Those already live on the thread. Open Reporting, then click into the story not a spreadsheet nobody updates.

First-touch by source

Facebook vs ADF vs site form on the same stream. After-hours pings should still have an owner by morning.

Owner coverage

Unassigned threads are the leak. Team Inbox should be empty at close. Coverage is per rooftop so the south lot is not buried in Hudson’s pile.

Held visits vs conversations

A reply is not a slot. Calendar Booking is the conversion event. If the CRM never saw the hold, the floor will not work it.

06 · Account & billing

Account & billing

Pricing is per rooftop so the floor can share Team Inbox. Implementation is included. No setup fee.

How we charge

Per rooftop, not per seat. Closers and BDC share Team Inbox without a seat tax. See pricing for the current rooftop plans.

Setup and onboarding

No setup fee. Onboarding is included. Sources and phones are usually live in 24–48 hours after go-ahead.

Groups and extra rooftops

Multi-location groups run intake per rooftop. Add a store the same way you add the first assignment and write-back stay mapped to that lot.

Where to ask billing questions

Plan changes and invoices go through sales on the contact page. Product questions stay here or on the FAQ. Support is support@leadstreamiq.com once you are live.

Request a demo and we will map your sources, mailbox, and CRM live.

View pricing

Enter your information

Privacy Policy.
By submitting, you agree to be contacted regarding your inquiry. Consent is not a condition of purchase.