Docs

Message Center Explained

How a dispatch message actually routes: broadcast to driver and customer, @driver for the driver only, a specific @username, and what changes with no dedicated number.

Published

The Message Center (/app/message-center) is where a dispatcher reads and sends the SMS conversation attached to a delivery ticket, and where a driver's in-app notes to dispatch show up. It has three tabs: Tickets (customer/driver conversations, the subject of this article), Operators (internal team chat, see Operator Chat explained), and Archived.

Opening a conversation

The Tickets tab lists every delivery customer you have an SMS thread with, most recent first. Click one to load its history in the centre column. A conversation is keyed to the customer's phone number, so it carries messages across every ticket that customer has ever had with you, not just the newest one.

What happens when you send a message, and why the wording matters

Type in the compose box at the bottom of an open conversation and press send. What actually happens depends on what you typed:

  • Plain text, no tag — a broadcast. The assigned driver gets a free push notification into the driver app, and the customer gets a text message through your account's dedicated number.
  • Contains @driver — routed to the driver assigned to this ticket only. The customer is not texted at all. The tag itself is stripped before anything is sent or stored, so neither party ever sees the literal word "@driver". If no driver is assigned yet, the send is refused outright with a message telling you to assign one first — it does not fall back to texting the customer instead.
  • An @username that matches one of your drivers — routed to that specific driver only, the same way @driver is, even if they are not the driver currently assigned to the ticket. This is the older mechanism and still works; @driver is the simpler form Zippykind now teaches for the common case of reaching whoever is already on the ticket.

The hint text under the compose box says this directly: "Include @driver tag to send a message to the assigned driver only. Otherwise the driver and customer will both receive the message."

Accounts without a dedicated phone number

Sending SMS through a shared, non-dedicated number is worse than not sending at all — the customer's reply would land on a number this account does not own and never thread back into this conversation. So if your account has no dedicated virtual number, the customer leg of a broadcast is skipped automatically and only the driver is pushed to; you do not need to remember to tag @driver yourself. If there is also no driver assigned to the ticket, the send is refused, because there would be nobody left to reach at all. Request a number from Get Help under "Get Dedicated Phone Number".

The billing disclaimer, and what an SMS actually costs

The first time any operator on your account sends a message, a one-time disclaimer modal appears and must be agreed to before the send goes through; the agreement is recorded per operator and is not asked again after that. It states plainly:

  • A broadcast (no tag) sends one SMS to the customer and a free push to the driver — 1 SMS billed per broadcast.
  • A tagged or @username message sends only a push notification — 0 SMS billed.
  • Inbound replies from customers and outbound SMS your drivers send also count against your account's usage.
  • 1 SMS is 140 characters. Longer messages split into 140-character chunks and are billed per chunk — 280 characters is 2 SMS, 420 is 3, and so on.

Tagging works from the driver's side too

The reverse tag exists for a driver replying from the app: including @operator or @operators in a note sends it to dispatch only, and it is never texted to the delivery recipient. Same idea as @driver, opposite direction, and the tag is stripped the same way before storage.

Archiving is per operator, not account-wide

The archive icon on an open conversation moves it to your own Archived tab. This is recorded against your operator login specifically — archiving a conversation does not remove it from a colleague's active list, and a colleague archiving one does not remove it from yours. Reopen it any time from the Archived tab and press Unarchive to reply; you cannot type into an archived conversation's compose box until you do.

Starting a new conversation: the Send Message modal

Press the + icon in the page header to open Send Message in Ticket mode. Filter by driver, date and location, or search by ticket number, name, address or order id, then pick the ticket the message is about. It sends through the exact same routing rules described above — there is no second, different send path for messages started this way.

Why this matters for compliance

Every message sent through @driver, a driver @username, or an account with no dedicated number, is marked internally as reaching only one party, never the delivery customer. That marker is what Exclude Internal Messages on the Compliance Export PDF filters on when it is turned on — it is the mechanism that setting relies on, not a separate system.