Kommo + Altegio

Clients don't get lost between your CRM and bookings

The service decides on its own who to remind and when — no admin has to keep track of thousands of clients across dozens of services

Why we're not like the rest

Native to Kommo + Altegio

Not a bolted-on broadcast tool — it reads CRM pipelines and service categories directly

Every service tracked separately

Laser hair removal doesn't hide an overdue dental reminder

Control group — on request

If the network wants it, some clients are deliberately left alone so the effect of reminders can be measured accurately

Transparent down to one client

Any phone number shows why a task exists or doesn't

No spam avalanche

Daily caps and merged tasks keep managers from being overwhelmed

Sounds familiar?

A lead lands in your CRM, talks to a manager — and disappears before ever booking. A client who visited six months ago never comes back — not because they didn't want to, but because no one reminded them in time. No admin can keep thousands of people in mind across dozens of services at once.

How it works

1

Nothing to check manually

The system keeps track of every client and every service on its own — no need to remember who needs a reminder and when.

2

It creates a ready-made task for the manager

With the text and the deadline already filled in — right inside your CRM. The decision on what to do next always stays with a human.

3

It closes the task itself

Once the client books or shows up, the cycle starts over — nothing to clean up by hand.

Try it in your business — the request takes a minute.

Try it

The full client journey, as the system sees it

Not a single funnel, but a connected chain of states — from the first CRM contact to regular visits and, if needed, back again.

  1. 1
    Kommo

    A Kommo contact with no deal yet

    Just a contact. The clock starts from the date it was created.

  2. 2
    Kommo

    A deal opens in a pipeline

    If deals are open in several pipelines at once, each is tracked in parallel, with its own separate clock — no pipeline takes priority over another.

  3. 3
    Kommo

    All deals are closed

    No active deal left — reminders stop. This is not "we don't know you yet": there was already contact, so the tone has to be different.

  4. 4
    Altegio

    First booking created in Altegio

    The booking exists, but the visit hasn't happened yet — this used to be a "dead zone," now it's a state we actually track.

  5. 5
    Altegio

    First visit completed

    The lead has officially become an Altegio client.

  6. 6
    Altegio

    From here, each service is tracked on its own

    On schedule, overdue, or paused (an upcoming booking is close) — independently, for every service the same person uses.

Plus two cross-cutting states at any stage: the client opted out of reminders — and we go silent entirely; or the client came back — the cycle starts fresh.

Every pipeline gets its own chain

A lead from the "Social media" pipeline and a lead from the "Partners" pipeline are different stories, and they get different messages on different schedules. The system maps a specific Kommo pipeline to a specific touchpoint chain and task type — not one script for everyone.

Kommo and Altegio speak different languages

Kommo
pipelinesdealscontactstaskstags
Altegio
visitsbookingsservicescategories

The bridge between the two systems is the client's phone number — the one thing that doesn't change. Internal IDs on both platforms turn out to be unstable in practice.

Try it in your business — the request takes a minute.

Try it

Lead activation

A Kommo lead gets a different tone depending on their history: someone we've never talked to doesn't get a "we haven't seen you in a while" message — these are different states with different logic. We also separately track the case where a booking already exists but the visit never happened — a point where clients used to simply fall out of sight.

Client reactivation

Not one blanket "come back" broadcast, but a chain of touchpoints with growing intervals — for example −7 / 0 / +3 / +10 / +21 / +45 / +90 / +180 / +365 days from a reference date, tracked separately for each service. A visit for one service does not hide an overdue reminder for another.

Problems we already solve in practice

Duplicate contacts

In Kommo, the same client often exists as two separate contacts — we match by phone number, not by internal ID.

The "avalanche" on first launch

If no one was tracking lapsed clients before, there could be thousands of them the moment you switch this on — we split them into a current stream and an accumulated backlog with separate limits.

False reminders

We don't message people who already visited, just for a different service — the check runs separately per service, not "for the client in general."

Why this isn't spam or chaos

A flexible touchpoint schedule

The intervals between reminders are tuned to your business — not one blast sent to everyone at the same second.

Daily caps

A cap on new tasks per day keeps managers from being overwhelmed, while the backlog gets worked through gradually, on its own track.

Smart "don't interrupt"

If a client already has an upcoming booking, no reminder is sent — they're coming anyway.

One call instead of several

If several reasons to reach out line up for the same client, the system merges them into a single task instead of creating a pile of separate ones.

Try it in your business — the request takes a minute.

Try it

What this means for you as the owner

Works inside the tools you already use

No new software to learn — managers keep working in Kommo and Altegio, tasks simply show up where they already look.

You can start cautiously

Daily limits start conservative and grow gradually — once you've seen results and know what to trust.

Works across your whole network

Not one location but the whole branch network at once — each with its own time zone and responsible manager.

Accurate numbers, not wishful thinking

If the network wants it, some clients are deliberately left alone — this is the control group. Comparing against it gives an accurate estimate of how many people came back because of the reminder, not because they would have come anyway. By default, every client gets reminders.

Full transparency for the owner

At any moment you can see your actual chains, intervals, and quotas — not abstract rules from a slide deck. For any phone number, you can check in seconds why a client does or doesn't have a task right now. Plus you can see how many touches have been made and how the picture changes over time — not "switch it on and forget it."

Want the same for your business?

Leave a request — we’ll show how reminder chains will work across your branches.

Or write to us directly:
founder@alteg-tech.com

What are you interested in (pick any)

By submitting the form you agree to the Privacy Policy.