What a contractor's mechanics taught us about requesting parts

We're piloting a new parts-request flow with a heavy-equipment contractor's team. Before rollout, their field lead handed his phone to his mechanics. Their reaction changed the feature.

What we are taking from it:

1. The field side should be two buttons, at most. The mechanics looked at a screen full of choices and said they just wanted one thing: the ability to add a request. On the call, we built a mechanic role that does only two things: create a parts request and send a ticket. The field lead called it much cleaner.
2. Text is the front door. Given options, the mechanics preferred texting. They wanted to open their messages, type the unit and what's wrong, and be done.
3. The photo is the request. They wanted to send a picture so the shop knows what they're getting into before anyone drives out. With Gearflow, that photo goes to a single number and becomes the request itself.

Their team rolls this out to the rest of their mechanics next. When they do, we'll share what changes.

Gearflow turns a text, a call, an email or a photo into a tracked parts, service, rental or equipment-move request.

Book a demo