A sales visit report (or call report) records who was seen, what was learned, what each side promised, and the next action with its date.
It is written right after the visit, in a few minutes, and updates the customer profile and open deals. Without a dated next action, it only proves you were there.
What a visit report is for
A sales visit report is the written record of a meeting with a customer or prospect: who was there, what was learned, what was agreed and what happens next. It serves three readers: the rep at the next visit, the manager following the account, and whoever takes over the portfolio one day.
A useful report is not a story. It answers the same fixed questions every time, so that visits can be compared and a fact found without rereading three paragraphs. The most important question is the last: what happens now, and when?
The complete set Field sales templates: how the documents connectThe template, field by field
Copy the fields below in this order: the first column becomes the heading, the second says what goes in it, the third why the field exists. Remove a field you have no use for; add one your business needs.
| Field | What to write | Why |
|---|---|---|
| Account and date | Account name, date and length of the visit | Find the visit and measure visit frequency |
| Type of visit | From a list: prospecting, follow-up, order, audit, complaint | Count visits by purpose |
| People met | Name and role of each person present | Know whether the decision-maker was seen |
| Objective | What you came for, written before going in | Judge whether the visit achieved it |
| What was learned | New facts: need, budget, competitor, deadline, change of contact | Update the customer profile |
| What was promised | By the rep and by the customer, each with a date | Keep your word, and remind them of theirs |
| Outcome | Order, quote, deal opened, nothing: from a list | Link the visit to revenue |
| Next action | What, who, by when: a date, not “soon” | The only field that moves the account forward |
A filled example
| Field | Example |
|---|---|
| Account and date | Delta Bistro (fictional) — Tuesday 6 October 2026, 10:15, 40 minutes |
| Type of visit | Follow-up |
| People met | A. Turner, owner; R. Patel, head chef (first meeting) |
| Objective | Present the winter range and learn the annual closing dates |
| What was learned | Closed 4 to 18 January; new menu on reopening; the chef chooses products, the owner signs |
| What was promised | Rep: send data sheets for three products by 9 October. Customer: taste the samples by 20 October |
| Outcome | Order: 24 cases at €18 = €432; deal opened for the winter range, stage “proposal” |
| Next action | Call the chef on 21 October for feedback on the samples |
The example follows the template line by line. All data in this example is fictional.
How to use it
- Write the objective before going in. One sentence: what you came for. It is what lets you judge the visit on the way out.
- Fill it in on leaving. Within minutes, before the next visit: after an hour, promises and names are lost.
- Separate facts from impressions. “The budget is approved in November” is a fact; “he seemed keen” is not. Facts go into the customer profile.
- Date every promise. The rep's and the customer's. A promise without a date cannot be followed up.
- Set the next action. What, who, when. If nothing is due, say so and date the next visit from the account's frequency.
- Move new facts to the profile. Change of contact, deadline, competitor: into the customer profile, not only into the report.
Common mistakes
- The narrative. Three chronological paragraphs nobody rereads; the useful fact is there, but cannot be found.
- A vague next action. “Follow up soon” is not an action: the date is missing.
- The Friday report. Written from memory for the whole week, it loses the details that mattered.
- The customer's promises forgotten. What the customer committed to is as useful as what the rep promised.
- Facts left in the report. A contract end date noted in an old report triggers nothing a year later.
Spreadsheet or tool
The template works in both. This compares categories of tools, not products: any given product may differ from these general tendencies.
| Aspect | Spreadsheet or document | Field sales tool |
|---|---|---|
| Entry | A form or a spreadsheet row, often filled in at the office | On the phone on leaving, sometimes by voice |
| Link to the account | Copied by hand | The report is attached to the account and its deals |
| Next action | A cell nothing reminds you of | A due date that comes back in the rep’s day |
| Manager’s view | Open the files one by one | Visits listed by account or by rep |
| Without signal | Depends on the file and the device | Depends on the tool: test offline use in a trial |
What SalesIro brings
The features that fill in or replace this template, all taken from the public feature list (59 features, 3 of them marked “to be activated”):
- Dictated visit report: speak on leaving the visit, the text writes itself, you reread and approve;
- AI formatting of the visit report (to be activated: workspace AI key): dictated text becomes a report, a dated next action and promises;
- Tracked promises: what was promised, dated, with a reminder before it falls overdue;
- Dated notes and attachments: timestamped notes, photos and documents attached to the account;
- My day: the next action comes back on the day it is due;
- Offline mode: saved on the device, sent when the signal returns.
The same data can be queried from an AI assistant — Claude, ChatGPT, Le Chat or Perplexity — through the MCP server for AI assistants, with a key or an OAuth connection. A question such as “which promises made this week are still open?” is answered from your own data, without an export. Every read is written to the access log, and access rules still apply: a rep's assistant only sees that rep's accounts.
Related guides
How the templates fit together is explained in field sales templates: the complete set.
- Customer profile template (B2B)
- Weekly sales report template
- Account plan template
- Offline CRM for field sales
To compare features line by line, see the feature list. All English guides are listed on the guides page. A French guide on this topic is also available: version française.
Further reading
Frequently asked questions
What should a sales visit report include?
The account and date, the type of visit, the people met, the objective, what was learned, what each side promised with a date, the outcome and the dated next action.
When should a visit report be written?
Right after the visit, before the next one. Written at the end of the week, it is reconstructed from memory and loses names, dates and promises.
What is the difference between a visit report and a weekly report?
A visit report covers one visit and one account; a weekly report covers one week and a whole portfolio. The second is built from the first and does not repeat it.
Is a call report needed when the visit led to nothing?
Yes, a shorter one: what was learned and the next action. A visit with no order often reveals a change of contact or a deadline that will matter next time.
The report dictated on leaving the visit
In SalesIro, the visit report is dictated, reread and approved on the phone, even without signal. Promises are dated and followed up, and the next action returns to the rep's day when it is due.
See how it works