HV

Input Sources

Every channel feeds the same matching engine — source-agnostic by design.

Email
Gmail freight intake
Connected
This week
2,418
Avg parse
820ms
Telegram
Driver + dispatch bot
Connected
This week
1,651
Avg parse
640ms
WhatsApp
Direct driver channel
Connected
This week
1,102
Avg parse
710ms
Voice
Direct driver channel
Connected
This week
384
Avg parse
2100ms
API
Client REST integration
Connected
This week
512
Avg parse
210ms
Web Read
Automated web polling
Connected
This week
252
Avg parse
1140ms

Automation stack

Production architecture powering the ingestion layer

Telegram driver bot
Bot · Last run 2 min ago
Healthy
Gmail freight intake
Email · Last run 1 min ago
Healthy
AI document / image processing
AI · Last run just now
Healthy
Google Sheets sync
Sync · Last run 18 min ago
Attention
Make.com — DRIVER UPDATE
Scenario · Last run just now
Healthy
Make.com — Integration Telegram Bot
Scenario · Last run 3 min ago
Healthy
Source-agnostic
The matching engine is source-agnostic. New channels are added to the existing engine — no rebuild — so reach expands at low marginal cost.

Channel mix

Loads ingested per channel — this week

Custom source setup

For enterprise customers — API connection or automated web read against your own freight source

Endpoint
Normalized sample
{
  "id": "LD-88475",
  "channel": "Web Read",
  "origin": { "city": "Tampa", "state": "FL", "zip": "33602" },
  "dest":   { "city": "Charlotte", "state": "NC", "zip": "28202" },
  "total_miles": 588,
  "empty_miles": 51,
  "equipment": "Box Truck",
  "broker": "Sylectus feed",
  "received_at": "2026-06-30T18:47:00-04:00"
}