TreeBossPro Blog — Crew Dispatch & Routes

Two-Way Customer Texting on Tree Dispatch Days

Customers text. They text to say the gate is unlocked, to ask if the crew can also look at the maple out front, to say they need the driveway back by 3, and to ask whether today is still on after last night's rain. On a busy dispatch day, those texts are either a mess scattered across personal phones or a useful stream of information in one place.

Following Routing Estimate Consults Around the Working Tree Crews, this article covers two-way texting on dispatch days and how to keep it from becoming chaos.

Why Texts Beat Calls on Service Day

Phone calls on service day interrupt everyone. The office has to answer, the crew lead may need to be reached, and a climber in a tree cannot pick up. Texts are asynchronous. The customer sends it when it suits them, and the office handles it when it can.

With two-way texting in TreeBossPro, customer replies land with the office, tied to the customer. That means anyone in the office can see the conversation and answer it, instead of it living on one person's phone.

Pair It With Crew Alerts

The crew's one-tap on-the-way and arrival alerts start a lot of conversations. A customer gets the on-the-way text and replies that the side gate is open, or that the car will be moved in ten minutes. Because those replies come back to the office, the dispatcher can pass along what matters.

Customers choose which alerts they receive, so the texts go to people who want them. That cuts down on the annoyed replies you get from blanket messages.

Handle the Common Requests

A few kinds of texts come up again and again on dispatch days:

Access updates. "Gate code changed" or "use the back alley." Update the crew notes on the property immediately so the crew and every future visit has the right information.

Timing requests. "Can you come after 1?" Check the route and see if the order can shift. If it can, change it on the board so the crew app reflects it.

Add-on work. "While you are here, can you look at the oak in front?" That is a sales opportunity. Log it as a lead or have the crew lead take a look and the estimator follow up with an estimate.

Weather questions. "Are you still coming?" A quick answer prevents a lot of worry, and the live crew map in the customer app answers much of it on its own.

Keep It on the Record

Texts that live on a crew lead's personal phone disappear when that person leaves the company. Texts in the system stay with the customer. When a dispute comes up later about what was agreed, or a new office person needs to know the history, it is there.

That is also why access details from texts should be copied into the property notes. The text is the conversation. The note is the record the crew uses.

The same goes for scope changes. If a customer texts asking the crew to leave the larger rounds for firewood instead of hauling them, that changes the job. Update the crew notes, and if it changes the price, make sure the invoice reflects it. A text thread that says one thing and an invoice that says another is how small misunderstandings become payment disputes.

When a text calls for the crew to change something mid-job, keep the relay short and clear. The crew lead needs the change, not the whole conversation.

Automated Messages for the Routine

Not every message needs a person. Automated texts and emails handle routine communication like appointment confirmations, estimate follow-ups, and invoices. That frees the office to spend its texting time on the conversations that actually need a human.

Set Office Habits

Two-way texting works best with a few simple rules. Someone owns the inbox during working hours. Customer texts get a reply within a reasonable time. Anything that changes the job, such as access, timing, or scope, gets updated in the system right away, not remembered for later.

With those habits, texting becomes one of the smoothest parts of tree crew dispatch software. Customers feel heard, crews get the information they need, and the office is not chained to the phone.