Find the dispatch contact before the driver needs it

Format: Demo script: TMS screen explainer.

Set the training task

Scene context: The reference is the approved driver-app sales-demo still, not a live phone connection.

Narrator: “A new driver should not have to search for the office contact when a trip question comes up. In this exercise, find the contact control and the trip reference you would give dispatch. We are reading a sales demo image. We are not placing a call or testing a phone connection.”

Find the trip context

Scene context: The full phone view is the reference. No tap or screen transition is demonstrated.

Narrator: “Near the top, the card labeled Current load shows LD-1042. The trip runs from Dallas to Houston. Below it are pickup, loaded, and delivery rows. These are demo details. The times and marks tell us what this image shows, not what happened on a live trip.”

Narrator: “For this lesson, remember the load reference. If you need help, a clear reference lets the office know which trip you mean. Reading a route name alone may not distinguish similar work.”

Locate the contact control

Narrator: “Below the trip steps are two controls. One says Navigate. The other says Call dispatch. Find Call dispatch with your eyes. Do not press anything in this exercise.”

Scene context: The still remains unchanged.

Narrator: “Look back to the current load card. Say the load reference, then point to Call dispatch. That is the practice task. Know which trip you need help with. Know where to start contact before a problem comes up.”

Rehearse the question

Scene context: The next passage is a hypothetical practice exercise, not an app result.

Driver: “I have a question about load LD-1042. The delivery instructions I received seem different from the trip details. Which approved instructions should I use?”

Trainer: “Good. You identified the trip and the conflict. You did not assume that one screen settles it.”

Narrator: “The practice ends there. We do not invent a dispatcher reply, a connected call, or a changed trip. A visible Call dispatch label does not tell us which number would be used, who would answer, or what happens without a connection.”

Prepare the real onboarding check

Scene context: The closing passage returns to what the unchanged still can support.

Narrator: “Before real use, the training lead must check where the control connects. Check the approved backup contact path too. Test the device and the connection conditions drivers will use. Do this before they depend on the service. Train when the driver is safely stopped, not while driving.”

Narrator: “The lesson has a simple goal. The driver should be able to name the trip and find the contact path. Passing that reading task does not prove that a call will connect.”

Close

Narrator: “Bring your driver contact and fallback requirements to Core Agentic. Use the TMS sales demo to discuss the phone handoff your operation needs. Book a Demo.”

Sources and scope

Core Agentic TMS and design context. The operating steps and fictional examples are first-party recommendations, not verified installed controls or customer results.