Loading...
Self-serve Growth trial, for shops that do the work on site.
The form becomes a lead. On Growth you get the owner text, and a review request can follow a job marked won. A configured reply to the customer is a Pro workflow you install. Nothing here dispatches a crew or optimizes a route.
Sample account · Sample data. The text is to the owner. The customer is not messaged unless a Pro workflow is configured.
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. Lead
The form is stored with its source and sits on the pipeline.
2. Text
Growth queues the owner SMS. Quiet hours can hold it. You still make the call.
3. Estimate
You send the estimate. Templates are Pro. Each morning a reminder can name the oldest leads still in New, and the oldest still in Contacted or Quoted. It is a handful, and it is a prompt.
4. Review
After the job is marked won, Growth can send the review request on the delay you set. That is a request, not a promise of stars.
Owner alert on Growth. No customer reply unless you configure a Pro workflow.
Growth sends the estimate. Templates are Pro.
Review requests
Growth and above, after the job is marked won. The delay is the account setting.
Quiet hours and STOP apply to the texts.
The umbrella for trades, home services, and similar work.
The same alert, for route work. No recurring-visit scheduler.
Self-serve Growth trial, for shops that do the work on site.