SERGEY REVIN

Clients come back — for the dates that matter to them

After a visit, nobody usually talks to the client until their next booking. Nobody has time to ask every client about birthdays and anniversaries, write the dates down and remind them on time. The service does it on its own: it writes to the client in their messenger, remembers the dates and sends a personal discount 3 days before each one.

≈8 min → 0

of manual messaging and date tracking per client

Estimate: an invite, entering dates in a calendar and an offer for each of ~2 dates — 2 minutes each by hand

  • up to 10

    reasons to come back for every client

  • 3 messengers

    WhatsApp, Telegram and MAX — from the business’s number

  • 0

    apps the client has to install

Before

≈8 minutes per client — plus a daily calendar check

  1. Person2 min

    A couple of weeks after the visit, write to the client and ask about important dates

  2. Person2 min

    Read the reply and put the dates in a calendar

  3. Person

    Check every day whether someone’s date is coming up

  4. Person2 min per date

    Come up with a discount, create a code and write to the client

  5. Person

    Note who came with a code

Nobody has time for this, so after the first visit nobody writes to the client.

After

People only handle unclear replies and codes

  1. System

    The visit is marked in the booking system — the service queues an invite on its own

  2. System

    Two weeks later it writes to the client in their messenger, during business hours

  3. System

    It reads the reply, saves the dates and confirms: “Saved”

  4. Person

    Check a reply if it has a question or the service isn’t sure

  5. System

    3 days before the date it sends a personal discount code

  6. Person

    Mark the code as used when the client comes in

How it works

Client chat

Booking system

Anna K.

Visit · March 4✓ Attended
TodayMarch 4

Client’s important dates

14.02Anniversary
21.06Mom’s birthday
DEMO-7K2QX−15%
☀MorningWhatsApp · Telegram · MAX

  1. 1

    Visits come from the booking system

    Every 5 minutes the service pulls visits marked “client attended” from YCLIENTS, a booking system. Nobody copies anything by hand.

  2. 2

    It writes from the business’s number

    Two weeks later the client gets a message in WhatsApp, Telegram or MAX — wherever they already talk to you. The delay is configurable, even per service, and messages only go out between 10am and 8pm.

  3. 3

    It understands replies in the client’s own words

    “14.02 anniversary”, “mom’s bday June 21”, “for New Year” — dates in numbers and words, and holidays without a date. A question about booking or prices isn’t taken for a date, and a reply with a question goes to an admin so the client never gets an off-topic answer.

  4. 4

    An offer for the occasion

    3 days before the date — a personal code: 15% off for birthdays and anniversaries, 10% for holidays, valid for 14 days. Discounts, timing and texts change in the admin panel without a developer.

  5. 5

    Everything is visible in the admin panel

    Summary, upcoming dates, reply review, promo codes and a message log. A client writes “stop” — and is unsubscribed right away.

What it is made of

  • YCLIENTS

    The online booking system: this is where the service learns who came in.

  • Messengers

    WhatsApp, Telegram and MAX from your business’s number — wherever the client already talks to you.

  • Dates service

    Reads replies, remembers dates and issues codes. Runs on your own server.

  • Admin panel

    A web panel for admins: reply review, upcoming dates, promo codes, texts and discounts.

What it looks like

Mock-up with demo data

Morning

Anna, in 3 days, June 21, it’s your mom’s birthday.

Treat her to a visit: 15% off with code DEMO-7K2QX until July 2.

· Demo data

11:00

The offer 3 days before the date

💬Client’s reply → what is saved

Client wroteOccasionResult
“14.02 anniversary, 21.06 mom’s bday”2 datesSaved
“hubby’s bday is September 3”BirthdaySaved
“for New Year and March 8”HolidaysSaved
“how much is a booking?”Not about datesTo a person
“12.05 son’s bday, can we both come?”Has a questionFor review
Demo data
How the service reads replies (translated from Russian)

A good fit if

  • Clients book online, and after a visit you don’t talk to them until their next booking.
  • People give your services as gifts or time them to occasions: birthdays, anniversaries, holidays.
  • You use YCLIENTS — or another booking system you can pull visits from.

Common questions

Why no AI?

Replies about dates are short and alike — rules parse them instantly, for free and predictably. Anything the service isn’t sure about is checked by a person, so a client never gets a wrong confirmation.

Does the client need to install anything?

No. The chat happens in the messenger they already use with the business, from the same number.

What if a client doesn’t want messages?

They write “stop” — the service unsubscribes them right away and confirms. The client consents to their dates being processed when they reply to the invite.

Does it work without YCLIENTS?

The mechanics are the same for any booking system you can pull visits from: only the connection changes.

How it works under the hood →Stack, architecture and details — for whoever implements it.

Have a similar problem? Get in touch — we start by mapping your processes.

Message me on Telegram