# How do I get one answer from three people instead of three answers?

Keep one record that everyone reads from and writes to, with the reason beside each entry. Here is how to set that up, and what it looks like in Felesh.

Published: 2026-10-12  
Canonical: https://felesh.ai/blog/how-do-i-get-one-answer-from-three-people-instead-of-three-answers

## The short answer

You ask three people where a customer stands. One says the quote went out last week. One says it is waiting on a site visit. One says there has been no reply. Each of them is fairly sure.

The fix is not a better memory or a stricter meeting. It is one record that all three read from and write to, with the reason for each entry kept beside it. That is what people mean by a single source of truth: one place where the current answer lives, so nobody has to ask around.

## Why do three people give three answers?

Usually nobody is wrong. Each person holds a different slice of the story.

One took the call and remembers what was said. One sent the follow-up message and remembers what was promised. One visited the customer and remembers how it felt. Each slice is true when it is noted down. The trouble is that the notes sit in three places: a notebook, a phone, a head.

Time makes it worse. A promise made on Tuesday is remembered as "sometime this week" by Friday. A price is rounded. A next step that someone meant to take is assumed to have been taken by someone else.

So the problem is rarely honesty. It is that the work happens in several places and the account of it is never put together.

## What a single source of truth means in a small business

The phrase sounds heavy, but the idea is plain. For each customer, job or promise, there is one record. When something changes, the change goes into that record, not into a side note. When someone needs the answer, they look there.

Two things make it work.

The first is that people write to it. A record nobody updates is just an old opinion in a tidy place.

The second is that each entry carries its reason. "Waiting on a site visit" is far more useful than "pending", because the next person can see why and judge whether it is still true.

## How do I set one up?

You can start with these steps, whatever tool you use.

1. Pick one place for the record and say so out loud. If a fact is not there, it does not count yet.
2. Decide what goes in: what happened, what was promised and by when, and what happens next.
3. Write it down soon after the work, in a sentence or two, not at the end of the week.
4. Add the reason with each entry, so it can be checked later.
5. When people disagree, go to the record before going to each other. If the record is wrong, correct it there.

The fifth step matters most. It turns an argument about memory into a quick look at the page, and it keeps the record trusted.

## How does this look in Felesh?

Here is a walk-through of an ordinary week for a small team.

A call ends. The person who took it types one sentence about what happened. Felesh drafts a note, the promise with its date if one was given, and the next step. Each draft shows its reason and waits for a yes under "Review draft". The person reads it, corrects it if needed and says yes. Now there is one account of the call, not three recollections.

If the next step is a plain task, it is added directly. There is no approval step for tasks.

Later, someone else on the team is asked where the customer stands. They do not phone the colleague. They ask Felesh in their own words, such as what was promised to that customer or which jobs are still open. Felesh answers from your own records, so the answer matches what was written down.

If your customer list is scattered, you can bring contacts and companies in from one Excel or CSV file. You see the column mapping and the rows before anything is saved, so the starting point is one you have checked.

## What does it not do?

It does not read your mail or your drives, and it does not connect to other tools. Felesh knows what is done on Felesh, the files you import, and what you upload or teach it.

That limit is deliberate, and you should plan around it. If a conversation happened somewhere else and nobody typed a sentence about it, Felesh does not know about it. A single source of truth only holds what the team puts into it.

It also does not settle disagreements for you. If two people remember a promise differently, the record shows what was written. Which version was right is still your call.

## What changes for the people involved?

Mostly it is small habits.

The person who did the work says what happened, once, soon after. The person who needs the answer asks the record before asking a colleague. The owner reads the reasons beside each entry instead of chasing explanations.

There is a quieter benefit as well. The record is about the work, not about the people doing it. It shows a customer who has gone quiet, a promise still open, a job waiting on something. It does not turn into a way of watching who did what. That keeps people willing to write things down honestly, and honest entries are the whole value of the thing.

## Where to start

Pick your next customer conversation and type one sentence about what happened, so the team has one answer to look at. You can read more about how records and reasons fit together in Felesh.