Complaints and warranty: the assistant in a dispute

A complaint is the moment when a customer asks for something that costs money and a company has to decide whether to grant it. That makes chat a different tool here than it is for a question about opening hours: whatever an assistant promises in the name of the company, the company has to honour. The sensible scope is therefore narrow. The assistant explains the framework in your own words, records the facts in full, files the order number, the purchase date and the photos, works out where the case sits in the statutory periods and then hands over to a person. This article shows how the statutory warranty and a commercial guarantee differ, which rights Section 437 of the German Civil Code gives the buyer, why the burden of proof is different in the first year, and where the line between recording and deciding runs in a dispute.

Enlarge graphic

Labels in the illustration

• 1. Record in chat
• The facts in plain words
• Order number and purchase date
• Photos of the defect
• The outcome the customer wants
• Contact route for follow-up
• 2. Place it in the period
• Delivery
• 12 months
• 24 months
• First year: Section 477
• The defect is presumed, the
• company has to rebut it
• Then up to month 24
• The buyer carries the burden,
• Section 438 sets the end
• 3. A person decides
• Rights under Section 437
• Cure (Section 439)
• Rescission or price reduction
• Damages
• Goodwill beyond the law
• Every promise comes from a
• person, never from the chat
• What stays out of automation
• No assessment
• Whether a defect exists is
• not for the assistant to say
• No promise
• Rescission, reduction and
• refunds stay with the team
• No refusal
• A no is a decision of the
• company just as much
• Recording and classifying can be automated, deciding stays with people

Complaints in chat: record, classify, hand over

Statutory Warranty and a Guarantee Are Two Different Things

In everyday language everything is a complaint: the device that stops working after eight months, the seam that comes apart, the scratch that was already there when the box was opened. In law there are two separate foundations behind this. The statutory warranty is the seller liability for defects; it arises with the contract of sale and does not have to be promised anywhere. A guarantee, by contrast, is a voluntary declaration that someone gives in addition, usually the manufacturer. Section 443 of the German Civil Code describes it as an obligation that comes alongside the statutory liability for defects, and that is the point: it does not replace the warranty, it is added to it.

For the assistant this distinction is not a nicety, it is a switch. If someone asks about the guarantee for a device bought twenty months ago, the manufacturer undertaking may have expired while the statutory liability has not. An assistant that only repeats the manufacturer conditions sends the customer away with a false picture, and quite possibly into a complaint that costs more than the case itself. The knowledge base therefore needs both: your own rules and the sentence that statutory rights remain unaffected.

What Section 437 Gives the Buyer

If the thing is defective, the buyer does not have one claim but a graded set of options. The statute lists them in a fixed order, and that order is the most common source of misunderstandings in chat: asking for a refund straight away skips the first stage.

Cure means, under Section 439(1), that the buyer may choose: removal of the defect or delivery of a thing free of defects. Only when that stage fails do the further rights come into play, namely rescission or price reduction under Section 437 no. 2 and damages under Section 437 no. 3. Where a consumer is the buyer, Section 475d additionally governs when rescission no longer requires an express deadline to be set.

• Stage one: cure, with the buyer choosing between repair and replacement (Section 439(1))
• Stage two: rescission of the contract or reduction of the purchase price (Section 437 no. 2)
• Stage three: damages or reimbursement of futile expenditure (Section 437 no. 3)
• Alongside and independently: claims under a guarantee against whoever gave it (Section 443)

An assistant may explain these stages. It may say that cure comes first and that your team normally offers repair or replacement for it. What it may not do is apply them to the individual case: whether this condition is a defect, whether cure has failed, whether rescission holds. The difference between general information and applying the law to a case is easy to overlook in chat and is the whole difference in a dispute.

Two Years, One Year of Burden of Proof

The claims named in Section 437 no. 1 and no. 3 become time-barred after two years for movable goods; that is set out in Section 438(1) no. 3. Under Section 438(2) the period starts with delivery of the thing, and with handover in the case of land. These two years are a limitation period, not a durability statement: they say how long a claim can be enforced, not how long a product has to last.

In practice this sentence shifts the burden. If a consumer reports a defect within the first year, the company would have to show that the goods were sound at the passing of risk. After that the relationship reverses and the buyer carries the burden. For live animals Section 477(1) sentence 2 shortens the period to six months, and for goods with digital elements Section 477(2) contains its own rule. For chat this means one thing above all: the purchase date is the single most important piece of information in the whole conversation.

What the Assistant May Record

The real benefit is not in the answer but in the intake. Most complaints arrive incomplete: one sentence in a contact form, no photo, no order number, no purchase date. The team writes back, asks, waits, and the case drags on for days before anyone can even assess it. An assistant saves that round trip, because it asks while the customer is still in the conversation.

• The facts in the customer own words: what was bought, what happened, since when
• Order, job or invoice number so the case can be matched without guessing
• Purchase date and delivery date, because the statutory periods hang on them
• Photos or a short video of the condition being complained about
• What the customer wants: repair, replacement, a refund, or first of all an assessment
• Name, a way to reply and the consent to use those contact details for it

Photos are the biggest lever here, because one picture often settles at a glance what would otherwise take three messages; how to handle that cleanly in chat is covered in the article on image upload in chat. For contact details the same rule applies as everywhere else in chat: they are collected because the case needs them, not as a stock. The rules that apply are described in the article on GDPR, data protection and hosting.

What It Does Not Decide

The line runs where a piece of information turns into a declaration by the company. Anything that creates, waives or refuses rights does not belong in automation. That is not caution on principle, it is the only division that holds up in a dispute: an assistant cannot examine a set of facts, it can only pass them on.

• No assessment of whether a defect exists or whether it was wear or improper use
• No promise about rescission, price reduction, refund or replacement
• No refusal either, because a no is just as much a decision by the company
• No goodwill beyond the statutory rights
• No setting of deadlines, no waiver, no statement on limitation in the individual case
• No information about the terms of a guarantee that a third party has given

Handover Is the Rule Here

For most questions, handing over to a person is the exception. In our own measurement series 43 of 48 questions stayed without a handover to a person; this was measured on a single assistant on our own knowledge base, not on customer projects, and a figure from live operation is not yet available. The method is set out under measurement series. For complaints this ratio is deliberately reversed: they belong to the cases that are handed over, and from the very start.

Handing over does not mean breaking off. The customer should not be sent to a form to type everything in again. The conversation continues with everything that has already been said, and the member of staff joins fully informed. What that handover looks like technically and organisationally is covered in the article on handover to human agents.

• The full transcript of the conversation, not a summary of it
• Order number, purchase date and the period classification the assistant calculated
• The uploaded photos, firmly attached to the case
• The outcome the customer expressly named, in their own words
• The note that the assistant promised nothing and refused nothing

During office hours a person ideally takes over directly. Outside those hours the assistant records the case in full, confirms receipt and names the next step, without committing to a processing time that nobody knows. Even that is progress for the customer compared with a form that disappears without a word.

A Flow That Protects Both Sides

For the division to hold in day-to-day operation it has to be part of the flow, not of good intentions. The following cut has proved workable: five steps, each one stating what the technology does and what it expressly leaves alone.

Transparency, Data Protection and Records

Anyone discussing a dispute in chat has to know who they are talking to. Article 50(1) of Regulation (EU) 2024/1689 requires that people are informed that they are interacting with an AI system, unless this is obvious anyway. In a complaint conversation this labelling is more than a formality: it is the reason why nobody has to take the answer for the binding statement of a case handler. What the duty means in detail is covered in the article on the transparency obligation.

In data protection terms a complaint is not an easy case. Order data, contact details and often photos accumulate, and those photos frequently show more than the condition complained about: a flat, a number plate, a person in the background. Article 5(1)(c) GDPR requires that only what is necessary for the purpose is collected, and point (e) limits storage to what is needed for it. In practice: no mandatory fields without a purpose, a named retention period for photos, and hosting you can name. The article on data protection and hosting goes into this.

That leaves the record. In a dispute a chat transcript is a file: it shows what was reported, when it was reported and what was answered. That helps both sides, as long as the transcript stays complete and is not tidied up afterwards. Anyone analysing conversations should look at complaints separately: they are rare, but they show the gaps in the knowledge base most clearly. How to do that systematically is covered in the article on conversation analytics.

Honest Limits

An assistant does not settle a complaint. It shortens the path to the point where a person decides, and it makes sure that person has everything in front of them. Where your own rules are written down nowhere, the assistant cannot repeat them either; where nobody on the team picks the case up, even the most complete intake helps nothing. And an assistant can be wrong. That is why it is bound to your sources, shows what an answer rests on, and is meant to pass sensitive cases on instead of handling them. How the support assistant records complaints and hands them over to your team is shown on the product page; we are happy to go through your own processes for warranty and withdrawal with you via the contact page.

• Keep statutory warranty, guarantee and withdrawal cleanly apart in chat
• Write down your own rules on cure, returns and who bears the cost
• Define the mandatory details: number, purchase date, description, photo, desired outcome
• Let the period classification be calculated, but not the assessment of the defect
• Prescribe the handover sentences word for word and take every promise out of automation
• Limit retention of photos and contact details and keep the AI labelling visible

Frequent questions