Using WhatsApp messages as evidence in a supplier dispute | ThreadRecap
Supplier relationships increasingly run on WhatsApp. Price agreements, delivery schedules, change requests, and complaints all flow through the same thread, often mixed with casual conversation. When a dispute escalates, that thread becomes your most important document. This guide walks through four common supplier-dispute patterns, the specific evidence each one requires, and how to turn a raw WhatsApp export into a structured, legally credible package.
Why supplier disputes increasingly live on WhatsApp
Business communication has shifted decisively toward messaging apps. Purchase orders get confirmed with a thumbs-up emoji. Delivery windows are set in voice notes. Price revisions are agreed in a quick back-and-forth that nobody bothers to formalise in writing. WhatsApp sits at the centre of this because it is already on every phone, requires no onboarding, and carries the informality that keeps negotiations moving.
That informality creates risk. When something goes wrong, the terms that both parties thought were obvious turn out to be nowhere near as clear as each side remembers. Screenshots circulate, context is stripped away, and the dispute becomes as much about what was said as about what actually happened.
Courts have begun to take this record seriously. Courts emphasize the evidentiary weight of WhatsApp messages, describing them as crucial when disputes turn on intention and liability. The landmark case of Jaevee Homes Ltd v Fincham (t/a Fincham Demolition) EWHC 1134 (TCC) made the point with force: the High Court held that a binding contract for demolition services had been validly formed via WhatsApp messages alone, with no formal subcontract signed. The messages covered the job award, a lump sum price of £248,000, and a proposed structure for monthly invoicing with 28 to 30 day payment terms. If WhatsApp can form a contract of that size, it can certainly dissolve one.
The practical implication is that the WhatsApp thread is not supplementary evidence. In many supplier disputes, it is the primary record.
Pattern 1: Insurance claim after contractor damage
When a contractor or supplier causes damage to property, equipment, or stock, the insurance claim depends on proving three things: that the contractor was engaged, what they were engaged to do, and when and how the damage occurred.
WhatsApp threads routinely contain all three. The engagement is confirmed in the initial exchange agreeing the job. The scope of work appears in follow-up messages, photos of the site, and voice notes describing what needs to be done. The damage timeline emerges from the messages sent immediately after the incident: complaints, photos, requests for explanation, and any admissions or deflections from the contractor's side.
Insurers and loss adjusters look for a coherent chronology. A screenshot from one message and a voice note from another, presented separately, is far weaker than a complete sequential export covering the whole engagement. The export needs to show the relationship from first contact through to the dispute, not just the moments that support your position.
Voice notes are particularly valuable here because they often contain the kind of direct, unguarded language that written messages do not. A contractor saying "yeah I know we knocked that wall, we'll sort it" in a voice note is a contemporaneous admission. ThreadRecap transcribes voice notes using OpenAI Whisper, producing a timestamped, readable transcript that can sit alongside the original audio in the evidence package.
Pattern 2: Payment denial after price agreement
Payment disputes follow a recognisable pattern. A price is agreed informally, work is delivered, and then the buyer either denies that the price was agreed at that level, claims a discount was promised, or introduces payment terms that were never part of the original conversation.
The Jaevee Homes case is directly relevant here. The court found that the WhatsApp exchange was sufficient to establish not just that a contract existed, but what its specific commercial terms were, including price and payment schedule. The lesson for anyone on the receiving end of a payment denial is that the agreement itself, if it happened on WhatsApp, is already documented.
The evidence package for a payment dispute needs to capture:
The initial price agreement, including any qualifications or conditions attached to it
Any subsequent messages that purport to change the price, and whether those changes were accepted
Delivery confirmations, because a buyer who acknowledges receipt has a harder time claiming the work was not completed
Any messages in which the buyer's own words confirm the original terms
Gaps in the thread are as important as what is present. If the buyer claims a discount was agreed but there is no message in which that discount appears, and the supplier's response to the invoice contains no objection, the silence is evidence.
Pattern 3: Delivery dispute over deadlines and partial shipments
Delivery disputes usually involve one or more of the following: a missed deadline, a partial delivery presented as complete, or a disagreement about what was actually ordered. WhatsApp threads tend to document all of these in real time, because both sides are using the thread to manage the logistics.
Deadline evidence is often the clearest. Delivery dates agreed in WhatsApp carry a timestamp. If the supplier confirms "we'll have it to you by Friday the 14th" and the delivery arrives on the 21st, the gap is documented. The more useful evidence is often what happens in between: messages chasing the delivery, explanations from the supplier, and any renegotiation of the date. If the buyer accepted a new date without protest, that acceptance is also in the thread.
Partial deliveries create a more complex picture. The key is to map each delivery confirmation against the original order. If the order was confirmed in a WhatsApp message listing specific quantities or items, and subsequent delivery confirmations cover only some of those items, the shortfall is traceable. Voice notes from site visits, photos of what arrived, and messages asking where the rest of the order is all contribute to the picture.
One underused source of evidence in delivery disputes is the supplier's own messages. Suppliers often send unprompted updates: "just loaded the truck," "driver is 20 minutes away," "we're short on the 50mm stock, sending the rest Monday." These messages, taken together, build a delivery log that neither party created deliberately but that exists in full in the export.
Scope creep is the gradual expansion of work beyond the originally agreed brief, often without a corresponding adjustment to price or timeline. According to the Project Management Institute, nearly 50% of projects experience scope creep or uncontrolled changes to the project's scope. WhatsApp is where most of those changes are requested, because it is the path of least resistance.
The evidentiary challenge in a scope creep dispute is drawing a clear line between the original scope and what was added. This requires two reference points: the initial agreement, and the sequence of change requests that followed it.
The initial agreement is usually in the early messages of the thread, sometimes supplemented by a document sent through the chat. Change requests tend to arrive later, often phrased informally: "while you're there, could you also," "actually can we add," "we've decided we want." Each of those messages is a timestamped record of a new instruction.
The supplier's response to each request matters too. If the supplier flagged that the change was outside scope and would cost more, and the client agreed, that is a variation with agreed pricing. If the supplier flagged it and the client said nothing, the silence may be interpreted as acceptance or rejection depending on context. If the supplier carried out the additional work without raising the issue, the evidence cuts the other way.
Scope creep disputes benefit from a structured output that separates the original scope from the additions. ThreadRecap's Decisions log and Action Items outputs are useful here: they surface the moments in the thread where specific commitments were made, allowing both sides to see exactly what was agreed and when.
For a broader framework on using WhatsApp exports in business disputes, the WhatsApp evidence for business partners feature page covers the full range of structured outputs available.
Building the evidence package each pattern needs
Regardless of which pattern applies, a credible WhatsApp evidence package has the same core components.
Complete export, not screenshots
Screenshots are easy to fabricate and easy to attack. A full WhatsApp export, produced through the app's own export function, carries far more weight because it includes the complete message sequence, timestamps, and sender identifiers. ThreadRecap can handle large ZIP exports, ensuring comprehensive coverage of extensive message histories., which means even a long supplier relationship can be covered in a single upload.
Voice note transcriptions
Voice notes are frequently the most candid part of any business conversation. They need to be transcribed and timestamped so they can be read in sequence alongside the text messages. ThreadRecap uses OpenAI Whisper for transcription, providing high accuracy on clear audio. The transcript and the original audio file both become part of the evidence package.
A chronological timeline
A raw export is hard to navigate. A structured timeline, organised by date and annotated with the key events in the dispute, is what a solicitor, mediator, or insurer can actually use. ThreadRecap generates this automatically from the export, identifying decisions, commitments, and conflicts across the thread.
Separation of facts from interpretation
The evidence package should present what was said and when, and leave interpretation to the legal or commercial argument. Mixing the two weakens both. ThreadRecap's structured outputs, including Meeting Recaps, Action Items, Decisions logs, and Conflict Resolution summaries, are designed to surface the factual record without editorialising.
Privacy and file handling
Before uploading any export, it is worth understanding what happens to the data. With ThreadRecap, the export-and-upload workflow means the file stays on your device until you choose to upload it. Photos, videos, and documents never leave the device. Chat text and voice note audio are stored encrypted in your account, and you can delete them at any time from the dashboard. This matters in supplier disputes where the thread may contain commercially sensitive information beyond the dispute itself.
For guidance on assembling evidence across a more complex business relationship, the article on WhatsApp evidence for legal disputes covers admissibility considerations in more detail.
The thread you already have may be more powerful than you realise. The work is in organising it.
