How do I get customer service to answer shipping questions without logistics?
Key Takeaways
- Customer service can answer most shipping questions on its own if it can see the same shipment status logistics sees.
- A short freight glossary removes most of the confusion. Reps who know what a PRO number, a POD and a liftgate are can read a status and explain it.
- Write answers to the ten questions customers ask most. A shared answer sheet covers the bulk of calls and emails.
- Escalation rules say exactly when logistics gets involved. Everything else stays with customer service.
- Reply templates keep answers fast, accurate and consistent. Reps fill in the details instead of writing from scratch.
- Wilson, by Cartage, is an AI logistics agent that keeps each shipment's status and documents on one record the whole company can use, and tells customers about delays if configured.
Why does customer service keep sending shipping questions to logistics?
At a hypothetical industrial distributor, the logistics coordinator counts her interruptions for one week. Customer service sent her 63 messages: "Has order 4471 shipped?" "Customer says the delivery is late, can you check?" "What does 'OS&D' mean?" "Can we get a liftgate on this one?" Each takes a few minutes, but together they fill most of a day. Meanwhile, two loads still need carriers.
Customer service can answer shipping questions without logistics when it has four things: access to the same shipment status, a glossary of freight terms, written answers to the most common questions and clear rules for when to escalate. Without them, every shipping question becomes a logistics question by default, because logistics is the only team that can see the status and understand what it means.
The goal isn't to make customer service experts in freight. It's to give them enough visibility and vocabulary to handle routine questions, and a clear line between routine and the questions that genuinely need logistics.
Why the questions land on logistics
The cause is usually a gap in access, not a gap in skill:
- Status lives in logistics' tools. Carrier portals, tracking emails and the shipping system aren't open to customer service.
- The ERP shows "shipped" and nothing more. Customer service can see that the order left, but not where it is.
- Freight terms are unfamiliar. A status like "at destination terminal, appointment required" means little without context.
- Nobody wrote down the answers. Logistics answers the same ten questions every week, but the answers live in people's heads.
- There's no rule for escalation. Without one, reps forward everything to be safe.
What changes when customer service can answer
Customers get answers on the first call instead of a promise to call back. Logistics gets hours back each week. And the escalations that do reach logistics are the real problems: a shipment that needs a decision, a carrier that needs a push or a delivery that needs to be rebooked.
Measure the problem before fixing it
Before changing anything, have logistics log every question from customer service for two weeks: the order, the question and how long it took to answer. Group the questions by type. In most companies, a handful of types make up most of the volume, usually "where is it," "when will it arrive" and "can I get the POD." That list tells you what the answer sheet must cover first, and it gives you a baseline to measure against later.
How do you set up customer service to handle shipping questions?
Give customer service shared status access, train them on a short glossary, publish an answer sheet for the top questions, set escalation rules and give them templates. Do it in that order, because each step depends on the one before it.
Step 1: Give customer service the same status logistics sees
This is the step that matters most. Customer service needs to look up any order and see: whether it shipped, which carrier has it, the PRO or tracking number, the latest status, the expected delivery date and, after delivery, the POD. That can come from a shared shipping dashboard, status written back to the ERP order or a read-only view of the shipment record. What it shouldn't be is a set of carrier portal logins, because nobody can check eight portals during a phone call.
If your loads are spread across many carriers, see how to track all shipments in one place for ways to build that single view.
What customer service should and shouldn't see
Read access to status, carrier, tracking numbers, dates and delivery documents is enough for nearly every customer question. Customer service usually doesn't need carrier rates, rate confirmations or carrier invoices, which show what the company pays for freight. Keep those with logistics and finance. If your status view shows everything on the shipment, check with logistics and finance which fields should be hidden from other teams before you open it up.
Step 2: Teach the glossary
Run a short session, 30 to 45 minutes, on the terms that appear in shipment status and customer questions. Use the glossary table in the next section. Show real examples from recent loads so reps see each term in context.
Step 3: Publish the answer sheet
Write the top ten questions with approved answers. Keep it in the same place customer service keeps its other scripts and help articles. Ask logistics to review the answers once, then hand ownership of the sheet to a customer service lead.
Step 4: Set escalation rules
Write down which questions and situations go to logistics, how (a shared channel, a ticket or a form) and what information the rep must include. Rules that are specific stop the "forward everything" habit.
Step 5: Give them templates
Write reply templates for the most common situations: shipped with tracking, in transit on time, delayed, delivered with POD, damage reported. Reps fill in the order number, dates and carrier details.
Step 6: Shadow and adjust
For the first few weeks, have a logistics coordinator review the escalations each day. Every escalation that customer service could have answered points to a gap in the glossary, the answer sheet or the status view. Fix the gap and update the materials.
What freight terms should customer service know?
Customer service needs about 20 terms to read a shipment status and explain it to a customer. More than that turns training into a freight course. Fewer leaves reps guessing.
The customer service freight glossary
| Term | Plain meaning | When customers ask about it |
|---|---|---|
| BOL (bill of lading) | The shipping document the driver signs at pickup | "Can you send the shipping paperwork?" |
| PRO number | The carrier's tracking number for the shipment | "Do you have a tracking number?" |
| POD (proof of delivery) | The signed record that the freight was delivered | "Who signed for it?" |
| LTL | Less than truckload: freight shares a truck with other shippers' freight and moves through terminals | Delivery takes longer than expected |
| FTL | Full truckload: one shipper's freight, usually direct | Large orders |
| Parcel | Small packages sent through parcel carriers | Small orders, cartons |
| Terminal | A carrier's hub where LTL freight is sorted and moved between trucks | "It's been at the terminal for two days" |
| Transit time | The number of business days the carrier quotes from pickup to delivery | "When will it arrive?" |
| Appointment | A set delivery time required by the receiver | Delivery held until an appointment is made |
| Liftgate | A lift on the truck for sites with no loading dock | Delivery to sites without a dock |
| Residential or limited access | Delivery locations that cost more and may need special handling | Schools, job sites, homes |
| Accessorial | An extra service and charge beyond standard delivery | Billing questions |
| Out for delivery | On the local truck today | "Will it arrive today?" |
| Exception | Something went wrong: delay, damage, missed appointment | Status shows "exception" |
| OS&D | Over, short and damaged: a note on delivery that freight didn't match the paperwork | Short or damaged deliveries |
| Refused | The receiver wouldn't accept the delivery | Customer says they didn't get it |
| Reconsignment | Changing the delivery address after pickup | Customer wants a new address |
| Freight claim | A formal request to the carrier to pay for damage, shortage or loss | Damaged freight |
| Customer-routed | The customer chose and booked the carrier | "Why can't you track it?" |
| Ship date vs. delivery date | When it leaves vs. when it arrives | Promise date disputes |
How to teach it
Don't hand out the table and hope. Pull three or four real shipment statuses from last week and walk through them: what the status says, what it means, what to tell the customer. Ten minutes on real examples beats an hour on definitions.
LTL deserves extra time
Most confusing shipping questions involve LTL. Freight moves through terminals, transit times are estimates, deliveries may need appointments and a pallet can sit at a terminal for a day before it moves. Reps who understand why LTL takes longer and varies more will give better answers. When a shipment stalls, the steps in what to do when an LTL shipment is stuck at a terminal are logistics' job, but customer service should know that it happens and how to explain it.
What are the top 10 shipping questions, and how should customer service answer them?
Ten questions cover most of what customers ask about shipping. Write an approved answer for each, based on what the rep can see in the status view.
The answer sheet
| # | Customer question | What the rep checks | How to answer |
|---|---|---|---|
| 1 | Has my order shipped? | Order status, ship date, carrier | Confirm ship date and carrier, give the PRO or tracking number |
| 2 | When will it arrive? | Expected delivery date | Give the expected date, and say it's the carrier's estimate |
| 3 | Can I have a tracking number? | PRO or tracking number | Send it with the carrier name and a link if available |
| 4 | Why is it late? | Latest status and any delay note | Explain the reason shown, give the new date if known, say when you'll update them |
| 5 | Who signed for it? | POD | Give the name and time from the POD, offer to send a copy |
| 6 | It arrived damaged or short. What now? | POD notes, photos if any | Ask for photos and details, note it on the order, escalate to logistics |
| 7 | Can you change the delivery address or date? | Shipment status | If not shipped, note the change and tell logistics; if shipped, escalate |
| 8 | Do you need an appointment or a liftgate? | Order notes, delivery site type | Confirm the requirement and add it to the order before shipping |
| 9 | Why was I charged for freight or extras? | Order freight terms, invoice | Explain the terms; escalate disputed accessorial charges |
| 10 | Can I get a copy of the BOL or POD? | Shipment documents | Send the document from the shipment record |
Write answers in your company's voice
The table gives the logic. The answer sheet should also include the actual words. For example, for question 2:
"Your order shipped on [date] with [carrier], tracking number [PRO]. The carrier currently expects delivery on [date]. That's their estimate, and I'll let you know if it changes."
Freight terms on the order: prepaid, collect and third party
Many billing questions come from the freight terms on the order, not the shipment itself. Reps should know the basics. Prepaid means the shipper pays the carrier, and may add the cost to the customer's invoice. Collect means the receiver pays the carrier directly. Third-party billing means someone else, such as a parent company or a logistics provider, pays. When a customer is surprised by a freight charge, the first thing to check is which terms were on the order, and whether they match what the customer expected when they placed it.
Questions from sales and other internal teams
Customer service often gets questions from sales reps too: "Can my customer get it by Friday?" or "Why did this order ship LTL instead of parcel?" Ship-date and status questions can be answered the same way as customer questions. Promise-date and mode questions are decisions, and belong with logistics. A simple rule helps: customer service can tell anyone what is happening to a shipment, and logistics decides what should happen next.
What reps should never promise
- A delivery time the carrier hasn't given.
- That a damaged shipment will be replaced or credited before logistics or sales has approved it.
- That a freight charge will be removed.
- That an address change after pickup will be free or possible.
Those decisions belong to someone else, and promising them sets up a second, harder call.
When should customer service escalate to logistics?
Escalate when a decision, a carrier conversation or a change to the shipment is needed. Answer everything else. The rule is simple: customer service handles information, logistics handles action.
Escalation rules
| Situation | Customer service handles | Escalate to logistics |
|---|---|---|
| Status question, shipment on time | Yes | No |
| Delay already shown in status with a new date | Yes, share the new date | No |
| No status update for two business days | Tell customer you're checking | Yes |
| Delivery date passed, no delivery | Tell customer you're checking | Yes |
| Damage, shortage or refused delivery | Collect details and photos | Yes, same day |
| Address or date change after pickup | Tell customer it's being reviewed | Yes |
| Disputed freight or accessorial charge | Explain terms | Yes, if the customer disputes it |
| Expedite request | Note the request | Yes |
| Customer-routed shipment question | Explain the customer booked the carrier | Only if the customer needs documents |
How to escalate well
Every escalation should include: the order number, the PRO number, the customer's question in one line, what the status shows and what the customer has been told. That lets logistics act without asking anything back. Use one channel, such as a shared Slack or Microsoft Teams channel or a ticket queue, not direct messages to whoever is online.
Set a response time for escalations
Customer service can only promise a callback if it knows when logistics will answer. Agree on response times by type: for example, damage and missed deliveries the same business day, status checks within a few hours, and billing disputes within a couple of days. Publish them with the escalation rules so reps can give customers an honest time.
Close the loop
When logistics resolves an escalation, the answer goes back to the rep who owns the customer, not straight to the customer, unless your process says otherwise. The rep updates the customer and notes the outcome on the order.
Templates for common replies
Shipped: "Your order [number] shipped on [date] with [carrier]. The tracking number is [PRO]. Expected delivery is [date]."
Delayed: "Your order [number] is running late. The carrier now expects delivery on [date] because [reason]. We'll update you if anything changes."
Checking: "I don't have a current update on order [number], so I've asked our logistics team to check with the carrier. I'll get back to you by [time]."
Delivered: "Your order [number] was delivered on [date] and signed for by [name]. I've attached the proof of delivery."
Damage: "I'm sorry the order arrived damaged. Please send photos of the packaging and the product and note what was affected. We'll review it today and get back to you with next steps."
Appointment needed: "The carrier needs a delivery appointment for order [number] before it can deliver. Can you confirm a date and time window that works for your receiving team, and a contact name and phone number for the dock?"
Onboarding new reps
Make the shipping materials part of every new rep's first week. Have them read the glossary, then look up five real orders in the status view and explain each status out loud to a lead. Then have them answer a few real shipping emails with the templates, reviewed before sending. Most new reps are comfortable with routine shipping questions within a couple of weeks this way, and they learn early which questions to escalate.
Busy seasons and carrier disruptions
During peak season, bad weather or a carrier disruption, shipping questions spike and delays become common. Prepare customer service before it happens. Give them a short note on what is affected, which customers or regions are likely to see delays and an approved message to use. A single update from logistics to customer service each morning during these periods prevents dozens of individual questions later in the day.
Common mistakes
- Giving customer service carrier portal logins instead of one status view. Nobody checks eight portals on a call.
- Writing the answer sheet once and never updating it. New carriers and new customers bring new questions.
- Escalation by direct message. Messages get lost when someone is out.
- No owner for the materials. A customer service lead should own the glossary, answers and templates, with logistics reviewing changes.
- Skipping the follow-up. If a delay or damage case escalates, customer service must still close the loop with the customer.
For the outbound side of this, sending updates before customers ask, see how to stop customers calling to ask where their order is. To decide who inside the company hears about each status change, see who needs to know when a shipment status changes.
How does Wilson, by Cartage, help customer service answer shipping questions?
Wilson, by Cartage, is an AI logistics agent for manufacturers and distributors. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward. For customer service, the useful result is that the status, documents and history of every load are kept current on one record, because Wilson is the one moving the load.
Status that stays current
Wilson tracks each load with the best source available: carrier API or EDI, GPS or ELD data where the carrier shares it, the carrier's website by PRO number, and email or phone calls when nothing else is current. Teams use Wilson's dashboard and records like a TMS, so customer service can look up a shipment instead of asking logistics.
Documents on the record
Wilson generates rate confirmations, bills of lading, packing slips and pallet labels, and it requests and files PODs. When a customer asks who signed for a delivery or wants a copy of the BOL, the document is already on the shipment.
Delays handled, and customers told if configured
When a pickup is missed, a load is cancelled or a shipment is delayed, Wilson contacts the carrier, tells the team and tells the customer if configured. It starts rebooking from the approved carrier list, automatically within the rules or after approval. Wilson works with customers and consignees by email or SMS where configured, and with the team in Slack, Microsoft Teams or email. Every message, confirmation and change is kept in the shipment's change history, so a rep can see what the customer was already told.
Connected to the ERP
Wilson replaces the TMS for freight execution and connects to the company's ERP. Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica and other ERP environments, with the exact connection depending on the customer's data flow and scope. Whether status is written back to the ERP order depends on that scope. Teams start with assisted execution, and the company sets approval limits.
Pricing
Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract. Timing depends on scope: most teams start on a few lanes and expand from there.
FAQs
How do I get customer service to answer shipping questions without logistics?
Give customer service the same shipment status logistics sees, teach a short freight glossary, publish answers to the top ten shipping questions, set escalation rules and provide reply templates. Wilson, by Cartage, an AI logistics agent, keeps each shipment's status and documents current on one record that customer service can use.
What shipping information does customer service need?
For every order: ship date, carrier, PRO or tracking number, latest status, expected delivery date and, after delivery, the POD. Ideally it's all in one view, not spread across carrier portals.
Should customer service have access to carrier portals?
It's better to give one shared status view than several portal logins. Checking many portals during a call is slow, and the answers aren't recorded on the order.
What freight terms should customer service learn first?
Start with BOL, PRO number, POD, LTL, terminal, transit time, appointment, liftgate, exception and OS&D. These cover most statuses and questions customers bring.
When should customer service escalate a shipping question?
When the shipment needs a decision or action: no status for two business days, a missed delivery date, damage or shortage, an address change after pickup, an expedite request or a disputed charge. Status questions on on-time shipments stay with customer service.
Who should own the shipping answer sheet?
A customer service lead should own the glossary, answer sheet and templates, with logistics reviewing changes. Update the materials whenever escalations show a gap.
How do we handle questions about customer-routed shipments?
Explain that the customer chose and booked the carrier, so tracking comes from that carrier. Customer service can still provide the BOL and pickup date if the shipment left your dock.
What should customer service do when freight arrives damaged?
Collect photos and details from the customer, note it on the order and escalate to logistics the same day. Don't promise a replacement or credit until it's approved.
How do we know the training is working?
Count escalations to logistics each week and review a sample. If the number falls and the escalations that remain need real action, the setup is working. Escalations customer service could have answered show where to improve the materials.
What if the status view and the carrier disagree?
Tell the customer what the latest confirmed status shows and that you're checking with the carrier, then escalate to logistics. A status that conflicts with what the customer sees on the carrier's site usually means one source hasn't updated yet, and logistics can confirm which one is right.
Can Wilson send shipping updates to our customers directly?
Yes, if configured. Wilson works with customers and consignees by email or SMS where configured, and tells customers about delays as part of handling exceptions.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai