Support and sales platforms sell ten use cases: order status, FAQ, callback, voicemail, appointments, support, voice agent, survey, lead qualification, and outbound. On a Mexico–U.S. yard that is not a call center: it is four jobs that must write the TMS and open a ticket.

support and sales, not a TMS
10 uses
sell, schedule, document, collect
4 jobs
if it breaks, someone owns it
Ticket

Cluster: tools · AI worker · voice.

Ten AI use cases in the operation (from the call to the file)

We do not publish ten thin landings. The map fits in one view. Each use case translates to freight, not to generic support software.

Sales

Lead qualification · outbound

Scheduling

Order status · callback · appointments

Voice / docs

Inbound voice · voicemail · POD

Support + Finance

FAQ · tickets · survey · invoice

Ten operations use cases. Four freight jobs. Do not buy a support pack as if it were a TMS.

Honest ranking, not a vendor top 10: (1) sales that create the booking in the TMS, (2) scheduling that rewrites the appointment, (3) voice and documents that paste the ID, (4) support that opens a ticket and Finance that holds. If the use case leaves no file, it is 24/7 theater. What the SERP does not say: ten chats do not cover a Bajío–Laredo trip.

Sales: qualify and go find capacity

Lead qualification in freight is a load request: lane, unit, date, fraud risk. Outbound is reactivating inactives and chasing capacity, not a “closers” call center. If it does not create the booking in the TMS, it is a star-rating CRM.

On the corridor the request arrives on WhatsApp: Bajío–Laredo, dry van, date, fraud risk. The worker qualifies, writes the booking in the TMS, and opens a ticket if the carrier does not cover. The lead-scoring listicle does not publish how many Monday requests left no trip ID.

Scheduling: status, callback, appointments

Order status is “where is my shipment”: see, write the ID, and act (move the appointment or open a ticket). The visibility glossary is already in shipment tracking; the see-vs-do thesis is in visibility vs execution.

Callback is rescheduling a call to the dock, the customer, or the carrier with the same ID. Appointment scheduling is the dock window: KPI in on-time appointments and the cost of no-show.

A callback without an ID is 24/7 theater. An appointment nobody rewrote is detention. OTIF (on-time, in-full, measured for real) does not move on a pin. What breaks Monday is the no-show Finance pays as if it were real.

Voice and documents

Inbound voice, voicemail, and WhatsApp voice notes are the same job: hear, identify the ID, do it or open a ticket. Page: voice agent in logistics.

Documents (POD, Carta Porte, invoice) are not a support use case. They live in IDP (automatic reading of invoices, Carta Porte, and POD).

A WhatsApp voice note and a dock call are the same job. If they do not paste the ID, Finance has no file. The unpublished number: how many dock messages stayed in a loose chat.

Support, FAQ, survey, and Finance

Woman in operations with screens: freight support is a ticket with an ID, not a 24/7 chat
A FAQ for rates and yard hours, yes. An endless chat with no owner, no.
Use caseFreight translationTest
FAQRates, docs, yard hoursDeep-link the rate search, no invented price
SupportShipper / carrier ticketHuman owner
SurveyOTIF / incident after PODAfter the file, not instead of it
Support without a ticket is theater. Finance does not pay a survey.

Audit case (do not clone it as a support use case): 2,250 / $3.6M / 5.7%. The post-POD survey measures. It does not replace matching rate, CFDI, Carta Porte, and POD. Finance does not sign a form. The ticket is the product.

Scene: the shipper asks for status on WhatsApp. Ten support uses answer. None moves the appointment or holds the invoice. The job that pays on Monday is the one that writes the TMS. A 6–8 week pilot on one corridor. If the pain is freight, 5–7% at 100%.

Related reading

Key takeaways5 points
  1. Ten operations use cases (from the call to the file). Four freight jobs.
  2. Status = see + write + act. Voice = ID or ticket.
  3. FAQ and survey do not replace Finance.
  4. 6–8 week pilot on one corridor. 5–7% pattern if you audit 100%.
  5. OCL is not a contact-center vendor.

Does the support pack fail to say who covers the trip?

In 30 minutes we map your real use cases to TMS, ticket, and file.

Frequently asked questions