Picture a Tuesday. Your outside parts rep pulls into a fleet shop, and the shop foreman mentions, almost in passing, that they’ve started buying brake parts somewhere else. He isn’t upset. The other supplier’s rep just stops in more often.

By Friday, the call report for that stop says “Good visit.” Nobody at the parts counter hears about the brakes. Two months later, that fleet’s parts sales dip, and nobody can say why.

Keeping track of outside parts sales rep visits is hard, whether you run one store or a small dealer group. It isn’t a sign your reps are doing a bad job. This post covers what a useful visit record looks like, why notes go missing, and a simple way to tie each visit to the parts sales that follow.

Short answer

Ask for less, sooner. Agree on four things every visit note needs, let reps capture them right after the stop instead of at night, and get what they hear to the parts counter the same day. Then, once a month, line the visits up against each account’s parts sales from your dealer management system (DMS). That’s when you see which visits paid off.

What keeping track really means

Most parts managers don’t want a GPS trail or a count of stops. They want answers to three plain questions:

• Which accounts did each rep see this week?
• What did the rep hear while they were there?
• Did the account buy more parts after the visit, or less?

A stop count answers the first question. The second lives in the rep’s head, and the third lives in your DMS. Keeping track means getting all of it in one place.

Why visit notes go missing

It’s tempting to call it a discipline problem, but outside parts reps are on the road all day, and plenty of good ones aren’t app people. Here’s what tends to get in the way:

• The write-up happens at night, at the kitchen table, when the details are already fuzzy.
• The call report form was built for the office. It asks for fields the rep doesn’t care about and has no good spot for “they’re buying brakes elsewhere.”
• Notes land on the wrong account. One fleet with three yards, or a customer whose name is an ordinary word, and the note ends up where nobody looks.
• Nothing comes back. If a rep writes a good note and never sees it used, the next one gets shorter.

Asking harder won’t fix any of that. Making the note easier to write, and more useful to the person writing it, will.

What a good visit record looks like

A good visit record is short. It answers four questions:

1. Who did you talk to? A name and a role, like the shop foreman or the fleet manager.
2. What did you hear? A competitor’s price, a truck count going up or down, a supplier they’re trying, or a part they keep running short on.
3. What did you promise? A quote, a price check, or a part to track down.
4. What’s next? When you’ll be back, or who needs to follow up.

Here’s that Tuesday visit, written up this way:

Talked to the shop foreman. They moved brake parts to another supplier about a month ago. Price was part of it, but mostly the other rep stops in every week. Promised a brake price sheet by Thursday. Back next Tuesday.

That’s five short sentences. A rep can say it out loud in the truck before pulling out of the lot. And now the counter, the manager, and the rep a month from now all know what’s going on at that fleet.

A simple way to start tracking outside parts sales rep visits

You don’t need new software to begin. If your reps still turn in paper call reports on Friday, that’s fine. Start here.

1. Pick the 10 to 20 fleet and shop accounts that matter most to your parts sales, and start with those.
2. Agree on the four questions above with your reps. Ask them what’s missing. They’ll know.
3. Let reps capture the note right after the stop, while it’s fresh. A two-minute voice memo in the truck beats a perfect write-up at 9 p.m.
4. Put the counter in the loop. When a rep hears about a price or a part shortage, the counter should hear it that day.
5. Once a month, sit down with each rep and go through their top accounts: the visits, what they heard, and what each account bought. Let the rep go first.

That last step is where the coaching happens. Given the chance, a lot of reps will point out the account that slipped before you do. That conversation goes better than one that starts with a report.

How to tie visits to parts sales

This is the hard part. Your DMS knows what sold. Your reps know what happened on the visit. The two rarely sit side by side.

The manual way works. Export each account’s parts sales from the DMS, put them in a spreadsheet next to the visit notes, and look for the gaps. It’s a lot of copy and paste, but it’ll show you something.

That gap is what Voze is built to close. Voze is a preferred partner of Procede, Karmak, and MaddenCo, and works with CDK. On Karmak, Procede, and CDK, its DMS integrations for heavy-duty dealers bring parts sales into Voze, so each field visit sits next to what that account bought. Managers can look at it by location, by rep, and by customer.

For the rep, it starts before the visit. On Karmak, MaddenCo, and CDK, the DMS customer list comes into Voze, so each rep sees their own accounts. On Karmak, a rep can open a company in Voze Pro, the app for reps, and see that customer’s parts orders. If the dealer in our Tuesday story ran Karmak, the rep could have seen from the parking lot that brake orders had gone quiet, and asked about it in the first five minutes.

After the visit, the rep records a voice note, and it attaches to the account. What you get depends on your DMS and how it’s set up. If you run something else, Voze connects through Zapier to the tools you already use, and we build custom connections for larger dealer groups. You can see more of how Voze works for heavy-duty truck dealers on our industry page.

Keep it about the rep

One last thing. If visit tracking feels like being watched, reps will write the bare minimum, and you’re back to “Good visit.” Keep the record useful to the rep first: their accounts, their notes, and what to bring up next time. When reps get something out of the notes, the notes get better.

Curious what your setup would look like? See what each DMS connection brings into Voze.