Tour operator complaint claims (reklamasyon): the records a hotel needs and how to answer

A reklamasyon is a tour operator's claim against a hotel for a guest complaint, usually raised weeks after the stay and settled through the contract. The hotel answers with dated in-stay records: request and complaint logs, work orders, hygiene records and signed feedback. Deadlines, deductions and liability follow the contract and counsel.

The claim arrives in February for a stay in August: a file from the operator's head office, a guest's account of a noisy room and a cold pool, and a line asking the hotel to accept a deduction. Everything the hotel can say about that week now depends on what someone wrote down at the time. This article explains how a tour operator complaint claim reaches a hotel, which records decide the outcome, how to answer, and how to stop the same claim arriving next season.

What is a reklamasyon and how does it reach the hotel?#

A reklamasyon is a claim a tour operator raises with a hotel, usually weeks after the stay, asking the hotel to answer for a guest's complaint or to share its cost. It arrives as a file and a number, not as a conversation at the desk.

The route is almost always the same. The guest complains to the representative during the stay, or to the operator after returning home. The operator opens a file, and the file reaches the hotel's contracted contact, usually sales or the general manager. It normally carries the booking reference, the guest's own account, the dates, and a demand: an explanation, a share of a refund, or a deduction from the hotel's settlement.

In Turkish hotel practice the same word also names the accounting line, the amount the operator deducts or invoices back. Same event, two documents: the claim file and the settlement statement.

Three things look alike and are not. A complaint handled at the desk during the stay, a review published on a public platform, and a contractual claim between two businesses each have their own timeline, their own evidence and their own reader. The claim is a matter between hotel and operator; the guest is usually not a party to it, which changes what the hotel writes, to whom, and how much of the guest's data travels with the answer.

The first move on receipt is procedural, not argumentative: write down the date the claim arrived, the booking reference and the deadline the contract sets, then pull the stay file before anyone drafts a reply.

Why do in-stay records decide the outcome?#

Because a claim is argued months later, and the only facts that survive that gap are the written ones with a date, a time and a name against them. Memory does not travel; a log entry does.

Four record sets carry most of the weight. The request and complaint log records what was asked, when, by whom and what was done. Work orders cover maintenance and housekeeping. Hygiene and cleaning records cover pool, kitchen and laundry. And feedback the guest gave or signed during the stay closes the circle. If you do not yet have a single log discipline, start with a routine for logging, assigning and closing every guest request.

Each entry needs the same five things: date and time, room or area, the guest's words as close to the original as possible, the action taken, and the person who closed it. Records must be retrievable by room number and date, not only by guest name, because the operator's file often spells the name differently from the reservation.

A missing record is not proof of fault, but it removes the hotel's ability to show what happened. Say plainly in the answer what is documented and what is not, rather than reconstructing the week from memory. A photograph or an inspection note taken at the time carries more weight than an accurate description written afterwards, because the date is part of the evidence. The same log serves the guest who complains at the desk and the operator who files a claim later, so one discipline covers both.

What should the hotel do with the tour operator representative during the stay?#

Treat the representative as the person the guest will describe the holiday to, and close every open issue before departure. An issue closed at the desk is a claim that never opens.

Agree a regular slot with the representative, daily in high season, and keep one shared open-issues list: room, issue, promised action, time closed, initials. Walk the list on the last evening or at check-out. Note what was resolved, what the guest said about the resolution, and what remained open. This sits naturally inside a front desk recovery routine for guest complaints.

Write down the guest's own words, the fix, and whether the guest said the matter was settled. Do not write a promise of compensation, an admission of fault or a waiver into that note. Do not ask a guest to sign a statement that there was no complaint; ask them to confirm what was done, which is a fact and not a legal position.

Record in the language the guest used, with a short translation where needed. The operator's file will be read by people who were not in the building. Any issue the representative raises twice goes to the duty manager the same day, and the escalation is written into the list. At the end of the season, hand the representative the pattern of closed issues, not only the individual files.

How should a hotel answer a tour operator claim?#

Answer in the form and within the time the contract sets, with facts in date order and documents attached, and admit nothing beyond what those documents show.

Read the contract before drafting: who the answer goes to, in what form, within how many days, and what silence is taken to mean. The contract, not habit, sets the clock. Open with the booking facts: dates, room type, board basis, party size, arrival and departure, and who handled the stay. Then give a dated chronology built from the log: each entry, each action, each closing, each conversation with the representative.

Attach only what the claim needs: log extracts for the dates in question, work orders, hygiene records, signed feedback, dated photographs. Keep three kinds of sentence in three separate paragraphs: what the hotel did, what the hotel accepts, what the hotel disputes. Mixed together, one line of concession is read as a general admission. No speculation about the guest's motives and no comment about other guests; both weaken a file that is otherwise strong.

Close with a clear position and a named contact, and keep an exact copy of what was sent, with the date it went. If part of the claim is right, say which part. A documented partial concession is more credible than a blanket denial.

Deductions and the claim invoice: what does the contract decide?#

The contract decides whether the operator deducts from the hotel's settlement or issues a document the hotel must pay, on what evidence, with what notice, and in what window the hotel may object. The hotel's part is to answer inside that window, in writing, with the evidence.

Two mechanisms exist and they are not interchangeable: a deduction taken from the monthly settlement, or a separate debit note or invoice. Which one applies is a contract term, not a preference. Check the clause for four things: what may be deducted, on what evidence, with how much notice, and how long the hotel has to object. The wider frame is set by the contract clauses that sit beyond the allotment, and the money at stake belongs to the discipline of protecting a hotel's receivables from tour operator payment risk.

Object in writing inside the window, using the evidence already gathered. Silence is often read as acceptance, whatever the hotel intended. Do not net the deduction off against another booking or withhold a commission payment without checking the contract; that turns one dispute into two.

How the amount is recorded, which document supports it and how tax applies belong to the hotel's accountant. The contract and counsel decide liability; the accountant decides the books. Keep the chain together in one folder: claim file, hotel answer, operator's decision, settlement statement, invoice. A dispute two seasons later is won or lost on that folder.

How does a hotel prevent claims instead of answering them?#

By reading claims as a pattern rather than as separate accidents, and by fixing the room, shift or repair that keeps producing them.

Review claims monthly, not one by one. Tag each by department (housekeeping, maintenance, food and beverage, front desk, animation), by cause (noise, cleanliness, air conditioning, food, pool, service speed) and by room or block. Normalize before comparing months: claims per thousand room-nights, so a busy August is not read as a worse month than a quiet February.

Look for repeats: the same room, the same shift, the same supplier, the same defect returning after a repair that was closed too early. Feed the pattern into three places: the categories in the request log, the maintenance plan, and the pre-arrival check for the room types that generate claims.

Share the pattern with the representative at the start of the season, not only in the answer to a claim. It changes what the guest hears on the first day. Keep a short written note of what changed after each pattern. Next season's file answers itself, and the same complaint stops arriving.

How much guest data should go into a claim answer?#

Only what the claim needs. Under Article 4 of the Personal Data Protection Law (KVKK, Law No. 6698), personal data must be processed for specified, explicit and legitimate purposes and be relevant, limited and proportionate to those purposes, as set out in the consolidated text on the Mevzuat Bilgi Sistemi (2 November 2026) (opens in a new tab).

The purpose here is answering one claim about one stay. Anything in the file that does not serve that purpose is not needed and should not travel. Redact before sending: other guests' names and room numbers, staff personal data beyond a name and a role, identity document copies, card details, health notes. Send extracts of the log for the dates in question, not the whole season's log and not the full guest account with unrelated charges.

Article 10 of the same law requires the data controller to inform people, when their data are obtained, of the purpose, the recipients and the method of collection. A privacy notice that already mentions sharing with business partners and handling legal claims makes this correspondence ordinary rather than surprising. The operator keeps its own copy of the file, but the hotel still decides what it sends and in what form. Confirm who is responsible for what, along with the wording, the retention period and the notice text, with counsel; the principle is fixed, the practice is local.

What to do next#

Open the request and complaint log today and give it the five fields a claim will need: date and time, room or area, the guest's words, the action, and who closed it. Everything else in this article depends on that one habit. The representative's visit list, the answer to the operator, the objection to a deduction and the monthly pattern review all draw from the same entries. Build the file during the stay, and the claim becomes a matter of copying extracts instead of reconstructing a week.