Meet Cora Live
Shipment status updates written from what the load is actually doing
Cora, the Customer Update Agent, sends an update on five load events: carrier dispatched, arrived at pickup, delivered, cancelled, and carrier fall-off. The POD and the freight photos ride on the email, so your salesperson forwards it to the customer without anyone signing into anything.
Every FreightVero agent drafts. A person on your team approves anything that changes a load or reaches a customer or carrier.
Short answer
Cora sends a shipment status update from real load events in the FreightVero TMS: carrier dispatched, arrived at pickup, delivered, cancelled, and carrier fall-off. Each message goes to the salesperson assigned to that load, plus any extra recipients set on the customer, and it carries the load number, the customer’s reference number, the carrier, the stop cities and times in the stop’s own time zone, and the POD and freight photos as attachments. Your salesperson forwards it to the customer. It has been sending since September 14, 2026.
The job today
Customers want three answers from a broker. Where’s my freight? Will it make the appointment? Where’s the POD? Most brokerages answer by hand. A rep watches the board, types an email when something changes, and digs the POD out of a folder when the customer asks for it.
That breaks down on busy days. Updates go to the loudest customers first. A carrier falls off and the customer hears about it after the recovery truck is booked, or never hears at all.
Cora sends on the five moments that actually change the customer’s day, writes the email off the load record, and staples the paperwork to it. Your salesperson reads it and forwards it. Nothing reaches a customer that a person on your team did not send.
How it works
One of five events fires
The carrier gets dispatched, arrives at pickup, delivers, the load is cancelled, or a carrier falls off. Arrival can come straight from the driver confirming on site in Load Market. Nothing else sends an email.
The email builds itself from the load
Load number and what happened go in the subject line. The body carries the customer, the customer’s own reference number, the carrier, the pickup and delivery city, state and time, and the photo and POD count. A fall-off or a cancellation carries the reason.
Times print in the stop's time zone
“Pickup: Hebron, KY 09/14, 12:30 ET”. A Kentucky pickup prints in Eastern and says so. Military time, same as the screens, so nobody has to do the math twice.
Paperwork rides on the message
The POD, the BOL and the freight photos attach to the email itself, up to eight files. They are not links. A salesperson forwards a delivery notice straight to the customer and the customer opens it without an account.
It lands with the salesperson on the load
Only the salesperson assigned to that load gets it, plus any extra recipients set on the customer. There is a button in the email that opens the load.
What it sends, and what it leaves alone
Five events, not every status change
Four or so emails per load instead of ten. A salesperson who gets ten learns to filter the sender, and then misses the one that mattered. The rest of the load’s movement lives on the load board where it belongs.
The salesperson on the load, and nobody else
No salesperson on the load means no email. That is a load nobody asked to be told about. Extra recipients can be set per customer, so the customer’s own people are copied automatically on their loads.
Carrier paperwork never leaves the building
The carrier rate confirmation, the signed rate confirmation, W9s and certificates of insurance are excluded on purpose. They never go out on a customer update. The POD and BOL are ordered first so they survive the eight file cap.
Cancelled loads come with nothing attached
Nobody needs freight photos of a shipment that is not happening. The cancellation carries the reason and the load number, and that is it.
Your name on it, your dispatch address on the reply
The message carries your company name, and replies go to your own dispatch address. The customer answers your team, not a system.
Any of the five can be switched off
Each event is a setting per brokerage. Turn off arrived at pickup if your customers do not want it. No code change, no ticket.
What week one looks like
Turn it on and the next load your team dispatches sends an email to the salesperson on it. By the end of the week that salesperson has a dispatched notice, an arrived at pickup notice and a delivered notice with the POD attached, sitting in the same inbox they already live in. That delivered notice forwards to the customer exactly as it arrived, because the POD is already on it.
Cora reads the events your team is already creating in the FreightVero TMS, including live tracking and the four checkpoints. If a customer would rather look than be emailed, point them at the customer portal.
Run it on your own freight
Tell us which customers expect updates and who on your team answers them today. We’ll turn on the events that fit your brokerage and set the extra recipients per customer.
Frequently asked questions
Does it email my customers directly?
It emails the salesperson assigned to the load. They forward it. The attachments are on the message, so forwarding a delivery notice with the POD takes one tap and the customer does not sign into anything. If a customer wants their own people copied every time, set them as extra recipients on that customer and they are copied automatically on their loads.
Why only five events?
Because a salesperson who gets ten emails on one load learns to filter the sender, and then misses the one that mattered. Carrier dispatched, arrived at pickup, delivered, cancelled and carrier fall-off are the five that change somebody's day. Everything else is on the load board.
Does it send the POD?
Yes. The POD, the BOL and the freight photos attach to the message itself, up to eight files, with the POD and BOL ordered first so they survive the cap. Carrier paperwork is excluded on purpose: the carrier rate confirmation, the signed rate confirmation, W9s and certificates of insurance never go out on a customer update.
What time zone do the times print in?
The stop's own, labeled. "Pickup: Hebron, KY 09/14, 12:30 ET". A Kentucky pickup no longer prints in Central with no label on it. Military time, same as the screens.
Can I turn one of the events off?
Any of the five, per brokerage, without a code change. If your customers do not care about arrived at pickup, turn it off and it stops sending.
Can it send EDI 214 status messages?
Not today. EDI is a planned integration and isn't built. Shippers that require 214s would need that integration first. See EDI integration for how 214 status messages work and what the integration is planned to cover.
Where do the load events come from?
From your team working loads in the FreightVero TMS, and from Load Market tracking, which is live. A driver confirming arrival on site can move the status. Other tracking providers such as MacroPoint and project44 are planned, not built.
