A customer visit report is a short written record of one in-person visit to one customer. It says who was there, what you saw on site, what was agreed, and what happens next and by what date. Write it within minutes of leaving, so the details are still true.
This is a different job from the other reports on this blog. A customer visit report covers one visit to one existing customer. The sales call report template is a general record of a call or visit, written for the next rep. The weekly sales report template covers a rep's whole week across many customers. Use the visit report when a visit has a story of its own: a service problem, a renewal, a price talk, a first visit after a long gap. The report is easier to write when you planned the visit; see pre call planning.
What a customer visit report is for
Think of the report as the answer to a question your manager, or the next rep, would otherwise ask by text: "How did it go at that customer?" If the report answers that question before it is asked, it did its job. If it only says that you went, it did not.
- It holds what was agreed. A price, a delivery date, a sample, a callback. The customer remembers each of them, so the report has to.
- It holds what you saw. Shelf space, stock on the floor, a competitor's product on the counter, a new manager. Nobody sees this from the office.
- It sets the next step. One action, one owner, one date.
- It outlasts you. When a territory changes hands, the report is the first thing the new rep reads.
Customer visit report template
Copy this into a notes app, a spreadsheet or your CRM. Keep the headings as they are, so every rep's report looks the same and a manager can scan ten of them in a few minutes.
Customer: ______________________ Site: ______________________ Date: ____________ Arrived: ______ Left: ______ 1. WHO WAS THERE Name and role: ______________________________________________ Who decides on orders at this customer: ______________________ 2. PURPOSE Why I went: _________________________________________________ 3. WHAT I SAW ON SITE Stock, displays, equipment, staff, competitor products: ______ Anything that has changed since last time: ___________________ 4. WHAT WAS DISCUSSED AND AGREED Raised by them: ______________________________________________ Agreed (price, quantity, date): ______________________________ Not agreed, and why: _________________________________________ 5. WHAT I PROMISED I will: _______________________ by: ____________ They will: ____________________ by: ____________ 6. NEXT STEP Action: ____________________ Owner: ____________ Date: ____________ Next visit: ____________ Account health: Good [ ] Watch [ ] At risk [ ]
Six headings and about a dozen short answers. If a line has nothing to say, write "none". A blank line makes the reader wonder whether you forgot it.
The five-line version for routine visits
Most visits are routine. You walked in, checked the account, took an order and left. The full template is too much for that. Use these five lines instead.
Customer and who I saw: ______________________________________ What I saw or heard that is new: _____________________________ What was agreed: _____________________________________________ What I promised: _____________________________________________ Next step, owner and date: ___________________________________
Switch to the full template when the visit includes a complaint, a price change, a new contact, a competitor you had not heard of, or any promise that costs money.
A filled-in example
This is a hypothetical visit to a hypothetical customer, written the way a rep should write it. The names and numbers are made up.
Customer: Brandt Industrial Supply Site: Tulsa distribution center Date: Wednesday, March 12 Arrived: 9:40 Left: 10:25 1. WHO WAS THERE Marcus Webb, warehouse manager. Priya Nair, buyer, joined for the last ten minutes. Priya signs purchase orders up to $8,000. Anything above goes to the owner, Gary Brandt. 2. PURPOSE Quarterly visit. Their orders dropped from about $14,000 a month to $9,500 over the last two months. 3. WHAT I SAW ON SITE Our fasteners are on aisle 6, but the bottom two shelves are empty. A competitor's pallet of the same range sits at the dock, wrapped, about 40 boxes. New: a second forklift driver and a relabeled bin system. 4. WHAT WAS DISCUSSED AND AGREED Raised by them: two late deliveries in January, each about three days. Agreed: standing order of 60 boxes every two weeks, starting March 24, at the current price. Not agreed: the 5% volume discount Priya asked for. It needs my manager. 5. WHAT I PROMISED I will: send Priya a written answer on the discount by Friday, March 14. They will: tell me by March 28 whether the competitor pallet is a trial or a switch. 6. NEXT STEP Action: ask my manager about the 5% discount today. Owner: me. Date: March 14. Next visit: April 9. Account health: Watch.
Read it as a stranger. You know the customer is at risk, you know why, you know who decides, and you know the two dates that matter. That is the whole job of the report.
Field by field: what to write
| Field | What to write | Weak entry | Strong entry |
|---|---|---|---|
| Who was there | Names, roles and who signs the order | Met the buyer | Priya Nair, buyer, signs up to $8,000 |
| Purpose | The reason for this visit, in one line | Regular visit | Quarterly visit; orders down from $14,000 to $9,500 a month |
| What I saw | Things you could photograph | Store looked fine | Bottom two shelves empty; competitor pallet at the dock |
| Discussed and agreed | Decisions with a number and a date | Talked about pricing | 60 boxes every two weeks from March 24, current price |
| Not agreed | What was turned down, and the reason | Nothing | 5% discount refused until my manager approves |
| What I promised | Each promise, who heard it, the date | Will follow up | Written answer to Priya on the discount by March 14 |
| Next step | One action, one owner, one date | Check in soon | I ask my manager on March 14; next visit April 9 |
| Account health | Good, Watch or At risk, and one reason | Positive | Watch: competitor stock on site |
What I saw on site
This is the field that makes a visit report worth more than a phone note. A phone call cannot tell you the shelves are empty. Write what you saw, not what you concluded. "Two empty shelves" is a fact the next rep can check. "They seem to be losing interest" is a guess.
Not agreed
Reps leave this out, and it is half of what happened. A refused discount, a postponed decision or a no to a new product all matter to the person who walks in next. Write it with the reason the customer gave.
Adapt the template to your business
The six headings are a starting point. Copy them into the tool your team already uses, whether that is a document, a spreadsheet, a form or a CRM, and change three things: the look, the fields and the length.
- Put your name on it. In a document or spreadsheet, place the company logo in the page header and use one brand color for the headings and the shaded answer cells. Keep the body text dark so it stays readable on a phone in sunlight and on a printout.
- Keep the headings in the same order for everyone. A manager can scan ten reports quickly only if every one starts the same way.
- Add fields for your kind of visit, and no more than three at a time. If you add a field, remove one nobody uses.
| Kind of visit | Fields to add | Why |
|---|---|---|
| Service visit | Equipment and model, the fault as the customer described it, work done, parts used, customer sign-off, follow-up date | The customer disputes a service visit more often than a sales visit, so the record has to show what was done |
| Stock check | Items counted, the usual stock level, the quantity to reorder, the oldest date on the shelf, where the stock sits | A stock count gives the order a number instead of a guess |
| Merchandising visit | Whether the display follows the plan, the number of facings, where the display stands, a photo taken, competitor prices seen, promotion material in place | The brand owner and the store can both check a display against what you recorded |
| Trade show | The event and date, each contact's name and what they want, samples handed out, the owner of each follow-up and the date | The show ends in two days and the follow-ups go cold in a week |
A trade show is not a visit to a customer, so give it its own short sheet and keep the visit report for visits. For the summary that rolls these reports up into a rep's week, see the weekly sales report template.
How to write one in under five minutes
The report is quick if you write it while the visit is fresh. After an hour of driving, you are writing fiction. Do this instead.
- Write it in the parking lot. Finish before you start the engine. The visit is still in your head, and the customer is still in sight.
- Start with the promises and the next step. If the phone rings and you have to leave, those two are the ones to have saved.
- Speak it if typing is slow. A dictated note keeps names and numbers, and it takes less time than thumbs on a small screen.
- Use the short version unless the visit earns the long one. A routine visit is five lines, not thirty.
- Copy numbers exactly. Quantities, prices and dates are the only parts a customer will check.
What a manager should read for
Do not read every word of every report. Skim for these five things, and ask about the ones that look wrong.
- Promises with a date. Open the promises for this week. Ask the rep whether each one is done.
- Reasons for a drop. A customer buying less should have a reason in the report. If the report says nothing, ask what the rep saw.
- Competitor products on site. One sighting is a fact. Three in a month is a pattern worth a team conversation.
- Who decides. If a rep keeps reporting visits with someone who cannot approve the order, the account is not moving.
- Reports that are too short. "Good visit, will follow up" is a report with nothing in it. Send it back with one question.
A report also needs a record behind it. The note says what happened. The visit record says that it happened, and when. In Sales Perch, sales rep tracking saves the time and the phone's location at check-in, and flags visits that need a second look: a check-in more than 500 meters from the customer, a check-out in under a minute, or a check-in within two minutes of the last one. The manager sees the rep's notes next to the visit.
For the accounts that matter most, move from one report to a pattern. Put the visit reports side by side in your key account management review, and you will see which accounts are drifting before the invoices show it.
Where reports should live, and who can read them
A report that cannot be found, or can be read by the wrong people, fails in a different way from a vague one. Decide three things before the first report is written: where it is stored, who can read it and how you know it was written.
One place, attached to the customer
Store every report on the customer's record, so the next rep finds it by opening the customer. Reports in a personal notes app, a text thread, a private email folder or photos on a rep's phone leave with the rep, and nobody else can search them. A field sales CRM is built for this, and a shared spreadsheet with one row per visit works for a small team.
Who can read what
| Person | Can read | Can edit |
|---|---|---|
| The rep | Reports on their own customers | Their own reports, and the next step |
| The manager | Reports for the whole team | Nothing, but can add a comment |
| A rep covering the territory | Reports for the customers they cover, for the time they cover them | Their own new reports |
| Service, warehouse or finance | Only the follow-up item they must act on | Nothing |
| The owner | Everything | Nothing |
Keep customer details safe
- Use company accounts and company devices. Reports about customers should not sit in a rep's personal email or a personal cloud folder.
- Leave out what the report does not need. Do not write down alarm or door codes, account passwords or payment card numbers. If a visit needs one, the customer keeps it.
- Write what you would be comfortable having the customer read. A report about a buyer's attitude can be read by someone you did not expect.
- Remove access when a rep leaves. Reassign the customers and keep the reports on the account.
- Decide how long to keep them. Pick a period, such as the life of the account plus a set number of years, and write it down. Check the rules that apply to your business and region.
Track whether reports get written
Check three numbers each Monday. The first is the share of last week's visits that have a report. The second is the share written the same day. The third is the number of promises past their date. A visit record, such as the one that sales rep tracking keeps, tells you how many visits happened, so the first number is a count and not a guess.
Mistakes that make a visit report useless
- Writing "good meeting". It is an opinion. Replace it with what was agreed and what was not.
- Leaving out names. "The buyer" is nobody after the buyer quits. Write the name and the role.
- No date on the next step. "Follow up soon" has no owner and nothing to check. Write a day.
- Writing the report on Friday. By then you have mixed up three customers. Write it before you drive away.
- Using the full template for every visit. Reps stop writing. Keep the five-line version for routine visits.
- Mixing visit reports with activity reports. A report of ten visits is a weekly report. Keep one visit per report, and use the weekly sales report for the rest.
- Keeping reports where nobody can find them. A report in a personal notes app leaves with the rep. Keep it on the customer record.
Start with one change this week. Ask every rep to write the "What I promised" and "Next step" lines after each visit, and read the promises on Monday. Add the rest of the template once that habit holds.
