How do you find what was promised to a customer in past visits?
Summary
Finding past visit promises takes three steps: narrow visit records by customer and dates, search exact action words, confirm open items with the customer. The steps work when visit notes are written down somewhere searchable; a promise kept only in one person's memory or private notebook has to be recovered by asking the people involved.
In the TREC 2007 Legal Track, a legal document discovery test, negotiated keyword queries found on average an estimated 22% of the relevant documents (NIST TREC Legal Track, 2007).
Outlook search returns only the first 1,000 results, so a broad search can hide the visit note you need (Microsoft, 2026).
Outlook uses prefix matching: "ray" finds Raymond and rays but not disarray or tray (Microsoft, 2026).
In Gmail, the after: and before: operators limit a search to a date range and from: limits it to a sender (Google, 2026).
This guide is for a supplier's technical sales or service person who visits customer sites and needs to know what the company already promised there. It covers finding and confirming promises; it does not decide whether a promise is a contract term, which is a question for your commercial or legal team.
What do you need before you look for what was promised to a customer?
Before you look for what was promised to a customer, you need the customer's exact account name and site, the date range of the visits you care about, and access to every place visit notes are kept. Write down the names under which the customer appears, because one plant can sit in the records as the group name, the site name and an old trading name. Fix the date range from the first visit you are unsure about to the most recent one; an illustrative range for an account handover is the previous 24 months. List who visited in that period, including colleagues who covered for the account owner and application engineers who joined a trial, since their notes may be the only record of what was said. Finally, decide what counts as a promise for this search: an action, an owner and ideally a date, such as sending a revised technical data sheet (TDS), returning to take samples or running a trial, rather than general goodwill.
Why do promises made in customer visits get lost?
Promises made in customer visits get lost because they are spoken during the visit, written down by one person in their own words, and stored wherever that person keeps notes. A rep who writes "will send the new TDS" in a notebook, and a colleague who later searches the shared records for "data sheet", are looking at the same promise with no words in common. Many promises also lack an owner or a date, so nothing prompts anyone to act on them until the customer asks. Handovers make the gap wider: when the account owner changes, the new owner inherits the shared records but not the notebook, the phone notes or the memory of what was agreed at the coffee machine. The quality standards point at the same weak spot from the other side. ISO 9001:2026 addresses communication and documented information as support requirements of a quality management system (ISO, 2026), and ISO 15489-1:2016 treats metadata for records as part of managing records (ISO 15489-1:2016). A promise written without an owner, a date or the customer's name is a record nobody can find or act on.
Where are commitments from past customer visits usually recorded?
Commitments from past customer visits are usually recorded in visit reports first, then in follow-up emails, quotations and trial plans, and sometimes only in personal notes. Search them in that order, because each later source is less structured and harder to search.
Visit reports or call notes in the shared system, filed by customer and date.
Follow-up emails sent after the visit, which often restate the promise in the customer's terms.
Quotations and offers, which carry promised prices, delivery terms and validity dates.
Trial plans and sample requests, which record promised tests and dates.
Complaint records. ISO 10002:2018 gives guidelines for complaints handling, including resolving any complaints received (ISO 10002:2018), so a promise made in answer to a complaint belongs in that record.
Personal notebooks, phone notes and calendars of the people who visited.
The key source is the follow-up email, because it is dated, addressed to the customer and written while the visit was fresh. A visit report without an email may record what the rep intended; an email shows what the customer was told. When the two disagree, treat the email as what the customer expects and confirm it.
How do you search visit records for a promised action or date?
Search visit records for a promised action or date by narrowing to the customer and period first, then searching the exact words for the action and their variants, then reading what the search returns. Narrowing first matters because tools cap results: Outlook returns only the first 1,000 search results (Microsoft, 2026). In Gmail, the operators after: and before: limit a search to a date range and from: limits it to a sender (Google, 2026).
Narrow by customer and dates. Filter by account, sender domain and the date range you fixed.
Search the action words. Try each likely wording: send, sent, TDS, data sheet, sample, trial, quote, revisit, call back.
Search the date words. Try month names and date formats used by the team.
Read the hits in date order and copy each promise into one list.
Exact-word search finds a promise only when the same words were written. Outlook uses prefix matching, so "ray" finds Raymond but not disarray (Microsoft, 2026), and a quoted word returns only that exact word (Microsoft, 2026). Keyword recall is low even when lawyers negotiate the query: in the TREC 2007 Legal Track, negotiated keyword queries found on average an estimated 22% of the relevant documents (NIST TREC Legal Track, 2007). Read the full notes for the visits that matter.
Does a past visit record state a promise someone can act on?
A past visit record states a promise someone can act on when it names an owner, an action, a due date, the customer contact it was made to and a status. The table below decides whether each promise you found can be acted on as written or needs confirming first.
Check | Pass | Fail and what to do |
|---|---|---|
Owner | A named person in your company | "We will" or no name: assign an owner before the next contact |
Action | One concrete action, such as "send revised TDS for product X" | "Look into it": rewrite as an action and confirm with the customer |
Due date | A calendar date or a dated event, such as "before the 2026 shutdown" | No date: treat as open and ask the customer what they expect |
Customer contact | The person at the customer who heard the promise | No name: ask your colleague or check the email recipients |
Status | Done, with the date and the evidence, or open | No status: check sent mail and shared folders for the deliverable |
Source | A dated visit report or email you can point to | Memory or hearsay only: confirm before treating it as a commitment |
The key row is status. A promise that was kept but never marked done looks open, and chasing it again tells the customer the company does not know its own history. Check sent emails and shared folders for the deliverable before you list a promise as open, and record the evidence next to it when you find it. A promise that fails the owner or due date row is still a promise: the customer heard it, so assign both before the next contact rather than letting the gap close it quietly. Run the table on every promise in your list, not only the ones that look important.
How do you confirm an open promise with the customer?
Confirm an open promise with the customer by sending one short written list of the open items, each with what was promised, when and by whom, and asking the customer to correct it. A list in writing gives the customer something concrete to answer and gives you a dated record of their reply. Open with the items you are sure of and finish with the ones you could not verify, phrased as questions: "Our notes from the visit in March 2026 mention a trial on line 2; is that still wanted?" Do not restate a promise you cannot find in any record as a fact; ask whether it was discussed. For each item the customer confirms, set a new owner and due date and say when you will report back. For items the customer no longer wants, record that they were withdrawn and on what date, so the next person does not reopen them. If the customer remembers a promise your records do not show, write it down with the customer's words and the date they told you, and check it with the colleague who made the visit before you agree to it.
How should you record a visit promise so the next visit can find it?
Record a visit promise so the next visit can find it by writing it on the day of the visit, in the shared customer record, as one line with owner, action, due date, customer contact and status. Use the same words every time for the same kind of action, because exact-word search depends on it: an illustrative team vocabulary is "send TDS", "send SDS", "run trial", "take samples", "quote" and "revisit". Put the account and product names in the line itself, not only in a folder name. Send the customer a follow-up email that repeats the promises in the same words, which gives both sides a dated copy. When the promise is kept, mark it done with the date and a pointer to the evidence, such as the sent email or the trial report. ISO 15489-1:2016 covers metadata for records as part of records management (ISO 15489-1:2016); for a visit promise, the owner, date and customer fields are that metadata.
When should you bring in a colleague or specialist about past customer promises?
Bring in a colleague or specialist about past customer promises when a promise touches price, warranty, delivery or product performance, when the customer and your records disagree, or when the person who made the promise has left. Promises on price and delivery can bind the company, so the commercial team should see them before you confirm them; a promised performance result belongs with the technical manager who can judge whether it can be met. When the customer remembers something your records do not show, the colleague who made the visit is the first person to ask, and their calendar and sent mail are the next places to look. When that person has left, check the quotations, trial plans and complaint records they created, because those survive in shared systems. In Lubinpla, you can narrow work logs to one customer account and period and read them, or ask the main agent with those records as the basis; the work log search itself matches exact words. Whoever you involve, bring the list of promises with their source, date and status, and the questions you could not answer from the records.
Frequently asked questions
How far back should you search for promises made to a customer?
Search back to the last point at which you know the account's open items were reviewed, such as a handover meeting or an account review. Without one, search the full period of the current account owner and the previous one, then narrow to promises that are still relevant to the products and sites the customer uses.
What if a promise was only made verbally?
Ask the colleague who was there and check their calendar, sent mail and notes around the visit date. If nothing written exists, raise it with the customer as a question, not as a commitment, and record their answer with the date.
Should promises go in the CRM or in the visit report?
Put them wherever the next person will look first, and in one place only. Splitting promises between a sales system and visit reports doubles the searching, and the two copies drift apart when one is updated and the other is not.