Buyer’s guide
The difficult day test
Every demo goes well, because every demo is a good day: three stops, full signal, a customer who agrees with the invoice. Run this instead. Seven steps, in order, on any product you’re considering — including this one. Do it in a trial, on real jobs, with a real driver holding the phone.
Seven steps, in order
Run it in a trial, on real jobs, with a real driver holding the phone.
Step 01: Turn the phone to airplane mode, then finish a job
Two photos, a signature, complete the stop. Then turn the radio back on and watch what happens. Do it standing in the yard where you can see the screen.
✓ What good looks like
The stop completes. Something on screen says, in words, that it’s waiting to send. It sends itself later without anyone tapping anything.
◆ What should worry you
A spinner. A retry dialog. “Please check your connection.” Anything that makes the driver responsible for the network, or loses the job when the upload fails.
Step 02: Photograph a scale ticket and time how long until it’s on an invoice
Not “can it store the photo” — how many minutes of somebody’s time between the picture and a billable line with the right arithmetic on it.
✓ What good looks like
Under a minute in the office, the photo visible beside the numbers, the overage sum shown before it’s charged, and the picture attached to the line afterwards.
◆ What should worry you
A photo gallery with no path to billing. Re-typing weights into a second system. Or a total with no visible sum — you can’t check what you can’t see.
Step 03: Book an exchange and count how many jobs appear
Drop an empty, take the full one, same visit. Look at the board, then look at the driver’s phone.
✓ What good looks like
One job with two sides, each side with its own container, its own allowance and its own rate.
◆ What should worry you
Two separate jobs you have to keep in step by hand. That’s how a ticket gets billed against the wrong side, and it never stops happening.
Step 04: Read the driver reviews, not the buyer reviews
Look the product up where the office buys it, then look up the same name in the phone app stores. Read the one-star reviews specifically, and read the replies.
✓ What good looks like
Two scores in roughly the same place, and replies that name a fix with a date on it.
◆ What should worry you
A wide gap between the two — about 4★ from purchasers, under 3★ from drivers. Your crew will write the second review, and then work around the product.
Step 05: Leave a driver signed in overnight, then start at six the next morning
Also: lock the phone at a stop, take a call mid-job, put it in a pocket for twenty minutes. Then come back.
✓ What good looks like
Straight back to the route, still signed in, half-finished stop intact.
◆ What should worry you
A login screen at the first stop, or work lost from the interrupted job. Drivers report sessions dropping from twelve hours to seconds after an update — ask directly how long a session lasts.
Step 06: Stand in the sun with sunglasses and gloves on, and tell two statuses apart
Then press the complete button while something else on the screen is still loading. Watch whether it stays where your thumb expected it.
✓ What good looks like
Every state carries a word and a shape as well as a colour. Buttons are big enough for a glove and never move once drawn.
◆ What should worry you
Two statuses that are nearly the same colour and nothing else. A late banner that pushes “complete” down into where the camera button was.
Step 07: Ask for your data back, and ask what it costs to leave
Before you sign anything. Export your customers, your containers and your invoices, and see what you get.
✓ What good looks like
A file you can open, containing the photos too, available to you without asking a human. Month to month, cancel yourself.
◆ What should worry you
An export request that goes to support. A setup fee you’d forfeit. A twelve-month term for software you haven’t put in a cab yet.
How it works · 01
Bring a difficult day to every evaluation
Use the same synthetic day with each vendor: a delivery, an exchange, a full container going to disposal, a closed site and a recurring stop. Add a photo and a weight overage. Ask to follow the work into billing, then change the scenario. A prepared demonstration can show the happy path while hiding what the dispatcher must repair.
Smooth Hauling is built around individual containers, offline driver capture and ticket evidence connected to charges. Those are useful reasons to evaluate it, not proof that another platform lacks them. Public vendor descriptions are documentation, not independent hands-on tests. Ask each supplier to demonstrate the same acceptance steps in the edition you would buy.
How it works · 02
Compare cost and operating responsibility together
Record the subscription, capacity limits, payment fees, messaging costs, website services, onboarding and data migration work. Published prices make the comparison easier, but a flat subscription is not the entire cost of running the system. Ask who owns an accounting mismatch, an undelivered text or an offline phone that will not sync.
Smooth Hauling publishes truck-based plans and a trial. Provider-backed payments, communication and accounting need configuration. Managed websites/local SEO, native QuickBooks Desktop/Enterprise integration and division-scoped access remain expansion areas, not features to assume from a general “all-in-one” description. If one is essential, make it a pass/fail requirement before buying.
How it works · 03
Write down what would make you stop
Reject a trial result when captures disappear, a replay creates a second charge, a customer can read another account’s evidence or exported data cannot be reconciled. Record the exact edition, device and test date. A checklist signed off by your dispatcher, driver and bookkeeper is stronger evidence than a long list of feature checkmarks.
What it won’t do
This page is ours, so run the test on us as hard as on anyone. Public vendor descriptions, this one included, are documentation, not a hands-on result.
Check it in your trial
- Run the same difficult day in every shortlisted product.
- Disconnect the driver phone and reopen the app.
- Trace one overage and one customer dispute.
- Reconcile a sample export and the total operating cost.
Continue your evaluation
Run it on us first, so you’ve practised
Thirty days free, no card, no sales call. If we fail a step, we’d rather you found out now — and we’d like to hear which one.