Skip to main content

How to View the Messaging Log

The Messaging Log shows all messages sent for a shift, including delivery status. This article explains how to access and interpret the log.

Open the Messaging Log

Navigation:

MMS > Dispatch > Dispatch Board

  1. From Scheduled Shifts & Dispatch, click the shift date to open the dispatch order.

  2. In the dispatch order panel, click Messaging.

  3. Click View Message Log.

The Messaging Log will open in a list format.


What You Can See in the Log

Each message entry shows:

  • The message content

  • The date and time sent

  • The sender

  • The delivery method (email, text, or both)

  • Delivery status for each recipient


Delivery Status Icons

  • Sent: The message left FleetWatcher.

  • Delivered: The message was delivered to the carrier or email address.

  • Failed: The message could not be delivered.

If a message fails, verify the recipient’s contact information.


Message Icon Color Coding

  • Green Icon: Indicates the user has successfully received an email or SMS.

  • Red Icon: Indicates an invalid or "random" phone number.

  • Yellow/Orange Icon: Indicates the phone number is part of the SMS Suppression/Do Not Disturb (DND) list.

Understanding the Yellow/Orange Icon

The icon turns yellow/orange when a user has opted out of receiving messages. This status is triggered by:

  • Manual Opt-Out: The user replied to a dispatch text with a keyword such as STOP, QUIT, UNSUBSCRIBE, or CANCEL.

  • System Suppression: The system received a "DND" or "Invalid Delivery" status from our provider (Plivo) and added that number to our global suppression list to protect our sender reputation.

Hover Text: When hovering over a yellow/orange phone icon, the following message appears: "Source Number Blocked by STOP from Destination Number".

How to Fix It

To change the icon back to green (active), the user must explicitly opt back in by texting START, YES, or UNSTOP to the dispatch number.

Note: For compliance reasons, we cannot manually override this from the backend to resume texting; the carrier requires the end-user to initiate the re-opt-in.

Did this answer your question?