Resources
How to Find Decisions and Promises in WhatsApp Chats
A WhatsApp message can suggest a date without confirming it. To recover what was agreed, read the proposal, the reply, any conditions, and later changes together. Keep each conclusion beside the messages that support it.
This is useful when a delivery date, client approval or responsibility has become scattered across a long conversation. The goal is a small, reviewable record that makes clear what is agreed, what remains conditional and what still needs an answer.
Start with one question
Write the question before collecting messages. “What is happening with the delivery?” is broad. “Was Tuesday agreed, and was a later change accepted?” gives you something specific to check.
Read the messages around the apparent answer, then look for later references to the same commitment. A short quote can lose a condition that appears in the next message. An older agreement can also be changed later.
Separate a request from an agreement
Consider this fictional example:
| Time | Sender | Message |
|---|---|---|
| Monday, 09:00 | Customer | Can you deliver on Tuesday? |
| Monday, 09:08 | Supplier | Tuesday works if the pallets clear the gate before 6pm today. |
| Monday, 09:15 | Customer | Agreed, with that clearance condition. |
| Monday, 15:00 | Supplier | Wednesday might be easier. |
| Monday, 15:10 | Customer | Please confirm whether Tuesday is still possible. |
The first message is a request. The next two support a conditional agreement for Tuesday. The fourth suggests a different day, but does not show that both sides accepted it. The final message leaves a question open.
A careful account is: Tuesday was agreed subject to Monday clearance. A Wednesday alternative was suggested, but acceptance is not shown. The excerpt does not confirm clearance or resolve the final question.
“Delivery confirmed for Wednesday” would go beyond the messages.
Record the condition, not just the date
Use a small table to keep the result inspectable:
| Item | What the example supports |
|---|---|
| Agreed action | Delivery on Tuesday, subject to clearance |
| Condition | Pallets clear the gate before 6pm on Monday |
| Supporting messages | Supplier at 09:08 and customer at 09:15 |
| Later change | Wednesday suggested at 15:00; acceptance not shown |
| Outstanding question | Is Tuesday still possible, and was clearance completed? |
Record a responsible person or completion date only when the conversation supports it. If an owner is missing, write “not stated” rather than assigning one from context.
Check whether the agreement is still current
Before using the record, ask:
- Is there an explicit reply accepting the proposal?
- Does the agreement depend on a condition?
- Is the date a deadline, a suggestion or an event that already happened?
- Did later messages change, cancel or complete it?
- Can someone reviewing your conclusion open the messages behind it?
If the available conversation ends with an unanswered question, preserve that uncertainty. A useful summary can tell you exactly what still needs confirmation.
Where chat analysis helps
Analysis can help organize a long conversation into summaries, timelines, decisions and tasks. Source-linked answers also make it easier to inspect the messages behind a conclusion. The review still matters: opening a citation is the start of checking a claim, not a guarantee that the claim is correct.
Explore decisions and tasks in Knowledge Hub, or see how Ask & Verify links answers to messages.
Keep this checklist: action, owner if stated, date if stated, conditions, supporting messages, later changes and unresolved questions.
DialogSignal is opening access through its early-access list. Join early access to be contacted about trial availability.