Skip to content

Check-Call Chaser · Freight & Logistics

Stop loads going dark between check calls

Every 2 hours it finds in-transit McLeod loads overdue for a check call and drafts a short location-and-ETA text to each driver or dispatcher. One approval sends the batch.

Coming soon — waiting for McLeod (LoadMaster / PowerBroker) and Twilio approval $149 one-time · never renewsIncluded in Enterprise
Start free Get product updates

Can't be bought yet: waiting for McLeod (LoadMaster / PowerBroker) and Twilio approval. It opens for purchase on its own once approved.

  • Runs on a schedule
  • 1 AI step
  • A person approves before it acts
  • About 30 min to set up

Sound familiar?

The job, before and after this agent.

What it feels like today

  • “Loads go dark and the customer asks for an ETA before we have one.”
  • “Night dispatch spends the shift dialing drivers one at a time.”
  • “We don't notice a load has no contact number until it's already late.”

What you get with the agent

  • In-transit loads searched in McLeod every 2 hours, up to 50 per run, with recent check calls read.
  • Overdue loads picked by your check-call rules, inside your quiet hours.
  • A short location-and-ETA text drafted per load to the driver or carrier dispatcher's mobile.
  • One dispatcher approval for the batch; texts sent from your Twilio number.
  • Loads with no number listed for a manual call.

Before

2am. You scroll the board, spot six loads without a recent check call and start dialing.

After

A batch of six short texts is waiting. You remove one, approve the rest, and call the one load with no number on file.

How it works

The whole workflow, step by step.

Every 2 hours the agent searches McLeod for loads matching your in-transit filter and reads each load's recent check calls. AI compares them with your check-call rules and the current time, picks the overdue loads, finds the driver or carrier dispatcher's mobile number on the load and drafts a short location-and-ETA text for each, respecting your quiet hours. A dispatcher approves, edits or removes texts in Reviews and the approved ones are sent from your Twilio number; loads with no number are listed for a manual call. Replies arrive in Twilio and aren't written back into McLeod, and it doesn't use GPS or ELD data.

  1. TriggerEvery 2 hours
  2. App callFind in-transit loads in McLeod
  3. LogicEach in-transit load
  4. App callRead the load's recent check calls
  5. AI stepPick the overdue loads and draft the texts
  6. LogicAny texts to send?
    • Nothing to send:Nothing to send
    • Texts drafted:Approve the batch of texts
  7. OutputNothing to send
  8. Human approvalApprove the batch of texts
    • Approved:Each approved text
  9. LogicEach approved text
  10. LogicCheck before texting
  11. LogicText it?
    • Passes:Text the driver or dispatcher
    • Held:Held
  12. OutputHeld
  13. App callText the driver or dispatcher
  14. LogicCount what happened
  15. OutputTexts sent

This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.

  1. Step 1Every 2 hoursRuns every 2 hours (change the schedule and time zone on the trigger).
  2. Step 2Find in-transit loads in McLeodSearches McLeod for orders matching your in-transit filter (e.g. status P), newest first, up to 50.
  3. Step 3Each in-transit loadRepeats the check-call lookup for each load found (up to 50 per run).
  4. Step 4Read the load's recent check callsReads the most recent check calls (call-ins) McLeod has for this order.
  5. Step 5Pick the overdue loads and draft the textsAI compares each load's last check call with your rules and today's time, picks the overdue ones, finds the driver or carrier dispatcher's phone on the load and drafts a short ETA request for each.
  6. Step 6Any texts to send?When nothing is overdue (or no number was found) the run just records the check; otherwise the batch goes to review.
  7. Step 7Nothing to sendThe run history keeps the check and any loads with no phone number.
  8. Step 8Approve the batch of textsA dispatcher checks the drafted texts in Reviews, removes or edits any, and approves the batch to send.
  9. Step 9Each approved textChecks and sends the approved texts one by one (up to 50).
  10. Step 10Check before textingIn code: a real phone number, a message of at most 300 characters and no placeholders left after editing. Anything that fails is held, with the reason.
  11. Step 11Text it?Texts that pass the check are sent; the rest are held and listed in the run summary.
  12. Step 12HeldStopped by the check (no valid phone, too long or a placeholder left); the reason is in the summary.
  13. Step 13Text the driver or dispatcherSends the approved text from your Twilio number.
  14. Step 14Count what happenedIn code, not AI: lists every approved text as sent, held (with the reason) or failed, from what each step really did.
  15. Step 15Texts sentThe run history keeps the count of texts sent, held and failed, per load.

Example run

What goes in, and what comes out.

Example with fictional data

Comes in

Fictional run: 14 in-transit loads, three past your check-call window, one with no driver number on the load.

The agent produces

Three draft texts such as: Hi Luis, checking on load 20417. Can you send your current location and ETA to Atlanta? Plus a call list with the load that has no number.

What you need

Everything it takes to run it.

About 30 minutes from purchase to live. A checklist above the canvas takes you through each step.

Plan

Included in Enterprise; on other paid plans it's $149 once. Agents run live on paid plans, from Basic ($39/mo).

Your AI key

Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.

Apps

Checklist

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • McLeod API access (orders and call-ins) and a Twilio account with an SMS-enabled number.
  • Your in-transit filter and check-call rules.

Setup, about 30 minutes

  1. Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
  2. Connect McLeod. Connect your McLeod server (web services URL + user or API token) in Settings → Integrations → McLeod. The user needs access to orders and call-ins.
  3. Connect Twilio. Connect your Twilio account (Account SID + Auth Token or API key) in Settings → Integrations → Twilio.
  4. Set the McLeod connection and in-transit filter. Open “Find in-transit loads in McLeod” and “Read the load's recent check calls”, pick your McLeod connection in each, and enter the filter that selects in-transit loads.
  5. Write your check-call rules. Open “Pick the overdue loads and draft the texts” and replace the placeholder with your rules, quiet hours, company name and callback number.
  6. Pick your Twilio number. Open “Text the driver or dispatcher”, pick your Twilio connection and the number to text from.
  7. Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
  8. Switch the trigger on. Open the trigger, check the schedule and time zone, and switch it on. Assign the review step to your night and day dispatchers.

Is it a fit?

Who it's for, and what it won't do.

Built for

  • Brokerage track-and-trace teams
  • Night and weekend dispatch
  • Brokers running McLeod

What it doesn't do

  • Replies arrive in Twilio; they aren't written back into McLeod as check calls.
  • It doesn't use GPS, ELD or tracking-app data: only the check calls recorded in McLeod.
  • McLeod search filters and call-in fields vary by version: confirm the filter and call-in service with your McLeod admin.
  • It never texts without a person approving the batch. Texting consent and carrier messaging rules (A2P 10DLC) are your responsibility.
  • Whether a load is overdue is judged by the AI from your rules and the check-call times (hours, not calendar days), so the dispatcher's review matters.
  • Coming soon until McLeod and Twilio are approved.

We list the limits up front so you can decide before you buy.

Price

$149 one-time

Per workspace. It never renews.

Coming soon — waiting for McLeod (LoadMaster / PowerBroker) and Twilio approval
  • Included at no extra cost on Enterprise.
  • Buying and running it live need a paid plan, from Basic ($39/mo).
  • Dry Run costs nothing: simulated AI and app calls, nothing sent.
  • AI usage is billed by your own provider, at cost. No AI credits to buy from us.
Start free Get product updates

One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy

FAQ

Questions about Check-Call Chaser.

Which apps does it need?

McLeod and Twilio. Confirm your in-transit filter and call-in fields with your McLeod admin. The agent's page shows whether each app is ready to connect.

Do driver replies go back into McLeod?

No. Replies arrive in your Twilio inbox; enter the check call in McLeod as usual. It doesn't use GPS or ELD data, only the check calls recorded in McLeod.

Will it text drivers at 3am without asking?

No text goes without a dispatcher approving the batch, and it respects your quiet hours. Texting consent and A2P 10DLC registration are your responsibility.

Setup and cost?

About 30 minutes once the apps are connected. A one-time unlock that never renews; live runs need a paid plan and your own AI key, and Dry Run is free.

Are the drivers' replies saved in McLeod?

No. Replies arrive in your Twilio number's inbox; enter the check call in McLeod as usual (or forward Twilio replies to your team).

Does it use GPS or ELD tracking?

No. It works from the check calls recorded in McLeod and asks the driver by text.

Is this a subscription?

No. Check-Call Chaser is a one-time purchase of $149 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.

Can I test it before it touches real data?

Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.

Check-Call Chaser is almost ready.

Can't be bought yet: waiting for McLeod (LoadMaster / PowerBroker) and Twilio approval. It opens for purchase on its own once approved. Create a free account now and you'll find it on your Agents page.

Start free Get product updates