Guide
Customer Info Is Everywhere: A Simple Way to Track Repeat Work
A minimum customer record so when they call back you have one place to look: who they are, what you did last time, and what to do next.
For teams whose customer details live in texts, paper, and memory and who lose repeat work because no one has the full history.
Next: Pick one shared place (spreadsheet, FSM, or simple CRM) and use it for the next 20 jobs; then hit the FSM category if you want software to tie jobs to customer cards.
The situation
Customer details live in texts, paper, and people's heads. When they call back, the person who took the call doesn't have the history.
Repeat work and warranty callbacks get delayed or lost because "who was that?" and "what did we do?" take too long to answer.
One shared place and a simple format—name, last visit, next step—fix most of this. Use it for the next 20 jobs; then look for software that ties jobs to customer cards.
What a minimum customer card needs
- Name, address, best contact (phone and email so you can reach them and they can reach you).
- Job history in 2–3 bullets: last visit date, what was done, what was found (e.g. "Jan 15—furnace tune-up; filter replaced; recommended duct seal in 6 months").
- Photos or docs tied to the job so the next tech (or you in 6 months) can see condition and proof.
- Preferred payment and any notes (pets, access, preferred time) so you don't ask the same questions every time.
A simple way to start this week
- One shared place for customer cards—a spreadsheet, a folder with one file per customer, or your FSM's customer list. Not three places.
- Update after every job closeout: add one line to job history and attach or link the key photo so the next visit has context.
- Same format for every customer so you can scan quickly (same fields, same order).
- When they call, open the card first; then you can say "last time we did X; you asked about Y" instead of "remind me again."
When tools help
- Customer cards tied to job history so one click shows all visits and notes.
- Photos stored per job so you're not digging through the camera roll.
- Searchable notes for the team so anyone can find "filter size" or "gate code" without calling the tech who was there.
Mistakes to avoid
- Building complex CRM fields before you have a habit of updating—start with name, address, last job, next step.
- Each tech keeping their own notes in their phone or a personal list; repeat work and callbacks need one shared view.
- Skipping the update after the job; the card is only useful if it's current.
Take the FSM quick check
Quick checkSee if Field Service Management tools are right for your team.
Take the FSM quick checkRelated templates
Copy-paste scripts and checklists for this pain: