Your plumber’s drivers do not carry a laptop into a crawl space. If your automation lives only in a chat window, the people doing the physical work will never open it.

On October 13, Samsara made Agent Studio, its no-code agent builder for physical operations, available to every customer. The company’s own announcement says voice agents passed chat in interaction volume within four weeks of launch and have led every week since. It also reports that about 75% of organizations using voice agents increased their weekly usage after they started, and more than half at least doubled it.

Treat those as Samsara’s own numbers. The company picked the metric, counted the sessions, and wrote the release.

The fine print changes the story a little

FreightWaves asked Samsara some follow-up questions, and two answers matter. First, most of the voice interactions so far are calls the agent places on its own, set up by the businesses using it. A system that calls drivers when a truck crosses a geofence will rack up sessions faster than an office manager ever could by typing into a dashboard. Second, Samsara said more than 1,000 organizations use its agents weekly, but did not say how many of them use voice. The 75% figure has no denominator anyone outside the company can see.

So this is not proof that workers prefer talking to software over typing. It is closer to proof that an agent gets used when it shows up where the work actually happens.

Why the direction still holds up

Samsara’s own example: a truck crosses a geofence around a job site it has not visited before. The agent calls the driver and explains which entrance to use, where to park, the yard speed limit, and what safety gear is required. The driver can ask questions back. When the truck leaves, the agent captures what happened on the visit.

The driver never opens an app. Their hands stay on the wheel, which matters because federal rules bar commercial drivers from holding a phone while driving but allow hands-free use, as FreightWaves points out.

Most automation projects assume someone is sitting at a keyboard. For an office team, that is a fine assumption. For a plumbing crew, an HVAC tech on a roof, or a driver between stops, it is the assumption that kills adoption before the tool ever gets used. Samsara’s own product chief, Johan Land, put the split plainly in the release: in the back office that happens through chat, on the road it happens through a phone call.

Where voice tends to fit for a crew

A few places worth a look if your people work with their hands:

A call before a crew arrives at a new site, with access notes and safety requirements already covered. A short call at the end of a job that captures what happened and turns it into the report nobody wants to type. A line techs can call at 9 p.m. with a policy question instead of waking up a manager.

None of these need a fancy model. They need the agent to know your schedule, your sites, and your rules, and to trigger on real events instead of waiting to be asked.

Two cautions. Outbound calls can turn into noise fast, so measure whether the work actually got easier, not just how many calls went out. And be careful about copying a vendor’s adoption numbers into your own plan. Samsara counts sessions. You should count hours saved and mistakes avoided.

Sources

Kush AI Automation builds voice agents for businesses whose crews work away from a keyboard. Get in touch if a phone call is the right interface for your team.