EmpfangoThe short answer
Handling a complaint in commercial cleaning takes five steps: answer the call, capture site, area, defect and deadline, request a photo, notify the person in charge, confirm back. With a phone assistant the first part takes around 60 seconds.
Today these steps run through notes, call forwarding and a WhatsApp group in which the report has vanished after twenty messages. This article shows how the client's call becomes a case that contains site, defect, deadline, photo and the responsible person before the site manager has even picked up.
Why complaints end up in note chaos today
Complaints reach the site manager between sick calls and material orders, usually by mobile phone, and are answered there but rarely documented.
Blink describes the daily routine like this: “a client calls with a complaint … With complaints he has to react, document and communicate” (Blink blog on site managers, 8 May 2025, retrieved 14 Oct 2026). Job profiles for dispatchers list “point of contact for queries, complaints, site inspections” as a standard task (Indeed). And the tools for it in 2026 are still often “paper notes, wall calendars and group WhatsApp” (hagel-it).
The market makes every complaint more expensive: in the BIV autumn survey 2026, 70 % of companies report clients cutting back services and 57 % a decline in clients or orders (rationell reinigen, 2 Oct 2026, as of 10/2026). With labour costs at 85 % of revenue (BIV industry report 2025) margins are thin. A client who cannot get through twice and finds nothing documented the third time cuts the next contract.
Then there is the question of evidence. If the client says the area has not been cleaned since Tuesday and nobody has the report with date and photo, it is one word against another. Whoever documented the case can show when it was reported, when it was fixed and when it was confirmed.
The process in five steps
A documented complaint case needs five pieces of information: who is reporting, which site and which area, which defect, by when, and who on your side is responsible.
Steps 1 to 4 run without your team being involved. Step 5, fixing and confirming, remains manual work; that is the part that deserves your time.
The 60 seconds break down like this: announcement and greeting around ten seconds, asking the six fields around forty, assurance and goodbye ten. It only takes longer if the caller cannot name the site unambiguously or reports several defects at once. Then Empfango asks until each defect has its own field.
- 1. Answering: the client calls the company number. Empfango picks up immediately, even if the site manager is on another site, and announces that an AI is speaking.
- 2. Capturing: Empfango asks for the caller's name and company, the site, the affected area (floor, room, zone), the type of defect and the requested deadline. The callback number is added. These are the fields every case will need later.
- 3. Requesting a photo: if WhatsApp is connected, Empfango sends the caller a message after the call. The client replies with a photo of the area, and the image sits in the conversation belonging to the case.
- 4. Notifying: the summary with all fields goes via WhatsApp, Telegram, email or webhook to the responsible site manager. Transcript and summary are in the dashboard.
- 5. Confirming: still during the call, the client is assured that the report has arrived and who will take care of it. Your team reports the fix back, with a date.
Today and with Empfango compared
The difference is not in individual steps but in every step getting a fixed place: fields instead of notes, a case instead of a group chat, a timestamp instead of memory.
| Step | Today (notes, WhatsApp group) | With Empfango |
|---|---|---|
| Answering | Site manager's mobile rings on site; voicemail or callback in the evening | Company number is answered immediately, including after 5 pm and at weekends |
| Capturing | Keyword on a note or in someone's head; area and deadline often get lost | Name, site, area, defect, deadline and callback number as fixed fields in summary and transcript |
| Photo | Client sends it at some point to someone in the group | WhatsApp message after the call; the reply with the photo sits in the conversation for the case |
| Notifying | Voice message in the group WhatsApp; who is responsible gets sorted out in the chat | Summary to the stored site manager via WhatsApp, Telegram, email or webhook |
| Confirming | Client calls again after two days to ask | Assurance during the call; team reports the fix back with a date; status enquiries by phone |
| Evidence | Search the chat history, look for the note | Transcript with timestamp in the dashboard, optionally via webhook in your own system or in the LiteLog portal |
Where the case lives: dashboard, webhook or LiteLog portal
The case needs a place where it continues to live after the call: the Empfango dashboard is enough for small companies, a webhook hands it to your ticket system, and with LiteLog reports land directly at the site.
For companies using LiteLog for patrols and checkpoints there is a special option: reports land directly in the LiteLog portal, at the site and in the area they belong to. The site manager sees the complaint there next to the checkpoint data, and the fix is documented in the same place. In the same way Empfango can give clients information about patrols from LiteLog data, see client enquiries.
This also works without LiteLog. Without the connection, the case stays in the dashboard with transcript and summary, and the webhook hands it to any system that accepts HTTP calls, such as a ticketing tool or a spreadsheet.
Which place you choose depends on the number of sites. Up to around ten sites the dashboard is enough, because the site manager knows all the cases anyway. Beyond that, a system pays off in which complaint, re-clean and confirmation hang on one site and can be shown as a list at the quarterly review with the client.
What Empfango does not do with a complaint
Empfango answers, captures, notifies and provides information; it does not decide who re-cleans the area and does not write into any third-party system without a webhook.
Faults at the site that are not complaints, such as a water leak or a broken door, take the same route; how that works around the clock is shown in fault reporting 24/7. For an overview of everything Empfango handles for cleaning companies, see the industry page.
- No assignment of staff: who takes on the re-clean is decided by the site manager.
- No promises about the fix: Empfango confirms receipt and names the contact person, but does not promise a date your team does not know about.
- No outbound calls without configuration: the confirmation to the client after the fix stays with your team.
Frequently asked questions
Store your sites in the knowledge base. Empfango asks for the site and matches it against this list. If the caller only gives an address or a company name, Empfango asks until the assignment is unambiguous.
The case remains complete, just without an image. The site manager sees in the summary that a photo was requested and can follow up during the callback or take one during the site inspection.
Yes. Empfango provides information from the data you have stored. With the LiteLog connection this includes whether a re-clean or a patrol at the site has been completed. Without the connection, Empfango states when the report came in and who the contact person is.
Transcript and summary stay in the dashboard until you delete them or a retention period applies. Audio is not stored permanently. As evidence towards the client, the transcript with timestamp is sufficient.
Conclusion
A complaint in commercial cleaning is answered and captured in 60 seconds once the fields are fixed: site, area, defect, deadline, callback number, photo. The rest, re-cleaning and confirmation, stays with your team, but with a case that has a date and content. That is the difference between “he called at some point” and evidence you can put in front of the client.