Blog · JUN 19, 2025 · 3 min read
A Regional Sales Manager's First 90 Days on FieldVoice
One RSM's own account of rolling FieldVoice out to eighteen reps, week by week, including the two weeks it nearly stalled.
We asked a regional sales manager who rolled FieldVoice out to eighteen reps across three states to walk us through his first 90 days, in his own words, warts included.
Weeks 1 to 2: skepticism
The first reaction from most of the team was that this was another head office mandate that would add work rather than remove it. Two reps quietly kept their old paper diaries running alongside the app for the first ten days, treating FieldVoice as a formality rather than their actual system of record. Adoption looked fine on paper. It was not real yet.
Weeks 3 to 6: the stall
This is the part he was most candid about. Around week three, four reps in the more rural cluster hit repeated sync issues tied to poor connectivity, and rather than trust that queued reports would sync later, they reverted to calling him directly with verbal updates. Adoption dipped to roughly 60 percent daily use. He raised it with us directly, and it became one of the inputs into the offline queue improvements we shipped shortly after.
Weeks 7 to 10: the turn
Once reps saw that offline-recorded reports reliably synced without being lost, the reverting stopped. He also changed his own behavior, and this is the part he credits most: he started reviewing voice-logged notes every evening rather than waiting for the weekly call report, and began giving same-day feedback on messaging to individual reps. Reps noticed the coaching got faster and more specific, which reinforced logging honestly rather than logging minimally.
Day 90: where it landed
By day 90, adoption held at 17 of 18 reps logging daily without reminders. Average reporting time dropped in line with what we see across pilots, and he told us the bigger shift was qualitative: he could see coverage gaps in near real time instead of discovering them at month's end. His one piece of advice for other RSMs starting out: expect a stall around week three to four, and do not read it as failure. Read it as the point where offline reliability gets tested for real, and plan your own check-ins around it rather than being surprised by it.