Skip to content
Stackly by Temaco

Personal project

A sequence that goes quiet when the customer replies.

A handful of messages spread over time, each saying something different, sent through the channel the customer actually uses. A reply stops the sequence immediately, so nobody receives an automated message in the middle of a human conversation.

The problem it solves

Most people do not answer the first message simply because they were busy. Chasing manually after a few days is dull and the first thing to fall off the schedule. An automation that fires blindly risks something worse: a message arriving after the customer already replied.

Built with

  • n8n
  • Telegram Bot API
  • SMS API
  • PostgreSQL

How it works

  1. 1The lead enters the sequence tagged with its source and preferred channel
  2. 2Messages go out at intervals matched to response speed, each with different content
  3. 3Any reply stops the sequence immediately and notifies a person
  4. 4Opt-outs are stored permanently and honoured across every channel
  5. 5Finished sequences move to a list for re-contact after a longer gap
1Lead enters the sequence2Message 1 — SMS or Telegram3Message 2 a few days later4A reply stops the sequence5Opt-out stored permanently
Flow: lead enters, spaced messages, reply detected, sequence stopped, opt-out handled.

What I would refine for a client

What is missing is branching by what the customer showed interest in. Right now everyone gets the same path. At a client I would split it by product and add a time window, because an SMS at seven in the morning does more harm than good.

Do you have a similar process?

Describe it in a few sentences. I will tell you whether it can be automated and what it would cost — including when the answer is that it is not worth it.