For dispatch, forwarding and transport desks
Signalhaul reads the email, Telegram, Viber and PDF traffic your desk already receives and pulls each shipment into fixed fields with the line it came from. A dispatcher on your team approves and sends the reply — always.
Pilot price [PILOT_PRICE] Early access — paid pilot
One fixed fee for the fourteen days, agreed in writing before anything is connected. No subscription and no commitment beyond the pilot. Works inside the inbox and chat accounts your team already uses. No outbound message is ever sent without a human clicking send.
Lane view
Illustration — not live dataHeld for approval
Illustrative queue. Items move through reading and drafting, then stop at the approval gate and wait for a person.
Channel marks: TG (Telegram), PDF, MAIL (email). The animation pauses when this panel scrolls out of view, and never starts if your system asks for reduced motion.
A worked example
The same inbound message at three stages: as it arrives, as it is extracted with the line each field came from, and as a draft waiting for a person to approve.
Illustrative example — sample data, not a customer.
01 — As it arrives
TelegramMarta K. — sample sender, not a real customer
Morning! Do you have a truck for 22 pallets, non‑stackable, from Rotterdam 3011 to Poznań? Loading Thursday from 14:00, unloading Monday morning slot. No temperature control. Also — is your office open on Friday, and can someone resend last month’s invoice? The PDF wouldn’t open on my phone.
Received 08:41
02 — Extracted, with provenance
Opportunity cardHover, tap or focus a field to highlight the sentence it was read from. A field and its source carry the same mark.
No field selected.
Missing fields are flagged rather than guessed — the draft asks the question instead.
03 — Drafted, awaiting approval
Not sent — waiting for a personHello Marta,
Thanks for the request. We can cover Rotterdam (3011) → Poznań with a standard curtainsider, loading Thursday from 14:00 and unloading Monday morning.
Two things before we confirm: what is the total gross weight, and is a tail lift needed at unloading? Your office-hours and invoice questions have gone to our administration team separately.
Best regards,
Dispatch
How it works
01
Newsletters, invoice chases, driver chatter and status pings are set aside with a reason attached. Real transport requests move forward, in whatever channel they arrived.
02
Route, dates, cargo, equipment and references are read out of the message body or the attached PDF, each with the source line it came from. What is missing stays visibly missing.
03
A reply is prepared in your tone, with open questions included. It waits in your queue. Your dispatcher edits, approves and sends it from your own account.
Control & safeguards
Dispatch is a relationship business. Nothing here replaces the person who answers — it removes the reading, sorting and retyping that happens before they can.
Drafts sit in a queue until someone reads, edits and sends them. There is no auto-send mode, no scheduled release and no “confident enough” threshold that bypasses review.
Your shared mailbox, your Telegram and Viber numbers, your PDF attachments. Replies leave from your own address, so the customer sees the same sender as always.
Messages set aside stay in their folder with the reason recorded, so a dispatcher can disagree and pull one back. Every extracted field keeps a pointer to the line it came from.
Before the pilot starts we document, in the pilot agreement, which mailboxes and chats are connected, what is stored and for how long, who on our side can see it, and how to revoke access and request deletion. Scope, retention and processing terms are set with your team — and reviewed with your own legal or compliance people, not asserted here.
The other end of the inbox: doors, bays and a yard that does not wait.
Illustrative photography. Nobody and nothing pictured is a customer — no vehicle, site or livery shown belongs to one.
Photo: Matthew Jackson / Unsplash
The photograph did not load, so the drawing stands in for it. README.md documents how the plates are swapped.
Who you would be working with
[FOUNDER_NAME]
Founder, and the person who runs every pilot
[FOUNDER_LOCATION]
This is an early-stage product, not a finished platform. For the fourteen days you deal with me directly: the workflow review, the tuning of what gets extracted, the check-ins during the two weeks and the written hand-back at the end.
That is the honest trade. You get someone who will sit with your actual inbound traffic instead of a support queue — and software that is still being shaped around desks like yours, which is exactly why the pilot is short, paid and easy to walk away from.
Draft Name and location are placeholders on this prototype and must be filled in before the page is published.
Where the pilot lands: a yard still working after the office has closed.
Illustrative photography. Nobody and nothing pictured is a customer — no vehicle, site or livery shown belongs to one.
Photo: Tasha Kostyuk / Unsplash
The photograph did not load, so the drawing stands in for it. README.md documents how the plates are swapped.
The offer
Two weeks, one desk, your own messages. Long enough to see whether the queue is genuinely faster to work through — short enough that nobody has to reorganise the company to find out.
The first 30 minutes
The sample review costs nothing, and nothing is connected to your mailboxes or chat accounts at that stage.
Questions
Shared and individual mailboxes over standard mail protocols, Telegram and Viber business accounts, and PDF attachments including scanned transport orders. Extracted cards can be exported as structured records or pushed into a TMS or CRM where an interface exists.
If a system on your side has no usable interface, we will say so during the workflow review instead of promising an integration.
No. Drafting and sending are separate steps, and only the second one reaches a customer. A draft stays in the queue until a person opens it, edits it if needed, and sends it. There is no setting that removes that step.
One fixed fee for the fourteen days, quoted after we have seen your sample messages and agreed the scope, and written into the pilot agreement before anything is connected. The sample review that comes first is free.
A short workflow review, then access to one mailbox and one chat channel. Your team keeps working the way it does now — the queue sits alongside the inbox rather than replacing it, so there is nothing to migrate and no new system for dispatchers to learn on day one.
That is what the paid pilot is for. It runs on your real inbound traffic for two weeks against the measures listed above, and it ends with a written summary of what worked and what did not — including the honest answer if the volume or channel mix does not justify it.
Companies whose requests arrive already structured, through a portal, usually have little to gain here.
Request a pilot
We will read it, come back with whether a pilot makes sense for your desk, and propose a short workflow review. If it is not a fit, we will tell you that instead.
Prefer email? Write to hello@signalhaul.example
This prototype is not connected to any service, so nothing was transmitted. Below is exactly what a real endpoint would have received.