Loading...
The owner SMS alert is on Growth. A configured first reply and follow-up task are Pro.
Service businesses capture the submission, alert the owner, and move the card. Calling the customer is still a person. A first reply runs only if a Pro workflow is configured.
Sample account · Sample data. The film is a demonstration of the product, using sample records.
Your website
Request a quote
POST /api/leads/ingest
{
"name": "Sample Lead",
"phone": "(•••) •••-0142",
"service_type": "Example Service",
"source": "website",
"source_page": "/contact"
}201 · lead created
The record it created
One form submission becomes a lead, with its source attached.
Screening: honeypot · disposable domain · content scoring
A sample lead moving through Long Drive Leads, built from the product’s own screens and anonymous sample data. Nothing here is a real customer.
1. Trigger
Someone submits a form on your site. The request is screened, then stored as a lead with its source.
2. Long Drive Leads
The owner alert is queued. Quiet hours can defer the text. On Pro, a workflow you configure can send a first reply and create a task.
3. Operator sees
The submission label, where it came from, how long it has been waiting, and the card on the board.
4. Next action
You call them. The product does not send a customer reply unless that Pro workflow is installed.
Open, accept and a deposit. Templates are Pro.
Permission, bad addresses, pause and STOP. Supporting, not the flagship.
The owner SMS alert is on Growth. A configured first reply and follow-up task are Pro.