A sales call report template has seven fields: who you saw, why you went, what you learned, what the customer decided, what you promised, what happens next, and by when. Fill it in within ten minutes of leaving, in plain sentences, so the next rep can pick up the account without calling you.
The same template works for a customer visit report, a sales visit report or a call notes template. Only the first line changes: visit or call. The rest of this article gives you the template to copy, says what each field is for, shows a bad and a good report side by side, and covers how to keep the habit going across a team.
Who reads a sales call report
Most reports get written for a manager and never read again. That is the wrong reader. Three people use a call report, and each wants something different.
- You, in three weeks. You will not remember the buyer said the order was waiting on a budget meeting. The report will.
- The next rep. Someone covers your territory for a vacation, a sick week or a resignation. They walk in cold, and your notes are all they have.
- Your manager. They read for promises that are due, accounts at risk and problems that need their help, not for proof that you worked.
Write for the second reader. If a rep who has never met the customer could act on your report tomorrow morning, the other two readers are covered too.
A sales call report template you can copy
Paste this into a spreadsheet, a notes app or your CRM. Keep the field names exactly as they are, so reports from different reps look the same and a manager can scan them.
Customer: ______________ Location: ______________ Date and time: _________ Visit [ ] Call [ ] Who I saw (name, role): ________________________ Why I went: ________________________ What I learned: ________________________ What they decided: ________________________ What I promised, to whom: ________________________ Next step: ______________ Due: ____________________ Next visit: _____________ Account health: [ ] Good [ ] Watch [ ] At risk
That is seven fields, and each takes one sentence or less. If a field has nothing to say, write "none" so a reader knows you did not forget it.
What each field is for
| Field | Question it answers | Who needs it |
|---|---|---|
| Who I saw | Who is the real contact, and who decides? | The next rep, who needs a name to ask for |
| Why I went | Was this a routine visit, a problem or a pitch? | Your manager, to read the rest in context |
| What I learned | What changed in their business? | You and the next rep, before the next visit |
| What they decided | Did the visit move anything? | Your manager, to see what the visit achieved |
| What I promised | What does the customer expect from us? | Everyone, because a missed promise costs the account |
| Next step and due date | Who does what, by when? | Whoever owns the account on that date |
| Account health | Is this account safe, slipping or in danger? | Your manager, to spot trouble early |
Why I went
State the purpose in one line before the visit starts, not after. "Quarterly check-in" and "price complaint on last invoice" lead to very different notes. Reading the reason first tells the next rep what the rest of the report is measuring. Five minutes of pre call planning gives you that line before you walk in.
What I promised
This is the most useful field and the one reps skip. Every promise goes here with the name of the person who heard it: "Send the revised price sheet to Dana by Friday." A promise that lives only in your head disappears when you change territories, and the customer remembers it.
Next step and due date
Name an owner and a date, or it is a wish. "Follow up on sample" fails. "I call Marcus on Thursday to ask whether the sample passed testing" works. If the next step belongs to the customer, write that too, and note when you will ask.
A bad report and a good one
Both reports below describe the same visit to a distributor's warehouse. The first is what most reps write. The second is what the next rep needs.
Customer: Hartley Supply Went by. Good meeting. Talked about pricing. They seem interested. Will follow up.
Customer: Hartley Supply, Fort Worth warehouse Date and time: Tuesday 10:15. Visit. Who I saw: Dana Ruiz, purchasing manager. She approves orders under $5,000. Her boss, Tom Keller, approves the rest. Why I went: Regular visit. Their last two orders were smaller. What I learned: They moved 30% of their volume to a cheaper supplier in March. Dana says our product is better but her budget is capped. What they decided: Nothing yet. She will test our product on one job next month. What I promised: Revised price sheet to Dana by Friday. Two sample cases delivered by the 20th. Next step: I email the price sheet Friday. I call Dana the 25th for the test result. Due: Friday. Next visit: December 2. Account health: Watch.
The bad report fails in specific ways. "Good meeting" is an opinion, not a fact. "They seem interested" cannot be checked later. "Will follow up" has no owner, no date and no subject. Each of these is a place where the report could carry a fact and carries a feeling instead.
Change the fields by call type
One template covers most calls, but four kinds of visit need different emphasis. Keep the core on every type: who you saw, what you promised, and the next step with a date. Add and drop the rest as the table shows.
| Type of visit | Add or stress | Shorten or drop | Account health line |
|---|---|---|---|
| First visit to a prospect | Who they buy from today, who decides, when they next order, what you left behind (a sample, a price sheet), and the reason they gave for seeing you again | What they decided. It is usually "nothing yet", so write the next step instead | Replace it with Warm, Cool or Dead end, plus one reason |
| Routine reorder visit | The order taken (quantity and delivery date), stock you saw, and anything that changed since the last visit | Why I went ("routine") and What I learned if nothing changed. Three lines is enough | Good, unless something in the notes says otherwise |
| Problem visit (a complaint, a late delivery, a quality fault) | The problem in the customer's own words, what you saw, what you offered, who at your company owns the fix, and the date they will hear back | Pricing talk, unless the fix involves a credit | Watch until the fix is confirmed by the customer, not by you |
| Review with a key account | Spend against last year, who attended from their side, their plans (a new site, a new line), competitor share, goals you agreed and any decision that needs their boss | Order details. The review is not an order visit | Good, Watch or At risk, with the reason and the date you will review it again |
For the key account review, the fields feed an account plan, and the habits behind it are in key account management. A phone call uses the same fields as the visit it replaces. Tick Call and drop What I saw.
Call notes the next rep can use
A call note is the short version of the report, written when you do not have time for nine fields. Use it after a phone call, a hallway chat or a drop-in where you only saw the counter clerk.
- Write the fact first. "Dana confirmed the March switch to another supplier" beats "Discussed competitors."
- Use names and numbers. A name, a date, a quantity and a price survive a hand-over. Adjectives do not.
- Separate what they said from what you think. Mark your own reading with "My read:" so the next rep can weigh it.
- End on the next action. The last line of every note says who does what by when.
- Skip what the system already knows. Date, location and time are recorded when you check in. Do not retype them.
Keep a note to three to six sentences. If you are writing more, you are either recording a meeting that deserves the full report or including things nobody will read.
Write the report before you drive away
A report written that evening loses details, and a report written on Friday is mostly fiction. The time to write it is while you are still in the parking lot. Three minutes is enough if you have the template open.
- Talk it instead of typing it. Voice dictation on a phone is faster than thumbs, and spoken notes keep names and numbers.
- Fill the "What I promised" and "Next step" lines first. If you run out of time, those two lines are the ones to keep.
- Check out of the visit, then write. Checking out ends the visit on the record, and the note belongs to the same visit.
Paper, spreadsheet, CRM or dictated: which way to report
How the report gets written matters less than whether it gets written the same day and lands where the next rep can find it. Every method below works for a team that uses it every visit, and fails for a team that uses it when it remembers.
| Method | Works well when | Where it breaks |
|---|---|---|
| Paper notebook or printed form | One rep covers a small territory and nobody else needs the notes | The notes stay in the truck, nobody can search them, and typing them up later doubles the work |
| Shared spreadsheet | The team is small and wants one set of columns that can be filtered and counted | Typing on a phone is slow, copies of the file drift apart, and a row cannot show the customer's earlier visits |
| Typed notes in a CRM | You want one record per customer that outlasts the rep | Long forms get filled in late, and required fields get filled with filler |
| Dictated notes | Reps write in the parking lot and typing is the slow part | Names and numbers can be misheard, so the rep reads the note once before saving it |
Software can also fill in what it already knows, such as the date, the time, the place and the customer's order totals from your invoices. That saves retyping. It cannot write what you learned, what you promised or what you think of the account. Those lines need a person. A good rule is to automate the facts and keep the judgment with the rep.
A call report and a CRM also do different jobs. The report is one entry about one visit. The CRM is the running history of every entry, so the useful setup is a short report that lands on the customer record. Sales rep tracking covers the record of when and where each visit happened, which you do not need to retype into the report.
What managers should do with the reports
A report nobody reads trains reps to write nothing. Read them on a schedule and say so. A weekly pass through the previous week's reports takes about thirty minutes for a team of eight, and you only need to look for four things.
- Promises coming due. Any "what I promised" line with a date this week. Ask the rep whether it is done.
- Accounts marked Watch or At risk. Pick two and ask the rep what the plan is.
- Competitor names. If the same name appears in three reports, you have a pattern, not an anecdote.
- Empty fields. A report with no next step is a visit with no result. Ask what the rep expected the visit to do.
Use the answers in your one-to-one conversations. Pair the reports with check-in records from sales rep tracking, so you can see both what a rep wrote and when the visit happened. For the numbers a manager can pull from visit records, see field sales KPIs. For a team-level summary that pairs with call reports, see the weekly sales report template.
Common reporting mistakes and how to fix them
Five habits ruin most call reports. They are about how reps write, not how the template is built, so the fix is a rule on your team.
| Mistake | What it costs | Fix |
|---|---|---|
| Writing it late | By Friday three customers have blurred into one, and the objections, the competitor's name and the exact date are gone | Write it before you drive away. Do the promise and next step lines first |
| A vague summary ("good meeting, will follow up") | The next rep has nothing to act on and the manager has nothing to read | Use names, numbers and dates. Run the stranger test above |
| Leaving out the objection | The same objection comes back at the next visit with no prepared answer, and the manager cannot see a pattern | Add an "Objection heard" line and write the customer's words, even when the answer was "none" |
| No next step | The visit has no result, and the account sits until the orders drop | A report without an owner and a date is not finished. Send it back |
| A stale record | The next rep calls a buyer who left or quotes an old price, and the account health still says Good | Update the record the day something changes, and review every Watch or At risk account older than 30 days each month |
To see whether the habits hold, count one thing each Monday: the share of last week's reports that carry a next step with a date. If it is under 90 percent, fix that before you add a field.
Mistakes in how the template is set up
- Too many fields. Past ten fields, reps skip half of them. Start with the seven fields above and cut before you add.
- Free text only. A blank box produces "good meeting." Prompts such as "what I promised" force a fact.
- Writing for the boss. Reports that perform for a manager read as defensive. Write for the next rep.
- No reader. If managers never refer to a report, reps notice within a month.
- Reports that live in a private notebook. A note in a truck is lost when the rep or the truck changes. Keep reports on the customer record, which is the job of a field sales CRM.
Start tomorrow with one change. Add the "What I promised" line to every report on your team, and read the promises each Monday. Once that habit holds, add the rest of the template.
