Meet Lena Live
AI load entry that shows where every field came from
Lena reads rate confirmations and air-freight delivery orders, drafts the load with the source text beside each field, and hands it to your team. Nothing gets created that a person did not confirm.
Every FreightVero agent drafts. A person on your team approves anything that changes a load or reaches a customer or carrier.
Short answer
Lena is the FreightVero Load Entry agent. Give it a PDF and it sorts which kind of document it is, drafts the load details with the source text behind every field, converts weights, resolves the stop’s time zone, flags duplicates and revised rates, and creates the load once a person confirms the draft.
The job today
For a brokerage that covers loads for other brokers and forwarders, a load starts as someone else’s paperwork. A rate confirmation lands as a PDF. Someone opens it and types the pickup and delivery addresses, appointment times, equipment, weight, reference numbers and rate into the TMS. Then the next one shows up in a different layout.
General purpose email parsing software has a hard time here, because freight paperwork does not share a format. The sample documents from Bronco Logistics, the brokerage FreightVero was built inside, came in three unrelated shapes, and plenty of them carried no price at all.
Some are rate cons from other brokers. Some are air-freight delivery orders from forwarders, with no rate, no appointment and no equipment anywhere on the page. The rest are supporting documents, BOLs and packing lists, that belong on a load already in the system.
Then there are revisions. In Bronco’s samples the same load arrived twice, minutes apart, at two different rates. A person keying documents as they come in books that load twice, or books it at the rate that was already replaced.
How Lena works
You give it a document
Lena takes a PDF. A carrier rate confirmation, or an air-freight delivery order from a forwarder. You hand it the file. You do not point it at a mailbox.
It sorts the document first
Rate confirmation, air-freight delivery order, or a supporting document like a BOL or a packing list. A supporting document attaches to a load that already exists and never creates one.
Every field comes back with its source text
Each value arrives with a confidence score and the exact text it was read from, so your team checks a snippet instead of retyping a document. A field the paperwork does not contain is marked not on this document.
Duplicates, revisions, zones and units get checked
Before the draft reaches anyone, Lena hashes the document to catch a re-send, compares the rate and the stops against loads on file to catch a revision, resolves what time zone each stop sits in, and converts kilograms to pounds.
A person confirms, then the load is created
The review screen is a split view. Document on one side, draft on the other, low-confidence fields outlined so your eye goes straight to them. Fix what is wrong, confirm, and the load, its stops and its freight lines are written in one transaction.
What it checks, and where a person stays in control
Not on this document beats a guess
An air-freight delivery order usually carries no rate. Lena says so instead of inventing one. Absent is a real answer, and it reads differently from missed.
A document that argues with itself gets flagged
A note reading PU BY 4PM against an appointment field of 14:30 to 16:00 is a conflict, not a detail. Lena marks the field and the call goes to your team.
The same load does not get booked twice
A content hash catches the identical PDF sent again. A revision is the sneakier one.. the same load at one rate, then another rate minutes later. That gets flagged against loads already on file instead of booked a second time.
Stop times land in the right zone
Lena reads the zone printed on the document first, then the facility already on file for that customer, then the zip code. Florida, Texas, Tennessee, Kentucky, Indiana and Idaho get resolved by zip, because the state alone does not tell you. Arizona does not shift in summer and is handled. When it cannot be certain, it asks.
Kilograms become pounds at save
Air freight comes in kilos and the TMS runs in pounds, so Lena converts at save. A weight with no unit on it is refused outright. A 2,075 kg load booked as 2,075 lb is a real problem, and asking beats assuming.
Nothing is created on its own
The draft writes nothing to your loads. The create step runs only after a person confirms, and the load then goes through the same four checkpoints as any other load in the FreightVero TMS.
What week one looks like
You point Lena at the paperwork already sitting on a desk. Rate cons from the brokers you cover for, delivery orders from your forwarders, BOLs and packing lists that belong on loads you already have. The review screen puts the document beside the draft and your team confirms or corrects.
Expect to correct fields that first week, and expect to see why.. every value carries the text it came from, so a correction takes a glance instead of a re-read. Loads land in the FreightVero TMS, where checkpoints are enforced in the database. For the manual version of the same check, see the rate confirmation checklist.
Run it on your own freight
Send us a handful of the rate cons and delivery orders that actually hit your desk, and tell us roughly how many a month. We’ll run them through and show you the drafts, source text and all.
Frequently asked questions
Is this email parsing software?
It does the job email parsing software does, aimed at freight paperwork: pulling structured load details out of documents. The difference is that Lena works from the documents you give it, and every field it returns carries the text it was read from.
What happens when the rate isn't on the document?
The field comes back marked not on this document, and a person fills it in before confirming. Air-freight delivery orders usually carry no rate, no appointment and no equipment, so those fields come back marked rather than guessed.
How accurate is it?
We don't publish a single accuracy number, because one number hides the thing that matters, which is which field was wrong on which document. Every value comes back with the text it was read from and a confidence score, and low-confidence fields are outlined on the review screen. Every draft is stored, so you can look back at what Lena read and what your team changed.
Does it read shipper load tenders?
Lena handles three document families: rate confirmations, air-freight delivery orders, and supporting documents like BOLs and packing lists. Shipper tenders by email or EDI sit outside that set. If most of your loads start as a tender, tell us during scoping and we'll say plainly whether the agent fits your desk.
Can it enter loads into our current TMS?
Lena creates loads in the FreightVero TMS, where the stops, freight lines and checkpoints live. For a brokerage running another TMS, we scope what a connection would take, and we'll tell you straight if your TMS doesn't allow it.
