Follow Every Load in Your Team's Slack

Updated 4 days ago

Connect Slack and every update TrackFlo records on a load posts as a reply in that load's Slack thread, so sales, account managers, and tracking see the same story without anyone copying updates between tools. Teams tell us they're tired of having to live "in multiple screens." Your team starts a thread the way it already does, by posting the load number in a channel, and we post each update under it until the load delivers.

What you need

The Admin role in TrackFlo, and permission to add apps to your Slack workspace.
The Slack channels where your team already talks about loads.

Set it up

Connect Slack

In Settings > Company Settings, open the Integrations tab and select Add to Slack. Sign in to Slack and approve. The card then reads Connected with your workspace name.

The Integrations tab with the Slack card reading Connected

Invite the bot to your load channels

In each channel, type /invite @TrackFlo. When it joins, it reads the channel's last 15 messages and links any loads they name, so threads already in progress pick up updates too.

Post the load number

Post a new message in the channel that includes the load number exactly as it appears in your TMS. That message becomes the load's thread. If several messages name the same load, the newest one wins.

Each reply shows the update type and a link to the load in TrackFlo, plus the city and state, the ETA, and the comment on a second line when available. Updates stop once the load is delivered.

When it doesn't go to plan

I posted the load number and nothing happened

The bot wasn't in the channel when you posted, and the message is older than the last 15. Post the load number again as a new message. Thread replies and edited messages don't start a thread.

Only some of my load numbers link

The number has to match the TMS load number exactly. A partial number, or one with extra characters, doesn't link. Multi-leg loads also link from the leg number, such as the load number followed by -2.

A message from a partner in a shared channel didn't link

Only messages from people in your own Slack workspace start a thread. Keep in mind that replies in a shared channel are visible to everyone in it, including the other company.

Updates stopped posting

The load delivered, the bot was removed from the channel, or Slack was disconnected. If the bot was removed, reinvite it with /invite @TrackFlo. If Slack is disconnected, the Integrations card shows Disconnected and you can select Add to Slack to reconnect.

Measure it

Load threads in Slack carry TrackFlo replies through delivery, and "any update on this one?" messages in those threads fall.
Account managers stop asking trackers for status, because the answer is already in the thread.

Answer "Where's My Freight" Before the Customer Asks

Public load pages, exception alerts, and reports that put the answer in front of the customer first.

Read recipe

Keep a Full Audit Trail on Every Load

Every update, message, and handoff on the load, timestamped and attributed.