Can your team reach an AI logistics agent on Slack, Teams, WhatsApp or text?
Can your team reach an AI logistics agent on Slack, Teams, WhatsApp or text?
Consider a hypothetical building-supply distributor on a Wednesday afternoon. A sales rep standing in a contractor's yard sends a WhatsApp message: "Did PO 5520 ship? Customer says nothing arrived." At the same moment, a customer service rep asks in a Microsoft Teams channel whether the Thursday delivery to the Reno branch is still on. The plant manager calls the logistics desk about a truck that hasn't shown up at dock 3. The logistics coordinator is answering a carrier email about a reweigh. Four channels, four questions, one person, and every answer lives somewhere different.
Yes, a team can reach an AI logistics agent on Slack, Microsoft Teams, WhatsApp, text, email or phone, as long as the agent is set up for those channels and every exchange is written to the same shipment record. The channel decides how fast and how easily people can ask. The record decides whether the answer is the same no matter who asks or where. An agent that answers a Teams message with one ETA and a text message with another has made the problem worse, not better.
The goal isn't to put freight into every app. It's to let each person ask in the place they already work, and to make sure the answer comes from one place.
What reaching the agent should look like
For the rep in the contractor's yard, a good exchange looks like this:
- The rep asks in WhatsApp, using the PO number.
- The agent finds the load attached to that PO, checks the latest status from the carrier, and replies: delivered at 10:42 this morning, signed by a named receiver, POD on file.
- The rep forwards the answer, or asks the agent to send the POD to the customer if that's allowed under the company's rules.
- The question and the answer are written to the load, so customer service sees the same thing an hour later.
Nobody had to stop the coordinator. Nobody had to log into a portal. And the next person who asks about PO 5520 gets the same answer.
What the channel can't fix
A new channel doesn't fix missing data. If the carrier hasn't sent an update in two days, the agent should say so and go get one, not guess. If the PO isn't linked to a load, the agent should ask which load it belongs to. Channels make the work easier to reach; they don't replace the work.
Let's review where your team talks about freight today. You don't need to prepare anything: Cartage maps the workflow with you on the call.
See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.
Book a demo →Which channel should each group use with an AI logistics agent?
Each group should use the channel it already checks most often, with clear limits on what that group can ask for and see. Internal teams, salespeople, customers and carriers have different needs, and treating them all the same leads to noisy channels and information going to the wrong people.
Four audiences, four sets of needs
| Audience | Channels that usually fit | What they typically ask or need | What they should not see |
|---|---|---|---|
| Logistics team | Slack, Microsoft Teams, email | Exceptions, approvals, quotes to review, rebooking decisions | Nothing withheld; they own the loads |
| Customer service and sales | Teams or Slack at the desk; text, WhatsApp or phone on the road | Order status, delivery date, POD, "can we ship by Friday?" | Carrier rates, margins, internal disputes |
| Plant, warehouse and receiving | Teams, Slack, text, phone | Which truck is next, appointment times, late arrivals | Customer pricing, carrier negotiation |
| Customers and consignees | Email, text where configured | Shipped, delayed, delivered, appointment confirmations | Carrier names if the company keeps them private, rates, internal notes |
| Carriers | Email, phone, API, EDI | Tenders, rate confirmations, pickup details, POD requests | Other carriers' quotes, the shipper's targets |
The table leaves out one common mistake: putting a customer or a carrier into the same chat space as the internal team. A shared channel is convenient until someone posts a carrier's rate in front of a customer.
Why the logistics team should stay in its main work tool
Most logistics teams already live in Slack, Microsoft Teams or email. Asking them to watch another app for freight work means they'll check it late. An AI logistics agent that posts exceptions and approvals where the team already works gets faster answers. Keep it to the decisions that need a person; routine updates belong on the load, not in the channel.
Why sales and customer service need mobile channels
Sales reps and account managers ask the most freight questions and are the least likely to be at a desk. A text or WhatsApp message from a phone is often the only way they'll check before promising a customer a delivery date. Giving them a direct way to ask cuts the "can you check on this for me?" calls that interrupt the logistics team. The guide on stopping customers from calling to ask where their order is covers the customer side of the same problem.
Why customers usually stay on email or text
Customers want short, clear updates: shipped, delayed with a new date, delivered. Email gives them something to forward; text works for appointment confirmations and delays on the day. Most companies don't want customers chatting with an internal tool, and customers rarely want to join a supplier's chat workspace. Keep customer messages one-way unless the company chooses otherwise, and make sure replies reach a person.
Why carriers are a separate world
Carriers have their own systems and habits. Larger carriers send status by API or EDI. Many others work by email and phone, especially for tenders, rate confirmations and POD requests. Carrier communication should run on the carrier's channels, and the result should come back to the same load the team and customers see.
How do you keep one shipment record when conversations are spread across channels?
Keep one record by tying every message to a load reference and writing every decision, update and change to the load itself, not to the thread where it was discussed. The conversation can happen anywhere. The record lives in one place.
Threads drift; records don't
Chat threads are good for quick questions and bad at being the final word. Three things go wrong:
- Answers go stale. A Slack message at 9:00 says "ETA 2 pm." At 11:00 the carrier pushes to 5 pm. The 9:00 message is still sitting there, and someone reads it at noon.
- The same question gets different answers. One person checks the carrier's website, another checks an email from dispatch, and they post different times in different channels.
- Decisions get lost. "Fine, book the second carrier" in a Teams thread is an approval. If it doesn't reach the load, the invoice audit later can't see it.
The fix is not to ban chat. It's to treat chat as the front door and the shipment record as the room where things are decided.
Every message needs a reference
An agent can only attach a message to the right load if the message carries something to match on. Encourage, and set up the agent to ask for, one of these:
- Sales order or PO number
- Load number or BOL number
- Carrier PRO number
- Customer name plus ship date, as a last resort
If the message has none, the agent should ask: "Which order do you mean?" Guessing between two loads to the same customer is how wrong answers start.
What gets written to the record
| Message type | Example | What goes on the load |
|---|---|---|
| Status question | "Where's PO 5520?" | The question, who asked and the answer given, with its source and time |
| New information from the team | "Customer says dock closes at 2 pm Friday" | The updated receiving hours, flagged for the carrier |
| Approval | "Yes, book the $2,150 option" | The approval, the approver, the amount and the time |
| Change request | "Push delivery to Monday" | The request, who asked, and the result of asking the carrier and receiver |
| Customer reply | "Can you deliver before 10?" | The request, routed to the load owner if it changes the booking |
| Carrier update | "Driver delayed, new ETA 5 pm" | The new ETA, the reason, and who was told |
Once these are on the load, anyone asking later in any channel gets the current answer, not an old screenshot.
A hypothetical day with one record
Back to the building-supply distributor. With every channel feeding one record:
- 9:10 am: The carrier emails a new ETA for the Reno delivery. The agent updates the load and posts it to the customer service Teams channel because that branch is on the watch list.
- 11:30 am: A sales rep texts asking about the Reno delivery. The agent replies with the new ETA it already has, not the old one.
- 1:15 pm: The customer emails asking for delivery before 3 pm. The request goes to the load owner, because it changes the delivery appointment.
- 1:40 pm: The load owner approves a call to the receiver in Slack. The agent contacts the carrier and the receiver, and the result goes back on the load.
- 2:05 pm: The plant manager calls to ask which trucks are still due at dock 3. The answer comes from the same record.
Five channels, one set of facts.
What can people ask an AI logistics agent, and what needs approval wherever it's asked?
People can ask for status, documents and routine actions from any channel, but anything that spends money, changes a commitment or touches a carrier relationship needs the same approval no matter which channel it comes through. The rule is authority by person and by action, not by app.
Sort requests into three groups
Answer right away. Status, ETA, POD, BOL copies, delivery appointment, which carrier is on the load. These are lookups. Any authorized person should get the answer in the channel they asked in.
Act within the rules. Request quotes for a new order, book within the lane's approval limit with an approved carrier, schedule a pickup, send a delay notice to a customer if configured. The agent can do these when the request comes from someone allowed to ask and the action fits the company's rules.
Route to a person. A rate above the limit, a carrier the company hasn't approved, a change to the delivery address, a request to waive or accept an accessorial, a credit or claim. These go to the person who owns that decision, with the context attached, even if the request came in by WhatsApp from a senior manager.
Who can ask for what
| Request | Logistics team | Sales and customer service | Plant and warehouse | Customers |
|---|---|---|---|---|
| Status, ETA, POD | Yes | Yes | Yes | Updates on their own orders, if configured |
| Request quotes | Yes | Yes, routed to logistics if outside rules | Rarely | No |
| Book within limits | Yes | Depends on company rules | No | No |
| Change delivery date or address | Yes, with load owner review | Request only, reviewed by load owner | Request only | Request only |
| Approve a rate above the limit | Named approvers only | No | No | No |
| Add a new carrier | Named approvers only | No | No | No |
The exact grid is the company's choice. The point is that it exists before the first message arrives, and that the agent applies it the same way in every channel.
Watch for approvals that only look like approvals
Chat makes it easy to say yes casually. A thumbs-up emoji on a message, "sounds good," or "do what you think" in a busy thread can look like approval. Decide what counts. A good rule: approvals must name the action and the amount ("approve $2,150 with the second carrier"), come from a named approver, and be written to the load. Anything else gets a follow-up question, not a booking.
Phone calls need the same discipline
Phone calls are fast and leave no written trail unless someone writes one. When a team member phones in a request, the request and the outcome should still go on the load. If a phone conversation produces a decision, such as moving a delivery, confirm it in writing to the person who asked.
What mistakes make chat channels noisy or risky for freight?
The most common mistakes are sending every update to everyone, mixing outside contacts into internal spaces, and letting decisions live in threads instead of on loads. Each one is easy to avoid if it's decided before rollout.
Mistake 1: One channel for everything
A single "#freight" channel that gets every pickup, every ETA, every POD and every exception becomes a wall nobody reads. Split by purpose: one place for exceptions that need a person, one for approvals, and leave routine updates on the record where people can look them up. The guide on whether the alert reached the right person covers how to decide which events are worth a notification.
Mistake 2: Alerts without an owner
An alert posted to a channel of twelve people often gets read by twelve and handled by none. Each alert type should have one named owner and a backup. If the owner doesn't respond by a set time, it goes to the backup.
Mistake 3: Outside contacts in internal spaces
Inviting a customer or a carrier into the team's Slack or Teams workspace seems friendly. It also means they can see what the team says about rates, other customers and other carriers. Keep outside contacts on outside channels.
Mistake 4: Personal numbers as the only link
A sales rep who gets freight updates on a personal WhatsApp creates a gap when the rep goes on vacation or leaves the company. Make sure every exchange is written to the load, so the history doesn't leave with the phone. The article on who owns the unanswered carrier email when a coordinator leaves covers the same risk from the inbox side.
Mistake 5: Assuming every channel is switched on
Channel options in a settings screen are not the same as working connections. Before telling the sales team "just text the agent," confirm the number, who is allowed to use it and where replies go.
Mistake 6: Different answers in different places
If customer service reads the carrier website and sales reads a chat message, they will give customers different dates. Point everyone to the same answer: whatever is on the load.
A setup checklist before rollout
| Decision | Questions to answer | Owner |
|---|---|---|
| Channels per audience | Which channels for the team, sales, plant, customers and carriers? | Logistics manager |
| Who can ask what | Which requests each group can make, and which need approval? | Logistics manager with finance |
| Approval format | What words, amounts and approvers count as an approval? | Finance and logistics |
| Alert routing | Which events go to which channel, with which owner and backup? | Logistics manager |
| Customer messages | Which updates customers get, through which channel, and who handles replies? | Customer service lead |
| Reference rules | Which numbers people must include, and what happens when they don't? | Logistics team |
| Personal devices | Whether personal numbers or apps are allowed, and how history is kept | IT and logistics |
| Review | Who checks after the first weeks whether channels are noisy or quiet? | Logistics manager |
For the onboarding side of the same setup, including how the agent learns company rules, see how Wilson communicates through email, Slack, Teams, phone or text and learns your SOPs.
How does Wilson, by Cartage, work across Slack, Teams, WhatsApp, text and email?
Wilson, by Cartage, is an AI logistics agent that people reach by email, Microsoft Teams, Slack, WhatsApp, text or phone, that works with carriers by phone, email and text, and by API or EDI where the carrier supports it, and that keeps every exchange on the shipment record. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
Cartage positions Wilson as a free logistics department: what big shippers build over years, Wilson does from day one. Each of its four parts shows up in how channels work.
The labor
The labor is the work behind each answer. Wilson does the work start to finish, from the first quote to the final POD: quotes, bookings, paperwork, tracking and carrier follow-ups, by email, phone calls, texts, Slack and Teams. When someone asks where a load is, Wilson checks the best source available for that load: the carrier's API or EDI, GPS or ELD data where the carrier shares it, the carrier's website by PRO number, or email and phone calls when nothing else is current. When the answer needs a carrier's input, Wilson asks the carrier. The team doesn't chase carriers.
The data
The data is what keeps the answers consistent across channels. Wilson keeps every order, load, quote, rate, document and contact on record as it works, connected to the company's ERP. Every message, confirmation and change is kept in the shipment's change history, so a question in Teams and a question by text get the same answer. Wilson also keeps memories and rules, learned from its own work or added by the team, such as "the Reno branch wants delay notices by text" or "this receiver only takes deliveries before noon," and the team can edit them. 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.
The network
The network sits behind quote requests from any channel. Wilson's network includes carriers and brokers, and the shipper's volume counts with every other Wilson customer's, which can bring better freight rates on its lanes. The company still approves who hauls its freight. A sales rep asking for a quote by text gets prices from carriers the company has approved, compared on total cost.
The payments
The payments keep approvals made in chat tied to the money. Wilson audits every freight invoice against the load before money moves, then pays carriers from the Wilson Wallet. Invoices over the rate or outside the rules wait for a person. An approval given in Slack is on the load, so the audit can check the invoice against it.
Channels by audience with Wilson
| Who | How they reach Wilson or hear from it | What Wilson does with the exchange |
|---|---|---|
| Logistics team | Slack, Microsoft Teams, email | Posts exceptions and approval requests; records decisions on the load |
| Sales, customer service, plant | Teams, Slack, WhatsApp, text, phone, email | Answers status and document questions; routes requests outside the rules to the load owner |
| Customers and consignees | Email or SMS where configured | Sends updates the company has set up; routes replies that change a booking |
| Carriers | Phone, email and text; API or EDI where the carrier supports it | Tenders, confirms, tracks, requests PODs; records every message |
Wilson starts with assisted execution. The company sets approval limits and decides who can ask for what; routine actions can run automatically within those rules as the workflow is proven. Wilson's channels are email, Slack, Microsoft Teams, SMS/text, WhatsApp and phone. It writes in several languages, phone calls have English and Spanish support, and it can be set to answer the team in Spanish while writing to US carriers in English. Wilson handles LTL, FTL, ocean, drayage, parcel and cross-border freight. It is not a freight broker or a customs broker.
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
Can we talk to Wilson on Slack, Teams or WhatsApp?
Wilson, by Cartage, an AI logistics agent, can be reached by email, Microsoft Teams, Slack, WhatsApp, SMS/text or phone, with Spanish support for phone calls. Every exchange is kept in the shipment's change history, so the answer is the same whichever channel someone uses.
Should customers message an AI logistics agent directly?
Usually through email or text, and only for their own orders. Most companies send customers one-way updates such as shipped, delayed and delivered, and route customer replies that change a booking to the person who owns the load.
How do carriers communicate with an AI logistics agent?
Through the channels carriers already use: phone, email and text, and API or EDI where the carrier supports them. Carrier messages are attached to the same load the internal team sees.
Can a salesperson approve a freight rate by text?
Only if that person is a named approver for that amount. Authority should depend on the person and the action, not the channel. An approval should name the action and the amount and be written to the load.
What happens if two people ask about the same shipment in different channels?
They should get the same answer, because both questions are answered from the shipment record, not from a chat thread. If the answer changes, the record changes, and anyone asking later sees the new version.
How do we stop freight alerts from flooding Slack or Teams?
Send only exceptions and approvals that need a person, give each alert type one owner and a backup, and keep routine updates on the load where people can look them up.
Is it safe to add carriers or customers to our internal chat workspace?
It's risky. Outside contacts can see internal discussion about rates, other customers and other carriers. Keep them on email, text, phone, API or EDI, and keep the internal workspace for the team.
What reference should people include when they ask about a load?
A sales order or PO number, load number, BOL number or carrier PRO number. Without one, the agent should ask which load is meant instead of guessing between similar shipments.
Does Wilson replace our team's chat tools?
No. Wilson works inside the channels the team already uses. It replaces the TMS for freight execution and connects to the company's ERP, while people keep talking in Slack, Teams, email or text.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai
- Cartage, The data: https://cartage.ai/data
Let's review where your team talks about freight today. You don't need to prepare anything: Cartage maps the workflow with you on the call.
