Work About Stack Services Contact
English Nederlands
Back to Work
Complete solution — Laravel & Flutter

TOS Ontstoppingsservice

A drain-service company automated end to end.

Year

2024 — now

Client

TOS Ontstoppingsservice

Services

Complete solution

Tech stack

Laravel · Flutter

TOS is a family-run drain unblocking business in the Rotterdam area, working for housing corporations, property managers and owners’ associations across Groot-Rijnmond since 1985, day and night. I build and run the internal system that sits between their planning and their customers.

Appointments that confirm themselves. Work orders arrive as CSV files dropped over SFTP from the back-office system. A scheduled job picks them up every minute and turns each one into an appointment. Because SFTP writes are not atomic, a file is left alone until it has been untouched for a settle window — otherwise a large upload gets read halfway through. Handled files move to a processed directory, failures to their own, and every run writes a heartbeat that a health endpoint checks, so a silent pipeline is noticed instead of discovered a day later.

Reaching the customer where they actually are. Every appointment gets its own unguessable link. The customer opens it and confirms or declines the visit in one tap — no account, no app, no phone call. Those links go out over the WhatsApp Business Cloud API and, in parallel, over SMS, because the one thing you cannot do is assume which of the two a household reads. WhatsApp only permits pre-approved templates here: the 24-hour customer service window never opens, since the customer has not messaged the company first. The link itself is built from the model that serves it, so the URL in a message sent weeks ago cannot drift away from the route that answers it.

The day before. A scheduled command finds everyone with a visit tomorrow and sends a reminder over both channels, with a dry-run mode for checking who would be messaged before anything goes out. Messaging is where quiet bugs get expensive, so each message carries a unique identity per appointment, per kind and per recipient — a reminder cannot overtake the original notice, and nothing sends twice. Failures retry with a deliberately long backoff: a provider outage is not resolved in seconds, and a duplicate appointment message is worse than a late one.

Talking to customers who do not speak Dutch. Technicians record a voice message in the field app; it is transcribed with Whisper and translated into Dutch, covering Dutch, English, German, Polish, Turkish, Russian, Ukrainian and Arabic. The transcription runs synchronously on purpose, so the employee can read back what was understood before anything is sent rather than finding out afterwards.

Paying on the spot. Numbered QR codes resolve to a Stripe checkout, so a job can be settled at the door instead of turning into an invoice, a reminder and a chase.

The stack is Laravel with a Flutter app for the field crew, with application monitoring on top. It has been in daily use since 2024 and I keep developing it.

Something like this, for you?

Most of these started as a conversation about a process that had stopped scaling.

Start a conversation