Skip to content
Client build / Case Study
Live in production

Dolce Aesthetic Clinic

with Polished by Dolce and Core Yoga & Pilates - Erbil

One system that welcomes every new client, asks for a review and sends the owners' campaigns across three sister businesses - each email once, with nobody chasing it.

3
brands, one system
5 min
new client to welcome
54
automated tests

The brief

Dolce runs three businesses in Erbil: an aesthetic clinic, a salon and a yoga and pilates studio. Many clients use more than one of them. Every new client was meant to get a welcome, a request for a review a few days later and the occasional offer, and in practice that depended on someone remembering to do it.

The owners wanted it to happen by itself and sound like them. It also had to be dependable: no client emailed twice, nobody emailed who had not agreed to it, and nothing announced without an owner's say-so.

What we built

A system that reads the client list the business already keeps and does the rest. A new client is welcomed by each brand they belong to within five minutes of being added. Three days later they receive one request for a Google review. Every client is asked, nobody is filtered out, and nothing is offered in return. Birthdays are remembered.

When the owners want to announce something, they write it in a private portal and preview exactly how it will arrive. Nothing goes out until it is approved from an email on the owner's phone. A campaign can start at once or wait for a chosen date and time.

The portal reports in sentences instead of charts: how many emails went out today, what is still waiting, and a live countdown to the next batch. When something needs a person, it says so at the top of the page in plain words.

The engineering underneath

Sending an email is easy. Sending it exactly once, every time, through outages, is the work. Each email is reserved in the database before it leaves, so two runs at the same moment or a client entered twice cannot produce a duplicate, and a run that dies halfway is picked up where it stopped.

Mail leaves through the clinic's own Google Workspace with a second provider standing by. If the first refuses, the second carries the same email and the owners are told. A test message goes down both routes every morning, so a broken route is found on a quiet day and not on campaign day.

The system is deliberately polite to inboxes. It keeps to a daily allowance, continues large batches in business hours, and sets an address aside the moment a mail server confirms it is dead. When a mail route has a bad quarter of an hour, it waits and retries instead of blaming the people on the list. Consent is checked on every send, and every email carries a one-click unsubscribe.

We did not take our own word for any of it. The system was run end to end against a mail server built to misbehave - refusing addresses, dropping connections, going down in the middle of a campaign - and 54 automated tests now replay those failures on every change. An independent review of the code went looking for ways to email someone twice or skip them silently, and everything it found was fixed.

Built to be handed over

It runs on one small server with no subscription platform underneath it. The code, the documentation and the data belong to the client, and it is written so their own team can run it without us. This is the approach behind our automation work and backend systems: the part nobody sees gets the same care as the part everybody does.

Want the follow-up to happen by itself, and to be able to trust it?

Book a 30-minute call

Also see: Studio Chenille case study and AttoGuard case study.