There is a category of product decision that looks obvious from the outside and isn’t.
Website text widgets are a solved problem. Several companies make good ones. A few thousand of our own dealers already pay for one. The straightforward move for us was to partner with one of them, certify the integration, and put it on a slide.
We didn’t do that.
I want to explain why, because the reasoning is the product.
What we kept seeing in dealerships
Our product team now averages 10 to 12 dealer visits a month. We do this because the difference between what a dealer tells you on a call and what you see when you stand behind the counter is substantial.
Here is something we saw over and over.
A BDC agent has two windows open. One is Lightspeed, where the CRM lives, where the deal happens, where the customer’s history is. The other is a third-party messaging tool, where the website conversations arrive.
When we asked which one they worked out of, the honest answer was almost always “both.” And when we pushed a little further, it usually became clear that one of them was getting checked far less often than the other.
That’s not a criticism of the tool. The tool works. It’s a structural problem: the conversation starts in one system and the deal lives in another, so somebody has to move it. Usually by hand, sometimes on a sync interval, occasionally not at all.
The decision we made
We decided the lead should not have to travel.
That sounds like a small distinction. It isn’t. It’s the difference between a website conversation that syncs into your DMS and a website conversation that starts there.
When we drew it that way, a partnership stopped making sense. You cannot deliver “the lead starts in Lightspeed” through an integration with a company whose product is, correctly and by design, outside Lightspeed. Integrations move data. We didn’t want to move data. We wanted there to be nothing to move.
What building it ourselves let us do
Four things fell out of that decision that we could not have delivered any other way.
The CRM lead creates itself.
Every submission through the widget creates or matches a CRM lead automatically, with the source, the page URL, and the unit the visitor was looking at attached. Nobody re-keys anything. Nobody waits on a sync interval. For the first time, a dealer can look at their CRM and see plainly what their website is producing.
It runs on texting the dealer already has.
Lead Capture uses the dealer’s existing Twilio configuration. No second number to provision, no setup fee, no parallel messaging account to administer. This is only possible because we already run the dealer’s texting.
The conversation lands where the team already works.
Website messages appear in the Communication Hub alongside every other conversation the dealership is having. There is no new interface, no new login, and no new thing to train staff on. The rep replies from the screen they were already looking at.
Compliance is part of the product, not a setting someone forgets.
TCPA consent capture, configurable quiet hours with auto-responders, and digital accessibility are built in. Multi-rooftop groups can put a location selector in the widget so the lead routes to the right store’s team and the right store’s number — which, for a dealer group, is not a nice-to-have. It’s the whole requirement.
What we deliberately did not build
I want to be straight about the scope, because I think the industry would be better off if more vendors were.
Lead Capture is a website lead capture widget. It is not reputation management. It is not broadcast messaging. It is not text-to-pay. Some of the tools dealers use today bundle those things together, and if a dealership genuinely uses all of them, this is not a one-for-one swap and I won’t pretend otherwise.
What I will say is that the widget is the piece that never should have lived outside the DMS in the first place. That’s the piece we fixed.
On pricing
We took the same approach here that we took with AI Command Center: make it predictable and make it easy to explain.
$199 per rooftop per month. No user tiers. Every user at the location is included, so adding a salesperson or a BDC rep does not change the bill.
Lead Capture runs on the Lightspeed texting your store already has. If you are texting through Lightspeed today, Lead Capture switches on alongside it. If you are not, that is the one piece to put in place first, and your account manager can tell you where you stand in a single call.
There is no per-conversation pricing and no setup fee. A dealer should be able to decide whether this is worth it in about fifteen seconds.
Where this goes
Capturing the lead natively is the foundation, not the finish line.
The reason we cared so much about the lead starting inside Lightspeed is that it makes the next thing possible. Once a website conversation is a first-class object in the DMS, our AI agents can work on it — qualifying an inbound text before a salesperson ever picks it up, so the shopper who messaged you at 9:15 on a Tuesday gets a real response at 9:16.
That work is underway. I’m not going to give you a date, because we don’t ship AI on a date. We ship it when dealers tell us it’s ready — the same standard we held ourselves to with AI Command Center.
But none of it is possible if the lead is sitting in someone else’s inbox.
Three things worth remembering
- It’s native. Website conversations start inside Lightspeed. There is nothing to sync, and no second inbox for your team to forget about.
- It’s simple to turn on. One script, your existing texting configuration, and a target go-live under 10 days.
- It’s honest about what it is. A website lead capture widget that belongs in your DMS — and the foundation for what our AI agents do next.
Your website has been generating these conversations all along.
Now they start in the right place.