Rules that match inbound leads to the right carrier automatically — service radius, vehicle match, availability, vendor rating. The preview is live in the CRM today; the production rule engine ships to the Growth tier Q4 2026.
Industry data on this is brutal: a lead responded-to within 5 minutes is 21x more likely to book than one responded-to in 30 minutes. By hour four, your odds are below 2%. Yet most operators we onboard are averaging 3-7 hours to first-touch on inbound widget leads — mostly because the dispatcher who sees the lead first is also the one answering the phone, charging a card, and loading a 20-passenger bus.
The fix the industry sells you is “hire more dispatchers.” The fix that actually works is a rule engine that routes the lead directly to the vendor most likely to cover it — before the dispatcher even sees it — and lets the first vendor to accept lock in the trip. First-vendor-wins forces vendors to respond in minutes, not hours.
The Stretch auto-leads engine is that routing layer. You write rules like “Mid-Atlantic airport runs under $400 → offer to Coastal Coach & Bluebird for 15 minutes.” Lead comes in matching the shape, both vendors get a push notification, first one to tap “accept” wins. Your dispatcher sees the already-covered trip when they next log in.
Visual rule builder: WHEN (lead service type / pax count / pickup region / trip date / dollar amount) MATCHES → OFFER TO (vendor list / vendor tier) FOR (15 min / 1 hr / 2 hr). Save as many rules as you want. Priority-ordered.
Lead lands in your CRM. Engine walks your rules in priority order, picks the first match, computes the eligible vendor set (filtering out vendors with expired insurance, no matching vehicle, or outside the service radius), fires the offer.
Eligible vendors see the trip in their portal with a countdown. Tap “accept” to claim it. First-accept wins; everyone else gets a “trip filled” notice. Vendor response time is logged against their close-rate score.
No vendor accepts in the window? Lead escalates to the dispatcher queue with a flag: “auto-leads couldn’t cover.” You intervene, re-offer manually, or call around — but at least you know within an hour, not six.
Each rule tracks: offers fired, accept rate, avg time-to-accept, trips won vs expired. Prune rules that aren’t working; double down on the ones that are.
One toggle to pause the whole engine — useful for holiday weeks, big weather events, or when you want to hand-dispatch for a day. Pending offers stay valid; new leads route to the manual queue.
No surprises, no “contact sales for pricing.” Everything in the stack has a price tag on the box.
Auto-leads engine unlocks on the Growth tier ($189/mo) alongside the vendor portal, SMS, integrations, and advanced reports. Preview mock lives in the CRM today; production engine ships Q4 2026. Growth subscribers get first access.
| Capability | Free | Pro | Growth | Scale | Enterprise |
|---|---|---|---|---|---|
| Preview in CRM | ✓ | ✓ | ✓ | ✓ | ✓ |
| Live rule engine (prod) | — | — | ✓ | ✓ | ✓ |
| Rules in production | — | — | 10 | 50 | Unlimited |
| Vendor pool per rule | — | — | 10 | 50 | Unlimited |
| Per-rule metrics dashboard | — | — | ✓ | ✓ | ✓ |
| Dispatcher fallback escalation | — | — | ✓ | ✓ | ✓ |
| Multi-brand cross-routing | — | — | — | — | ✓ |
Spin up a tenant in 60 seconds. Try the free tier first — upgrade only when you need the feature on this page.