For logistics and dispatch

A load moves on a dozen phone calls. Keep all of them.

Detention, a reschedule, a driver at the gate, all while dispatch is on another line.

A dispatcher in a small freight office, headset on, working through a whiteboard of routes.

The next shift reads it

What happened overnight is under the load, in the words it was reported in.

Detention, in writing

The accessorial agreed at four in the morning exists as a line with a date on it.

The desk, not a cell

A driver does not have to know which dispatcher is on shift tonight.

The cost

The money leaks in what was said, never written down.

It exists only in the head of whoever answered, and that person goes off shift.

24/7

the line is live — a call at four in the morning reaches the assistant and comes back written out under that customer.

The product

What the desk actually gets

Three calls at once

Dispatch is single-threaded: one person, one line, and behind it a reschedule and a load falling apart.

One dispatch number, answered from whichever seats are staffed

The rest of the desk can see it was picked up, and by whom

Nothing sits in a queue behind the longest call on the floor

The sentence that agreed the accessorial

Detention, a layover, a reconsignment — the money on a load is decided in a sentence somebody says on the phone.

Who agreed what, on which load, at what time

Kept in the words it was said in rather than tidied into a paraphrase

Sitting under the customer, so a dispute starts from a record and not a recollection

English runs out at the gate

Much of this workforce is not working in its first language, and the hardest call comes from a yard at 4am.

Rendered as they speak rather than mailed over as a transcript afterwards

Both directions, so the answer goes back in the language they called in

The whole exchange stays in the load’s record like any other call

Your week

The week this actually fixes

Two more calls come in

Calls ring everyone on shift instead of queueing behind one person. The desk sees it handled.

4am, at a closed gate

The call is written up on its own: which load, what happened, what was agreed.

A broker disputes the detention

The conversation sits under that customer with what each side committed to. A record, with a date.

That dispatcher is off shift

Everything sits under the load and the customer, visible to the whole desk.

Any size

One truck, one desk or several terminals

The product is the same in all three. What changes is how many phones the line rings, and who is expected to pick up.

Owner-operator or a small carrier

You are the driver and the desk. The assistant takes the broker call while you move.

A dispatch desk on shifts

The line rings whoever is staffed. The record is the handover: night reads what days wrote.

Several terminals

A local number for each, and one record per customer rather than three versions of it.

The fine print

What this is, and what it is not

Your money is decided on conversations, and a phone system is no place for a regulated file.

Off unless you turn it on
The call that agreed detention is the one worth having. Where a state requires everyone’s consent, both sides hear an announcement that cannot be disabled — and an interstate call can touch two states with different rules.
It is not your compliance file
Driver qualification files, hours-of-service records and DOT paperwork have their own retention rules. qallin keeps conversations — never let a call summary stand in for a record a regulator will ask for.
Texting drivers has to be registered
US carriers filter unregistered business messages, so a gate update quietly does not arrive. We file the A2P 10DLC registration, and until approval texting does not work.
It cannot dial 911
qallin runs alongside the phone in the cab, not instead of it. A driver reporting an accident uses the device’s own dialer.

Switching

Coming from something else

Porting is free and the line keeps working, so the number every broker has stays.

Straight answers

Set hours per line and route out of hours to whoever is on call. When nobody can take it, the assistant captures which load and what happened, and the desk picks it up.

Not directly — no TMS is on the integration list, and we would rather say that than let you find out. Call summaries go onward by webhook, or through Zapier or Make, with the fields mapped to what your system expects. It is a push from us, not a rummage through your data.

They call your number like they do today, from any phone. Only your team needs the app.

Yes. Every call shows who answered, how long it ran and what came of it, across the whole desk.

Yes, and porting is free. The number in every rate confirmation and every carrier packet stays exactly the same.

Waitlist

Run the load, not the recollection.

Every call under the load, every agreement written down, whoever picked up.